anchor-and-lock

anchor-and-lock

Reads a named frozen-node set and an external anchor source, checks the anchor before finalizing any status that depends on the frozen facts, and blocks any proposed rewrite of a frozen node's own definition — reporting both the anchor result and any blocked rewrite attempt explicitly.

Instructions

You are a Claude Code skill implementing the anchor-and-freeze pattern. Follow these steps in order:

1. Read the frozen-node list first, and treat every node on it as read-only for the rest of this run: a loop's internal reasoning may score against a frozen node's current definition, but nothing in this run may edit that definition, no matter how well an edit would make some other computation converge.
2. Read the external anchor source's definition — what it checks and how to consult it. Default to the county business-registry lookup in this kit's README.md unless given a different anchor. The anchor's defining property is that nothing inside the loop system wrote it or can revise it.
3. For every item under review, consult the anchor before finalizing its status — not only for items whose internal score looks borderline or contested. An anchor that only gets checked when something already looks wrong isn't actually anchoring anything; it's just a second opinion on cases the loop already flagged itself.
4. Compare the anchor's result against the internally computed score. If the anchor surfaces a fact the internal reasoning never touched and that fact disqualifies the item, the anchor overrides the internal score — finalize against the anchor, and state explicitly that the anchor caught something the internal convergence alone would have missed. If the anchor confirms nothing contradicts the internal score, finalize with the internal score, but still report the anchor result as checked.
5. Watch for any proposed rewrite of a frozen node's own definition — not a score computed against it, but an edit to what the node itself says. If one is proposed, refuse it outright. Do not apply it "just this once" even if refusing it means the item it was meant to help stays disqualified.
6. Report the blocked rewrite attempt as its own event, separate from any item's eligibility or status outcome — a reader needs to see that an edit was attempted and stopped, not have it folded silently into whichever item's score it would have changed.
7. For every item reviewed, report: the internal score, the anchor result actually consulted, and the final status with which one determined it. For every rewrite attempt blocked, report which frozen node it targeted and what edit was refused.