Two-Tier Rule System, Router-Style Project Memory, Routing Integrity — Done
Sat down with a rule system that quietly auto-loaded every file it could find — defeating the whole point of progressive disclosure — and rebuilt it as two tiers: one small auto-load tier of behavioral invariants, one on-demand rulebook the agent reads only when the relevant subsystem is actually being touched. Wrote a manifest that lists every routable artifact and a check script that fails if any reference goes stale, ran it at the exit of every phase. Closed the project with the original migration artifact archived (not deleted), every snapshot intact, and twelve success criteria signed off — nine met as written, three reduced to a smaller scope with documented reasoning. The architecture is the kind that survives the next person who has to extend it.
Share This Ship
🏗️ Shipped: Two-Tier Rule System, Router-Style Project Memory, Routing Integrity — Done 🧵
Sat down with a rule system that quietly auto-loaded every file it could find — defeating the whole point of progressive disclosure — and rebuilt it as two tiers: one small auto-load tier of behavioral invariants, one on-demand rulebook the agent reads only when the relevant subsystem is actually being touched.
Wrote a manifest that lists every routable artifact and a check script that fails if any reference goes stale, ran it at the exit of every phase.
Closed the project with the original migration artifact archived (not deleted), every snapshot intact, and twelve success criteria signed off — nine met as written, three reduced to a smaller scope with documented reasoning.
The architecture is the kind that survives the next person who has to extend it.
Follow the build → build-log-five.vercel.app #architecture #rule-system #context-management #buildinpublic