# Documentation Agent Instructions

Start at the [index and authority map](README.md). Follow [documentation governance](governance/documentation.md) when maintaining this subtree; follow [development guidance](implementation/development.md) and [security and operations](implementation/security-and-operations.md) for separately authorized implementation tasks.

- Edit the canonical owner of a concept, not a competing summary. The architecture overview is a navigation map only.
- Preserve detailed decisions, rationale, examples and constraints from the [source ledger](governance/source-map.md). Archived sources are provenance, not current build authority.
- [D01-D10 are settled](governance/decisions.md). Final transcript decisions and explicit project-owner corrections supersede conflicting repository prose. Do not reopen these decisions or create new architecture decision numbers. Missing code or physical implementation details do not mean missing architecture approval.
- Preserve the current 35-active-document structure (the 34 measured on 2026-09-23 plus the [readiness register](implementation/readiness-register.md), the sole owner of temporary decisions, deferred capabilities, known defects, architectural gaps and production-readiness risks). The cross-cutting [core object model and authority](architecture/core-object-model-and-authority.md) document is the approved additional conceptual owner; do not split documents automatically by engine. Follow the meaningful-concept-ownership test in documentation governance, which also records the dependent implementation records and historical documents that are not counted.
- Distinguish settled semantic contract, chosen implementation mechanism and current implementation status. Specify the smallest conforming mechanism in existing implementation owners; record evidence and limitations in [status](implementation/status.md). A simpler MVP must retain architectural distinctions.
- Reuse compatible UI and technical lessons without preserving old marketing models, schemas, APIs or migration obligations. The current specification takes precedence.
- Validate links, anchors, authority consistency and source coverage after documentation edits. Preserve the four archival sources unchanged.
- Do not run setup, deploy, change application code or alter the database during documentation-only work. Respect the current user-authorized scope.