scaffold-with-expiry

Every ceremony you add must carry its own removal condition.

2 · The failure it offsets

The lab’s process grew a ritual a week — checklists, advisory warnings, extra review passes — each added in response to a real incident, each permanent by default. Six weeks in, nobody could say which rituals still paid rent. Removing one felt like tempting fate, so none were removed. Process only accumulated, and the friction compounded quietly while the incidents it was bought to prevent stopped happening.

3 · The rule

When you add a ceremony — a checklist, a warning, a gate, a manual step — write down, in the same change, the condition under which it is removed or promoted. The condition must be observable: a count, a date, an event — never a feeling. Review a ceremony when its condition fires, not on a schedule. A ceremony with no expiry is a bug.

4 · Adopt in an afternoon

Add a retire: line to whatever file already defines each ritual. The lab’s advisory checks graduate to blocking on numbers, not vibes:

steal this

# hooks.conf — every level line carries its ladder
LEVEL_PII_GUARD=warn
#   promote to block: N>=25 commits observed AND FP<=2 AND FN=0
#   (any FN resets the count to 0)
#   retire: superseded when the blocking mode has held for a quarter

The numbers are the point: N≥25 observations before you trust a check, FP≤2 false alarms tolerated across the window, and a single missed violation (FN=0 is the requirement) resets the count entirely. Steal the shape, tune the constants.

5 · The refusal test

You know the pattern is working when the deny path observably fires: at review time you can point to a ceremony that was actually removed or promoted because its written condition triggered — not because someone got tired of it. For gates, prove it live: plant a violation, watch the commit get refused, then delete the plant. A guard nobody has ever seen refuse is a guard nobody knows works.

6 · Retire trigger

Retire scaffold-with-expiry itself when your ceremony inventory is small enough to review in one sitting — about five or fewer. A list that short does not need per-item expiry logic; the pattern’s overhead would become the very ceremony it exists to prevent.

captured 2026-07-19 · v1 · stolen from Buddy Lab · CC BY 4.0, snippets MIT