> For the complete documentation index, see [llms.txt](https://unitera.gitbook.io/unitera-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unitera.gitbook.io/unitera-docs/guide.md).

# Guide — Maintaining the UNITERA Public Documentation

This repository explains reviewed UNITERA principles and product behavior in German and English. It is a curated public projection, not an engineering inventory.

## Content workflow

For a substantive change:

1. verify the claim against its current owning source;
2. distinguish established semantics, public status, candidates, and gaps;
3. publish only the minimum abstraction needed to explain what and why;
4. synchronize German and English meaning;
5. apply the composition rule across the complete public projection;
6. run the disclosure, structure, link, and formatting checks.

Read `GOVERNANCE.md`, `CONTRIBUTING.md`, `PUBLICATION_MANIFEST.yaml`, and `MERMAID.md` before editing.

## Core rule

Public documentation creates no adoption, permission, runtime authority, or production activation. If a public statement conflicts with its verified owning source, correct the public projection without publishing restricted source detail.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://unitera.gitbook.io/unitera-docs/guide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
