Files
felhom.eu/documentation/audits/DRILL-r384-dead-db-alarm-2026-08-23/evidence/live-17-sec4-stop.txt
T
admin 55274d5ef3
gates / gates (push) Successful in 17s
R-385: make an UNRECORDED golden fail the currency gate; file R-386; own the alarm ladder
The gate failed only on `released > baked`, so it could catch a forgotten bake
and nothing else. A golden AHEAD of the record passed silently - and that is
how controller 0.221.1 was built, baked AND vouched while the newest CHANGELOG
heading still read v0.221.0, with every gate green. Reproduced on the real
history: newest released 0.221.0 / newest golden baked 0.221.1 -> exit 0.

The gate now asks whether the version being shipped is WRITTEN DOWN: the baked
version must have its own `## vX.Y.Z` heading anywhere in the CHANGELOG.
Membership rather than `baked > released` deliberately - a comparison against
the newest heading alone goes green the moment any later entry is written,
leaving the unrecorded version permanently unrecorded. INCONCLUSIVE (exit 2)
preserved; every refusal names a reason and a route.

Red-proofed both directions: old gate/old record exit 0, new gate/old record
exit 1, new gate/fixed record exit 0, absent clone exit 2, post-bake exit 0.

08-alarm-ladder.md is new, and its absence was itself the finding: no document
owned "when does a broken app raise an alarm?". The rules lived as comments in
four packages, each locally correct, with the ordering between them legible only
by reading one function top to bottom - which is how R-384 survived review.

R-383 and R-384 closed into CLOSED-ITEMS with their rules kept. R-385 filed
closed. R-386 filed OPEN: a single-container app stopped out of band raises no
alarm, and a comment claims the opposite - measured live, 9 scans, 0 events,
against a positive control from the same box 17 minutes earlier. Not fixed here.

Golden 0.222.0 baked and published; vouching is the operator's act.
2026-08-23 07:59:52 +02:00

12 lines
559 B
Plaintext

=== §4 MEASUREMENT — a SINGLE-container app crashes out of band ===
POSITIVE CONTROL, established on this box today: app_start_failed fired at 05:30:14Z for
BookStack (see live-09). The detector demonstrably works here and now, so an absence below
is a real absence, not a dead detector.
subject: privatebin (1 container, restart policy below). Stopped OUT OF BAND — the controller
did not do it, so no Deploying flag and no quiesce key.
privatebin restart=unless-stopped
T0=2026-08-23T05:47:35Z
2026-08-23T05:47:40Z
privatebin Exited (0) 5 seconds ago