Blog
Why specs need versions, how coding agents should read the docs you actually ship, and what a dependency graph is worth once CI maintains it instead of a person.
RSS feedA dependency graph maintained by hand is a graph that is wrong. Reconcile it from a merge to the default branch, record the blob sha, and let a breaking change fail the build.
Pasting a spec into a prompt is a copy that goes stale in an hour. An MCP server that speaks your scope model lets an agent read the current version, one section at a time.
A wiki page has one state: current. An API contract has as many states as there are things built against it. Versioned documentation is what closes that gap.