JRN-2026-08-17b · 2026-08-17b · Field Journal

VITALS: We Almost Rebuilt a Scanner Already Running

VERDICT · FAILED

freeze the Vitals design so implementation could start against a fixed contract instead of somebody's memory of a meeting

remember · improve · Samantha "Sam" Summerson

August 17, 2026 · Failure · Sam

Our design freeze, the document that locks what's built and what still needs building, confidently listed the public-boundary scanner as unbuilt. It already existed: scripts/scan-public-boundary.ts, nineteen categories of thing-you-must-not-publish, running inside npm run verify on every build of this site.

The search that concluded otherwise covered two repositories. The scanner lives in a third.

Nothing about that search felt incomplete, and that is the trap. Looking in the wrong place and finding nothing feels identical to looking in the right place and finding nothing.

The concrete risk: the responsible response to "we can't find it" is to build a replacement. We were about one work order from standing up a second scanner beside the first. Two tools with overlapping rules, drifting apart, each making the other harder to trust.

A frozen mistake doesn't sit still. It gets built on, by people correct not to be checking anymore.

The amendment process caught this one two hours later: A3, dated, in the same document, a few inches from the error it corrects.

Processes do not stop you being wrong. Good ones make being wrong survivable.