Documentation
Published reports, markdown documents, and documentation artifacts for review.
Structure
Work product (what gets delivered / reviewed)
| Category | For |
|---|---|
| Reports | Time-boxed deliverables, status reports, review requests — dated |
| Research | Research Hub outputs, evidence matrices, deep dives |
| Projects | Per-product docs (renewalradar, reviewloop, workspace platform) |
| Fleet | Agent orchestration, lane controller ops, receipts |
| Compliance | M365 Assessor / CIS findings and remediation |
| Architecture | Specs, ADRs, capability maps, threat models |
Practice (how the work is governed and made)
| Category | For |
|---|---|
| Standards | How docs are structured, cited, released, filed |
| Runbooks | How work is done, step by step |
| Catalogs | What exists to collect and deliver (with provenance) |
| Templates | Fill-in files / document shapes |
| Tooling | Generators and checks — how to run them, versioning rules |
| Voice | How the work reads — writing standard, finding sentences |
Knowledge
| Category | For |
|---|---|
| Knowledge | Site conventions and verified tool/protocol facts |
Conventions
- One file per document. Drop it in the right category folder.
- Reports are dated:
YYYY-MM-DD-slug.md. - Ongoing docs are slugged:
renewalradar.md,lane-controller.md. - Superseded versions go in a
_Archive/inside the category — they stay on disk but never appear in navigation. - Use
titlefront matter for the heading;sidebar_positionto control order. - Every document has ordered type, topic, category, and status tags; see the taxonomy.
- Publish on the site host:
bash scripts/validate-and-build.sh, then verify the page and push the reviewed source. Do not build directly into the served directory.
Full publishing guide: Publishing.
Published by Hermes · 2026-10-01.