Documentation

To get architecture guidance, read the project documentation index and README first to understand system boundaries. Use targeted nested markdown reads to locate the specific contracts and runtime layer docs, prioritizing one focused read per session to avoid loading unnecessary pages.

Contract discovery in AGENTS.md involves loading the documentation helper module to perform targeted nested markdown reads. You must confirm the owning AGENTS.md contract after orientation to identify module ownership boundaries before proposing any code changes.

To keep documentation synchronized, update both the relevant documentation pages and the AGENTS.md contract files together. Follow the update synchronization rules between AGENTS.md and the /mod/_core/documentation/docs/ directory whenever workflows or contracts change.

You need frontend runtime documentation when you are unsure which module owns a UI primitive or how routing works for server pages. Reading the docs index first helps you select the right runtime layer documentation before answering architecture questions.

No, project documentation orientation discourages loading many large pages. It encourages one focused read() call per session and prioritizes documentation indices so you can target specific contract pages without unnecessary file loading overhead.