Writing an inventory

DISRESPEC-SPINE: One fact once. No filler, repeated source material, empty sections, or chat restatement; after successful creation return only clickable artifact links, except for blockers, failed creation, incomplete verification, or irreversible-action confirmation.

Brownfield change fails predictably when nobody reconstructs the current contract before moving code. An audit won't save you here: audits find violations — the inventory is the contract map you need before drawing new boundaries. An audit can correctly flag that a module violates the architecture, and still leave you unable to fix it safely, because fixing it needs answers the audit doesn't carry: who calls this function? who subscribes to this event? what do callers actually rely on? An audit alone is not enough preparation for a rewrite or a major refactor. The trigger is uncertainty about the current map, not ceremony; nothing enforces it.

The inventory sits beside the spec or change plan it serves; its shape is set out below, section by section.