> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/build-with-ai/taxonomy-and-ontology/s10-ai-readme.md).

# S10 AI — README

> Generated from the verified S10 checkpoint on 22 October 2026. This page is a **machine-oriented retrieval reference**, not a human-facing recommendation. Relationships preserve their scope and evidence IDs. Do not interpret navigation or co-occurrence as universal necessity. Cite the original published EDT content to end users, not this reference.

Canonical S10 dataset contains 117 controlled concepts, 666 core entities, 276 core relationship records, 5952 detailed entities, and 6932 consolidated claims.

**Read order:** use the seven vocabulary pages to normalize language, then core relationships for reviewed contextual paths, and detailed claims for source-qualified assertions. Resolve sourcePageIds to published EDT pages before answering.

**Important:** These are plain Markdown projections generated from the S10 JSON source. Do not treat them as a substitute for S10 MCP graph search, traverse, source, and claim tools. Source IDs and the fuller original JSON remain authoritative. This pack is designed for native GitBook ingestion and should be tested for discoverability in the native Assistant and public GitBook MCP.

**Files:**

* vocabulary\_audience.md
* vocabulary\_capability.md
* vocabulary\_government\_task.md
* vocabulary\_journey\_stage.md
* vocabulary\_knowledge\_artifact.md
* vocabulary\_sector.md
* vocabulary\_technical\_topic.md
* core\_relationships\_01.md
* core\_relationships\_02.md
* core\_relationships\_03.md
* core\_relationships\_04.md
* core\_relationships\_05.md
* core\_relationships\_06.md
* core\_relationships\_07.md
* detailed\_claims\_01.md
* detailed\_claims\_02.md
* detailed\_claims\_03.md
* detailed\_claims\_04.md
* detailed\_claims\_05.md
* detailed\_claims\_06.md
* detailed\_claims\_07.md
* detailed\_claims\_08.md
* detailed\_claims\_09.md
* detailed\_claims\_10.md
* detailed\_claims\_11.md
* detailed\_claims\_12.md
* detailed\_claims\_13.md
* detailed\_claims\_14.md
* detailed\_claims\_15.md
* detailed\_claims\_16.md
* detailed\_claims\_17.md
* detailed\_claims\_18.md
* detailed\_claims\_19.md
* detailed\_claims\_20.md
* detailed\_claims\_21.md
* detailed\_claims\_22.md
* detailed\_claims\_23.md
* detailed\_claims\_24.md
* detailed\_claims\_25.md
* detailed\_claims\_26.md
* detailed\_claims\_27.md
* detailed\_claims\_28.md


---

# 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://experience-digital-transform.gitbook.io/experience-digital-transformation/build-with-ai/taxonomy-and-ontology/s10-ai-readme.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.