> 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/dpi-for-education/learning-content/specifications/description/scope.md).

# Scope

## Education levels

Version 1.0 addresses school education, corresponding to ISCED 2011 levels 1 to 3 and broadly equivalent to K-12.

Out of scope for version 1.0: ISCED level 0 (early childhood education); ISCED levels 4 and above (post-secondary non-tertiary and tertiary); and vocational and further education, which span several ISCED levels and are therefore named separately rather than by level.

Nothing here prevents later extension. The data model uses the ISCED vocabulary throughout, so extension is a scope decision rather than a remodelling exercise.

## Out of scope

The Building Block does not provide a teacher-authoring environment as a primary function; communities, forums or social features; course delivery, sequencing, scheduling, enrolment or any learner-facing presentation layer; learner progress tracking, gradebooks, assessment engines or proctoring; or its own implementation of identity, authentication or consent.

The authoring exclusion concerns the provision of an authoring environment, not the origin of content. Content authored by educators and submitted under authorisation is within scope for ingestion; the tools used to author it are not part of this Building Block.

## Boundary with the Digital Registries Building Block

The Digital Registries Building Block is a tool that manifests and maintains registries. A registry is a collection of documents of a specific type. This specification defines a registry of educational content that the Digital Registries Building Block can manifest; it does not redefine that Building Block.

{% hint style="info" %}
**Provided by Digital Registries, and not specified here:** storage across heterogeneous databases and file systems; assembly and segmentation of datasets across documents; create, read, update, delete, verify and list operations; schema versioning and introspection; transaction, administrative, security and performance logging; and registry-management fields such as record identifier and status.

**Specified here:** which fields a registry of educational content must carry; what they mean; the roles that operate on them in an education context; the states an item moves through; and the interfaces through which education consumers reach it.
{% endhint %}

The Digital Registries Building Block is optional for other Building Blocks. A conformant LCR MAY be implemented using it, and MAY equally be implemented on other storage, provided the requirements of this specification are met.

Where content resides is a deployment decision. Content may be held in the registry; held as files registered in the registry with identifiers carried in referencing documents; or the registry may hold references only.


---

# 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/dpi-for-education/learning-content/specifications/description/scope.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.