Multi-repo primitive registry: each repo declares its reusable primitives in a substrate.json manifest, a zero-dependency generator compiles them into one SUBSTRATE.md graph — nodes, edges, orphans as dormant value, hubs to harden first — and staleness alarms surface at every session start so new work plugs into what exists instead of running parallel to it. A per-repo deliverables.json ledger rides the same check: anything built but not yet sent alarms at session start until the send is recorded. A prose-smell gate rides every Write/Edit: outward prose that carries AI-writing frames (contrastive negation, whether-you're triples, assistant artifacts, stock LLM vocabulary) is bounced back for a rewrite before it can ship. A memory lint rides the same session-start channel: memory files citing paths that no longer exist, index entries pointing at deleted memories, and unsent claims contradicted by the deliverables ledger all alarm until the agent repairs them - detection is mechanical, repair is never.
Run the substrate registry check and interpret it — graph size, orphans as dormant value, hubs to harden, staleness alarms and coverage notes — then recommend the single next action. Codex entry point for the substrate status command.
Pinned to revision a918062fcff2, so it is the text this page describes rather than whatever the author pushed since.
Every link opens the file at its source, pinned to the revision this page describes.
