> For the complete documentation index, see [llms.txt](https://upskilling.stacs.scot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upskilling.stacs.scot/conference26/session-d-workshops/safe-to-think-safe-to-fail.md).

# Safe to Think, Safe to Fail

Why Computing Classrooms Help Every Brain Breath

The session will explore what makes Computing Science feel safe and accessible for many neurodivergent pupils and how we can protect that. It will also consider the hidden barriers that can undermine that sense of safety, such as logging in, finding files, switching between windows, remembering multi-step instructions, sensory overload or not knowing where to begin.

We will share practical ways to reduce those pressures through predictable routines, clearer resources, manageable instructions and supportive relationships. The aim will be to help us create classrooms where pupils feel safe to ask for help, make mistakes, debug, try again and show us what they can really do.

{% hint style="info" icon="school" %}
**Pamela** **Boal**

Director of Digital Strategy

Morrisons Academy
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://upskilling.stacs.scot/conference26/session-d-workshops/safe-to-think-safe-to-fail.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.