> 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-c-workshops/navigating-computing-in-the-cic-r.md).

# Navigating Computing in the CIC (R)

Unpacking the New CIC Technologies Framework for Computing

This session introduces the newly published curriculum framework for Computing Science, tracking "know, do, and understand" statements from early years through to the fourth level. Because the framework is highly structured with dense, nested tables, this workshop acts as your essential map. 

We will focus entirely on breaking down its main features and learning how to navigate the layout so you can easily find what you need. 

{% hint style="warning" %}
Please note

* This is part one of a two-part series; this morning's walkthrough lays the groundwork for the critical feedback session later this afternoon. Although no obligation to follow up.
* This first session runs twice in the morning, choose whichever is convenient to you.
  {% endhint %}

{% hint style="info" icon="school" %}
**Brian** **Clark**

Education Officer

Education Scotland
{% 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-c-workshops/navigating-computing-in-the-cic-r.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.