Reference

Use this section for durable facts and contracts that should stay stable even as the user-facing adoption lanes and contributor flows evolve.

Contributor how-to material now lives under contributing/, and user-facing routing now lives in the top-level adoption lanes.

Contents

• CLI Reference - Shallow map of the OAT command surface with links to owning sections.
• File Locations - Where core OAT files, assets, and artifacts live.
• Docs Index Contract - Authored index.md maps, .md links, generated Fumadocs manifests, and MkDocs nav sync boundaries.
• OAT Directory Structure - Canonical .oat/ tree map and the role of each major directory.
• Troubleshooting - Common issues, diagnostics, and remediation guidance.

What Belongs Here

• stable file and directory contracts
• docs-system rules that other pages should link to instead of re-explaining
• troubleshooting material that remains relevant across workflow and docs changes

Related Sections

• CLI Reference for the command-surface map
• Docs Tooling for docs app setup and workflow guidance
• Contributing for code, docs, and skill-authoring practices