> 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/anchor-use-cases.md).

# Anchor Use Cases

Functionalities, requirements, data structures and APIs are derived from the following use cases.

* **An LMS retrieves curriculum-aligned resources.** A school's LMS queries for approved resources mapped to a curriculum node and grade, and presents them in its own interface. The repository never sees the learner.
* **An application discovers content by competency.** A third-party application searches by learning outcome, language, licence and accessibility features, receiving ranked, machine-readable results with resolvable references.
* **A teacher tool assembles a draft lesson plan.** A teacher-facing service invokes optional AI assistance to draft a plan for a curriculum node, grounded exclusively in curated content, with full provenance, for the teacher to accept, amend or discard.
* **An authority publishes and versions national content.** After a curriculum reform, revised materials are ingested, assurance re-runs, superseded versions are deprecated with auditable history, and consuming systems are signalled of the change.
* **An external catalogue harvests metadata.** A regional or international aggregator harvests metadata on a schedule, extending discoverability without duplicating content.
* **Educators contribute under authorisation.** An authority authorises practising teachers to produce and submit content. Submissions enter the same assurance workflow as institutional contributions, with provenance recorded to the contributor and their authorisation.
* **An application serves content directly to learners.** A learner-facing application retrieves published content for a curriculum node. The repository authorises the application, not the learner, and holds no learner data.
* **A consuming system operates under constrained connectivity.** A system in a low-bandwidth or intermittently connected environment retrieves content in bulk, caches it, and later synchronises only what has changed. Continuity does not depend on continuous connectivity.
* **Several jurisdictions share one curriculum framework.** A framework agreed across sovereign jurisdictions is used by each. An alignment asserted against it can serve every participating deployment, while each jurisdiction retains its own authority — making the record of who asserted an alignment, against which version, with what review status, a governance requirement rather than an audit convenience.

{% hint style="info" %}
**Evidence.** Use case 5 is daily practice in Finland, where the national Library of Open Educational Resources (aoe.fi) exposes multilingual metadata for harvesting. Use case 8 is the operating condition for Learning Equality's Kolibri, which packages content into versioned channels synchronised into fully offline environments. Use case 9 describes the Eastern Caribbean, where a harmonised primary curriculum agreed across OECS member states is served from a shared platform while each state retains national authority.
{% 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://experience-digital-transform.gitbook.io/experience-digital-transformation/dpi-for-education/learning-content/specifications/description/anchor-use-cases.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.