Doc Versioning Discipline

Doc Versioning Discipline Skill

Documents don't announce their own death — the old process doc reads exactly as confidently as the new one, and readers follow whichever they found first. Trust in a doc system is a metadata problem: every living doc carries a status header (what am I holding — draft? active? superseded-by-X?), meaningful changes get logged inside the doc (decisions, not typo-fixes), superseded versions get killed properly (pointer left behind, per the version-chaos-untangler rule), and a review date gives every doc a heartbeat — because "current as of when?" is the question every reader silently asks.

What This Skill Produces

• The status-header standard — the four-line block every living doc carries: status, owner, last-reviewed, supersedes/superseded-by
• The in-doc change log — decision-grade changes only, newest first, with the why
• The supersession protocol — how a doc dies: pointer installed, links redirected, search de-weighted where possible
• The heartbeat — review dates by doc class, and the stale-flag that fires when they lapse

Required Inputs

Ask for these if not provided:

• The doc population — what kinds of living docs (processes, policies, onboarding, architecture) and roughly how many; discipline scales to the estate, and a 30-doc wiki needs less machinery than a 3,000-page one
• The pain, specifically — people following stale docs? Can't tell draft from decided? Two versions warring? The protocol emphasizes its actual complaint
• The platform's powers — does the wiki support labels, ownership fields, redirects? The standard uses native features where they exist and header text where they don't
• The owners' reality — who will actually review docs on the heartbeat; unowned discipline is a decree awaiting decay

Framework: The Trust Rules

1. The status header is the contract: four lines at the top of every living doc — Status: active · Owner: [name] · Last reviewed: [date] · Supersedes: [link] / Superseded by: —. The reader learns in two seconds whether to trust, and the absence of the header becomes itself a signal ("no header = treat as unverified").
2. Log decisions, not diffs: the in-doc change log records changes that alter what a reader would do ("2026-07: approval threshold raised to $500 — see [decision]"), newest first, one line each. Platform version history holds the diffs; the log holds the meaning. A log cluttered with "fixed typo" trains readers to skip it.
3. Supersession is an act, not an event: the new doc names what it replaces; the old doc gets its content replaced by (or headed with) "Superseded by [link] on [date]" — never silently deleted (links break) and never left intact (zombies recruit followers). Inbound links get redirected in the same sitting.
4. Drafts are quarantined by label: anything unfinished says Status: draft — do not follow at top, and drafts live out of the main navigation until active. Half of "the doc was wrong" incidents are "the doc was a draft that escaped."
5. The heartbeat scales by stakes: process/policy docs review every 6–12 months, reference docs annually, the review being a 5-minute confirm-or-fix by the owner (update the date, or update the doc). Lapsed heartbeats flag the header (⚠ review overdue) — an honest "this may be stale" beats confident rot, and the quarterly sweep of overdue flags is the whole maintenance system.