// Track

Self-Maintaining Documentation

Docs as Automated Artifacts

Stop maintaining docs by hand — make them maintain themselves. Drift detection that tests docs like code, generated references with one source of truth, doc-updating agents on a safety model, runbooks verified in CI, autopilot changelogs, doc registries, and the freshness SLOs and blocking gates that make stale docs unmergeable.

Recommended: Complete Documentation is King first

10 lessons~80 min total

Lessons are shown in recommended order. Complete them in sequence for the best experience — or jump to any lesson.

Lesson 596·8 min read

Docs Rot Because Humans Maintain Them

Documentation scales with the system; human attention doesn't — the only fix is to stop relying on humans to maintain it.

Lesson 597·8 min read

Drift Detection: Docs That Are Tested Like Code

Write drift tests in vitest like any other test — they run on every PR and block merge the moment a documented fact diverges from reality.

Lesson 598·8 min read

Generated References: One Source of Truth

When a source of truth changes, every doc projection should update automatically — generators with ownership markers make hand-editing a detected offense.

Lesson 599·7 min read

Agents That Update Docs

A doc-bot that opens PRs instead of pushing to main, constrained to mechanical ground by the surgical-edit contract, is the last automation layer before the human semantic boundary.

Lesson 600·8 min read

Runbooks That Stay True

A runbook is only as good as the last time its steps were executed against the real system — drift is silent until 3am.

Lesson 601·8 min read

Changelogs & Release Notes on Autopilot

Conventional commits are the structured source — haiku classifies, sonnet narrates, and the changelog writes itself while the team ships.

Lesson 602·8 min read

Docs as Dashboards: Registries & Status Ingestion

The registry is the index over every doc that exists — who owns it, when it was last verified, and whether the file the registry claims is there is actually there.

Lesson 603·8 min read

Freshness SLOs & CI Gates That Block

A doc verified six months ago is expired even if the file was never touched — verification is the SLO, and CI must block on it.

Lesson 604·8 min read

The Doc-Bot Safety Model

A bot that confidently rewrites an architecture doc with a config option that has never existed is worse than the stale doc it replaced — recency signals trust, and the safety model is the only thing between auto-merge and hallucination.

Lesson 605·9 min read

Capstone: The Self-Maintaining Repository

A self-maintaining repository is not one with perfect documentation — it is one where the infrastructure maintains the documentation, and human attention is reserved for the semantic boundary where judgment is actually required.