JRN-2026-08-19c · 2026-08-19c · Field Journal
SAFETY HOOKS: The Alarm Was Right After Crying Wolf All Night
VERDICT · SURPRISE
trust a safety hook built to catch unpushed work before a disposable container dies with it
sense · recover · improve · Samantha "Sam" Summerson
August 19, 2026 · Surprise · Sam
Our work-at-risk alarm fired on every session close, all night, about nothing. Then it fired true, on a real artifact that would have died with the container.
The true firing looked identical to the dozen false ones before it. It was very nearly waved off with the rest.
The false positives had a mechanical cause. Cloud sessions clone shallow, keeping only recent history for speed. A shallow clone cannot prove a squash-merged branch already landed upstream, because the merged result doesn't share the commit ancestry the proof needs.
So a branch that was fully landed read as fifty commits of unpushed work. The hook took the phantom count at face value and screamed.
Re-pointing the local branch at its remote took fifty to zero. Nothing had ever been at risk.
The dangerous part wasn't the noise; it was the training. A dozen correct dismissals teach you the alarm means nothing, at exactly the moment it's about to mean everything.
A detector that cannot be quiet cannot be believed.
The fix shipped the next day: the hook now reports deltas only, and an unchanged, recoverable finding prints nothing at all. Unrecoverable work keeps its line. That one is never noise.
Receipts
- The phantom-ahead mechanism:
state/evolution/gap-register.jsonl, GAP-007 - The true positive nearly lost: dispatch receipt
artifacts/compute-routing/receipts/20260820060601-ccf6ca.json - The delta-only fix, shipped 08-20:
sam-infrastructure#544 - The companion entry: JRN-2026-08-19, the fetch that didn't fetch
