> 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/agents.md).

# AGENTS.md — unitera\_public\_docs

## Repository mission

This repository publishes the bilingual public documentation projection for UNITERA. It is an explanatory surface, not an authority source.

## Authority boundary

* The verified source in the owning repository wins on conflict.
* This repository creates no semantic, contractual, tenant, runtime, or execution authority.
* Registry references and imported material do not create authority.
* Candidate and non-canonical branch material must remain explicitly labeled.

## Public disclosure boundary

Public documentation is a curated, deliberately lossy projection. It explains what UNITERA does and why; owner/internal sources define exactly how, where and under which contract.

Every statement belongs to one disclosure class:

* `PUBLIC_CORE`: principles and product behavior suitable for direct explanation.
* `PUBLIC_ABSTRACTED`: architecture explained without reconstructable implementation topology.
* `PUBLIC_STATUS`: coarse maturity only: concept, contracted, under implementation, pilot preparation, limited pilot, or production.
* `RESTRICTED_SOURCE_DETAIL`: exact repositories, refs, change/review identifiers, internal object/schema/package names, state enums, capability identifiers, providers, credentials, protocols, routes, enforcement order and test topology.

Composition rule: individually acceptable facts MUST NOT be combined when their combination reconstructs internal ownership, runtime, authority or enforcement topology.

Exact refs remain required for internal verification but MUST NOT be published. Engineering state changes continuously; public architectural state changes deliberately.

## Change rules

Before changing substantive content:

1. verify the owning source repository and exact ref;
2. verify the status label and distinguish canonical state from candidates;
3. update the German and English editions together;
4. update `PUBLICATION_MANIFEST.yaml` when publication metadata or source refs change;
5. avoid unverified production, deployment, runtime, or compliance claims.

Editorial-only changes may be scoped to the affected text when they do not change meaning.

## Diagrams

Mermaid in this repository is GitHub-native only. Follow `MERMAID.md` as the binding contract (GitHub renderer documentation: <https://docs.github.com/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-mermaid-diagrams>).

* Fence every diagram as a backtick `mermaid` block, never `~~~mermaid`.
* Quote labels that contain `/`, `<br>`, or other shape/syntax characters.
* Write the product path as `["/work"]`, never `[/work]`.
* Keep German and English diagram topology identical.

## Validation

* Confirm substantive German and English content remains synchronized.
* Run `git diff --check`.
* Review `PUBLICATION_MANIFEST.yaml` whenever source-backed claims change.
* Preview every changed Mermaid block on GitHub before merge.
* Run `python3 scripts/check_public_disclosure.py` and resolve every finding.

See `README.md`, `GUIDE.md`, `MERMAID.md`, `GOVERNANCE.md`, and `CONTRIBUTING.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 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/agents.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.