Keep a WAD current

§ 1Purpose

The maintenance sweep that stops the document drifting from reality.

§ 2Prerequisites

• A populated WAD with a recorded baseline

§ 3Flowchart

§ 4Steps

Run the sweep when something meaningful lands: code merged, infrastructure changed, a decision made, an incident that revealed the doc was wrong.

just extract (or just wad-extract in the WCL repo) — generated data re-derives from the live sources; the git diff of data/generated/ IS the machine-visible drift.

wcl diff <baseline>:wad.wcl wad.wcl — read what moved. Update the hand-authored blocks the changes invalidate (a renamed crate's relations, a retired container's deploy targets).

Have an LLM read the git log since the last sweep and list what changed that the WAD hasn't caught up with — renamed modules, new services, retired jobs, decisions visible only in commit messages. Commits are the change log the document must answer to; extractors only cover the machine-derivable slice.

Anything decided since the last sweep becomes an adr now, while the context is fresh. New operational learnings update the SOPs.

wcl check, render, and have the owner spot-check the affected chapters. Commit; if the sweep was substantial, record a fresh reviewed baseline.