> 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/functional-requirements/content-retrieval-and-access.md).

# Content Retrieval and Access

| ID          | Requirement                                                                                                                                                                                                                                         |
| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| LCR-RET-001 | For any authorised request by persistent identifier, the repository MUST serve the metadata record, the manifest, and either the content or a resolvable reference to it                                                                            |
| LCR-RET-002 | Content packaging MUST follow the manifest model in Data Structures, mappable to recognised packaging standards                                                                                                                                     |
| LCR-RET-003 | Retrieval responses MUST include version, status, classification, licence and provenance, so that consuming systems can honour rights and establish currency                                                                                        |
| LCR-RET-004 | The repository MUST support conditional and bulk retrieval adequate for offline caching and synchronisation, and MUST expose a changed-since mechanism allowing a consuming system to retrieve only what has altered since its last synchronisation |
| LCR-RET-005 | Consuming systems holding cached content MUST be able to determine, on reconnection, whether any cached item has been superseded, deprecated or recalled                                                                                            |


---

# 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/functional-requirements/content-retrieval-and-access.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.