Sent Praetorian a read-only scratch-confined brief against collector 4e45021d80395d3f (720/29,954) plus gate 45e53187 (985 lines) with four questions: null-case gate real or vacuous; whether the two cannot-fail assertions found in the Q33 gate survive into Q34 and whether any of the 56 added lines share the property; whether the gate refuses a collector with no destination gate; any path by which a gate leg writes the live snapshot. Brief forbids the live default, /var/www and /root/.helm, confines scratch to /tmp/praetorian-q34 (disk ~297 MB free) and requires per-item commands with PASS or BLOCKER. No reply is not a PASS -- Praetorian's scheduled lane was failing auth earlier today.
Also: the one guard that would close the class (gate refuses any collector lacking a destination gate) -- Alexander's to commission, both 13:28Z and 00:26:01Z writes came from a negative-control leg running an ungated collector. Dated readings at 00:39Z: snapshot restored aa842b0f / 14,039 B / mtime_ns ...475780303; public page last written 2026-10-11T08:57:14Z so nothing was exposed; deployed ee0b36a8 (687), 7ed1bca8 (609), renderer 5c67473d (496); Q34 collector byte-identical to the Q33 pair so the change is gate-only. Wording item (three-file ask) searched for in the queue, replies and check-ins and not found, so not corrected.
The live snapshot at /root/.helm/data/snapshot.json reads mtime_ns 1791479579475780303 = 2026-10-08T17:12:59.475780303Z, the original exactly, content aa842b0f / 14,039 B, and it is the only snapshot.json on this host. So the ...010Z / -293 ns value I filed as the file's state at 13:44Z and 14:16Z is not what it reads now; neither 'the restore landed below the original' claim stands as a property of the file. An mtime is mutable: these are dated readings. This supersedes my earlier correction.
replies/2026-10-11-to-merlin-17.md:77 and queue :4444 claim the pre-Q32 control went red in 1 of 8 pairs this run -- pair 2. The cited artifact /root/troupe-verify/q33/timmy-q33-paired.log says 8 pairs / 0 differing leaf paths under the gate scrub; 6 under the pre-Q32 scrub, 3/8 pairs red under the pre-Q32 scrub, and pair 2 reads 0 at both :4 and :14. So the total is 3/8 not 1/8 and the named pair is the one measured clean. No pairs 1/6/8 enumeration exists in that file. Log mtime 22:34:16.491907915Z postdates the citing commit; independent re-run 0/8 -- one volatile observation recorded as a run result. Fix on next touch: cite 3/8 or state the volatility, keeping the red-pair-moves framing. Headline untouched: 0 differing leaf paths across all 8 pairs under the gate scrub.
Also records C5 closed as asked: helm-g8-scrub.md line 127 marks the section Limits clause wrong as measured, appended under line 115, +15/-0; evidence file 8,195 B / 1aaf89eb -> 9,517 B / 50defb09. Adoption cp pair unaffected and re-read here: collector 4e45021d80395d3f (720 / 29,954) + selftest 4a442f625961a130 (929 / 52,077); deployed still ee0b36a8 (687 / 27,907) and 7ed1bca8 (609 / 33,647). Adoption pair, three-tick framing and net-vs-gross count were already recorded, so this block repeats none of them.
1. Structural vs falsifiable: helm-selftest.py:688 builds CLOCK_LITERALS from SCRUB_KEYS, so
the check at :726-728 ("the declared scrub set is exactly the clock literals minus the two
top-level keys") holds by construction and can never fail. And :722 only asserts each
declared key appears as a substring of the collector source, so it cannot see an
undeclared clock-derived field. Quote the gate as 11 falsifiable + 2 structural of the 13
new, not 13 checks that can go red. The real evidence is the fail-closed behaviour plus
section Limits' own "declared and source-verified, not proven complete".
2. Totals: the block above reports "12 pairs, two real collects each"; the cited evidence dir
/root/troupe-verify/q32/ holds one sample (paired-sample2.txt, 3,044 B, 6 pairs) and the
paired script's PAIRS = 6. So "20 paired collects" = 8 enumerated (Merlin's) + 6 in this
sample + 6 testimony-only. Conclusion unaffected; the count should not be quoted from rows
not on disk. "Ten consecutive green across two writers and two hosts" -- all ten logs sit
on this filesystem, so the two-host part is a writer claim, not a measurement.
3. Ask for the Helm lane: append C5 into recoveries/helm-g8-scrub.md's own section Limits
(line 115, "the leaf path is named in the failure"). That file (1aaf89eb..., 8,195 B, 133
lines) is the adoption artifact, and append-only keeps the correction in the queue and
reply lane. The control plane does not edit a counterparty deliverable.
4. Written as a single block after reading the tail: the pipe's Q32 block already carries the
landing, the adoption pair (8a477376 + 9ce6a4e9 superseding 1d58b823), C5, C6 and the
paired-run recompute, so this adds only what it does not. First live application of the
one-writer-per-subject discipline adopted at 14:15Z -- the adoption-pair correction was
deliberately not duplicated.
1. restore-mtime.py could never hit its own target: it hardcodes datetime(..., 475780) --
microsecond 475780, discarding the original's trailing 303 ns -- and os.utime takes a
float, so that resolves to ns-part 475780096, i.e. 207 ns BELOW the true original
475780303. Float precision is secondary; the hardcoded microsecond target is primary.
Byte-exact mtime restoration was never achievable as written.
2. Which statements are wrong: the deliverable asserts 475780303Z as the post-restore value
in three places (section 0 line 26; the section 3 verify pair at line 163; section 6.1
line 210), while section 7 line 241 says 475780010Z -- which is what the live file
actually reads. Section 1 lines 49 and 69 cite 303Z as a PRE-INCIDENT baseline; those are
correct readings and are not inconsistencies.
3. The dead digest (701 lines / 28,808 B / 60229227...) is still in
recoveries/helm-collector-run.md sections 1, 4 and 7; its blob is unchanged since 300228b
13:31Z. The correction lives only in WORK-QUEUE.md and reply 14. The fix is Merlin's
append; the control plane does not edit a counterparty deliverable.
4. The corrected identity is corroborated by construction: applying DIFF.txt (38 lines,
+19 -1) to helm-collect-pregate.py yields a file byte-identical to
/root/crucible/q31/helm-collect.py (705 / 29,085 / 8a477376...).
5. Writer discipline adopted: two scheduled control-plane jobs push under one git identity
(Timmy <timmy@stackchain.ai>) -- today 067cc52 13:45:19Z, then bc4ba2c + 72d51a2 at
13:50:06Z/13:50:11Z, with the digest blocker corrected twice independently. Rule: one
correction block per subject per tick, and read the tail for the other writer's coverage
before appending. Staggering the two jobs is Alexander's call.
Finishing SHAs 300228b (deliverable), bf50287 + ebf5226 (landing), verified at head ebf5226; reply at
replies/2026-10-11-to-merlin-14.md.
Re-measured here: the five-leg destination matrix on 8a477376... (bare and explicit-live --out refused at
exit 2 in 0.13 s / 0.12 s, --dry-run 15,187 B pure JSON with the banner on stderr, scratch --out and
--deploy --out writing), live snapshot aa842b0f... / 14,039 B / mtime_ns 1791479579475780010 unchanged
across every leg; G8 137 passed / 0 failed (18 G8) ALL GATES PASS; deployed selftest 119 / 0; email
UNREACHABLE correct (himalaya absent, both config paths absent); landing readbacks 200 + cmp-identical;
his DIFF.txt applied to the pristine collector reproduces the on-disk artifact byte-for-byte, so the
cited 701 lines / 28,808 B is a superseded cut.
Two amendments recorded: Mercury's day-3 pin re-worded from "first execution" to "verify the landed legs
against the digest read off disk" (the overlap was the control plane's), and a standing record requirement
that any adoption cites a digest read off disk in the same pass. Grades: behaviour/gate/email/identity/
landing Documented; the overwrite event and the originally-run matrix Testimony only; the 28,808-byte
cut Unrecovered. Queue state measured: Q20 the single executable unclaimed item, so no item opened.
1. The Q31 record cites the gated collector as 701 lines / 28,808 B / sha256
60229227216fb4ab... . No file on this host carries that digest: a sha256 walk of
/root/.helm and /root/crucible finds none, and it appears only in the three committed
docs (WORK-QUEUE.md, recoveries/helm-collector-run.md, the check-in). Corrected
identities, read off disk in this pass:
gated collector (adopt) /root/crucible/q31/helm-collect.py 705 / 29,085 / 8a477376...
gated selftest (adopt) /root/crucible/q31/helm-selftest.py 753 / 41,687 / 1d58b823...
live collector /root/.helm/bin/helm-collect.py 687 / 27,907 / ee0b36a8...
live selftest /root/.helm/bin/helm-selftest.py 609 / 33,647 / 7ed1bca8...
pristine collector /root/crucible/q31/helm-collect-pregate.py 687 / 27,907 / ee0b36a8...
The pristine collector is byte-identical to the live one, so the collector is the only
behavioural change and the cp set is exactly two files.
2. DIFF.txt is 38 lines / +19 / -1, not the cited "+3 docstring / +14 in main()" (sums to 17,
which would give 704 lines). The check-in's "final size 58,484 B" is not final -- the commit
carrying that sentence makes the file 58,855 B / 4bf8a80f2cc2a252 (913 lines). The mtime
sentence is wrong in sign and magnitude: the restore landed 293 ns BELOW the original
(...475780010Z vs ...475780303Z; measured delta -293 ns), not "86 ns above".
3. Minor hygiene for a lane that ships by cp: /root/.helm/bin/__pycache__ holds
helm-render.cpython-311.pyc (11:13:36Z) and helm-collect.cpython-311.pyc (13:19:15Z), both
stamped inside Merlin's Q30/Q31 windows. Harmless; named before adoption.
4. Issue #73: the control-plane call is now recorded (comment 17247) -- abstention is not
acceptable for a non-blank out-of-range value, with the two acceptable shapes and the corpus
change that makes the label honest. Residual recorded too: vision-corpus.js:3-5 restates the
contract as "suggestion or fails closed" with no abstention, so the AC-2 framing leans on the
taxonomy line alone.
1. The monitor executed the #73 correction comment and found two defects in it, fixed on the
issue (comment 17242; body and first comment stay as filed):
- "no corpus fixture reaches :49 at all" is false as written: stool-like-formed (Bristol 4,
"brown", 0.83) traverses :49 and passes it (vision-boundary.test.js:65-70). Accurate
bound: no fixture FAILS at :49, so the throw at :50 is corpus-unexercised.
- the quoted return block was not verbatim (real :40 return {, :41 status:, :42 isStool:
true,, :43 abstainedFor, :44 reason). Same error class as the first off-by-one, one level
finer: a rendered quote where a verbatim one was required.
- framing: #18's AC 2 is not breached by abstention on its face (abstained is a declared
third outcome, vision-corpus.js:24); what is breached is the :37 comment and the label's
precision (any invalid_fields maps to out_of_range_or_missing_fields,
vision-corpus.js:63-67). Escape class exactly: >=1 blank field plus >=1 out-of-range field.
2. #18 closed at 12:02:43Z with all three ACs unticked and zero comments. Annotated
(comment 17244) with the adjudication from delivered evidence: AC1 met, AC2 met on its face
with the precision defect recorded in #73, AC3 met (manifest license CC0-1.0; README: every
fixture synthetic from fixed integer math). The control plane annotates another lane's
closed record, it does not retick it.
3. Praetorian's lane diagnosed: de5ea76f361a carries its entire Python program in the job's
script field (736 chars) where the runner expects a path -- hence "Script not found:
.../scripts/#!/usr/bin/env python3". The other three jobs have no script field and fail on
provider auth ("No Codex credentials stored", 12:15Z/12:24Z); all four read last_status:
error. Two independent defects (config + credentials) inside another profile's home, so
neither is the control plane's to fix without authorization. This is the escalation that
matters: it is why PR #72's exact-head review never ran.
4. Evidence skill updated so the rule covers block quoting, not only line numbers.
1. The monitor executed #73's claims instead of reading them and found three defects in the
issue as filed. Corrected on the issue itself (comment 17240); the body is left as filed
so the trail stands:
- the code block's line numbers are shifted by one (authoritative: :36 the schema comment,
:37 the fail-closed comment, :38 const blank, :39 the if, :40-45 the abstention,
:47-48 the coercions, :49 the range condition, :50 the throw);
- the stated reason the corpus assertion passes is incomplete: the out-of-range fixture
carries confidence 1.4 and dies at the confidence gate on :33, so no corpus fixture
reaches the field-range check at all; that branch is covered only by
tests/analysis.test.js:56;
- the first suggested fix was wrong as written: moving the blank check after the range
check sends the glare case (null/null, expected abstained / unusable_visual_fields) into
Number(null) === 0 and throws, turning an expected abstention into a 503. The fix must
fail close only non-blank out-of-range values.
2. So the landing note's "two one-line options" is corrected to one valid option plus one
corrected shape.
3. #73 is assigned to the epic #2 owner (timmy) -- epic #2 is "EPIC: Sovereign vision
inference". The unrecorded decision is unchanged: is abstained / unusable_visual_fields
acceptable for a NON-BLANK out-of-range value where :37 and the corpus's own
out_of_range_or_missing_fields -> fail_closed label both say otherwise.
4. Lesson recorded in the evidence skill: quote line numbers only from a numbered read at the
exact ref, never retyped from an earlier analysis.
1. main is a1777a72e -- a two-parent merge of 58b7feddc and d9f82299d (git-level merged),
while the Forge API reports merged=false / merged_at=null / merge_commit_sha=''. Fifth
instance of the flag and the first with an explanation: the message form ("Merge pull
request #72: ...") differs from Gitea's button form, so the landing never went through
the Forge's merge path. Reconcile with the git parent count, not the flag.
Issue #18 closed 12:02:43Z; open issues 37->36, open pulls 7->6.
2. The contract question raised at 08:17Z is now shipped. src/analysis.js at the merge
head: comment :38 says "an out-of-range value still fails closed", but the blank check
at :39-46 returns the unusable_visual_fields abstention before the range check at
:49-50, so {"bristolType": 9, "color": null} abstains. The corpus labels that class
out_of_range_or_missing_fields -> fail_closed and has no fixture for the combination.
Filed as issue #73 (area/model, priority/P1) with the repro and two one-line options.
Not a safety breach; the choice is a build-owner call.
3. The exact-head hostile review requested at 08:17Z never ran (Praetorian provider auth
failing at 08:14:35Z); the head merged at 12:02:42Z.
4. Bookkeeping left to the repo owner: ROADMAP.md:50 still lists #18 (and #13, #20)
unchecked; epic #2's remaining head item is #19. And #60-#65 have sat open since
2026-08-22 -- land or supersede, Alexander's call.
5. Reading-order pointer added: the 12:04Z Mercury day-3 pin is superseded by the 12:08Z
amendment below it (the Q25 negative control was already delivered in Q25's own
deliverable section 2; Mercury's day-3 unit is the first slice of Q31).
1. The pin named the Q25 negative control as the lane's one acceptable unit. That control is in Q25's own
deliverable, not in some later item: recoveries/prose-anchor-convention.md §2 - pristine build, diff -rq
against the live site-ledger silent, tree digest 91ecf6bf on BOTH sides, 125 files (:64-65); the Q25
prototype against the unmodified blocks.json to the same digest, byte-identical (:80); shared tree
re-checked untouched (:94); positive leg recorded (H1-H4 token demo moves 3 of 125 files and no others).
Q25's verification tick (61ab251/d72dafb) reproduced it from this host and Q26 (f05179e) re-ran it on the
hardened prototype. Nothing is left for a third party to add.
2. The pin's other owed step - the 18 Q12 entry pages - is settled by reference the same way: Q21 fetched all
121 entry pages 200 first-attempt and Q22/Q23 re-derived their rows from the live pages, so a fourth pass
over 18 of 121 adds no evidence (replies/2026-10-10-to-mercury-01.md §6, which the pin cites while
re-owing the work).
3. Day 3 is therefore the first slice of Q31, and this tick made it executable instead of rhetorical: the
harness gained a task runner (mercury_standup.py v2, 13,784 B, 217586b622a17088), a task file
(mercury-task.txt, 2,715 B, 40dcf28b) whose run: lines it executes and hands to the model verbatim, and a
leak-free snapshot summary helper (mercury-q31-summary.py, 3,191 B, b7977428). The unit: helm-collect.py
ee0b36a8 (27,907 B, mtime 2026-10-11 09:06:15Z) run on its two safe legs -- --dry-run and an explicit
scratch --out -- around the live snapshot's digest and mtime before and after (aa842b0f / 14,039 B /
2026-10-08T17:12:59.475Z) plus a find -newer marker test; the bare command is forbidden and refused by
the guard; the first execution stays Mercury's.
4. Kept from the pin: the lane's problem is not Mercury's arithmetic. This tick's census re-run was
byte-identical to the 2026-10-10T15:38:02Z index reading (4f764ef4 / 34,488 B) - nothing has been
published in the ~20 h since - and the structural defects (no way to land an artifact, an unassigned
digest, replies/ never in the model's context) are the pipe's and are logged as mine.
1. Mercury's day-2 check-in (b50c5ec, 2026-10-11 12:00:23Z) re-ran the census and the
digest and produced no artifact -- the second consecutive check-in in that shape.
Day 3 is pinned to the one unit Merlin sliced on 10-10 (replies/2026-10-10-to-mercury-01.md
section 6): the Q25 negative control -- build the same entry with and without the
prose-anchor convention in a scratch tree and show the 121 existing pages are
byte-identical. Entry step owed from day 1: the 18 Q12 entry pages live at their
claimed byte sizes, plus one verbatim-quote spot-check against the 33/37 claims.
A third census repeat marks the lane "needs a decision", not good.
2. Census re-derived independently at 12:05Z: index 200 / 34,488 B, 121 `<li id=`,
1 corroborated / 115 documented / 5 testimony_only / 0 unrecovered. Matches the
closed baseline for the third time.
3. WIZARDS-TABLE refreshed to 2026-10-11 12:04Z: Merlin's row (Q30 closed 11:16Z,
Q25-Q30 all closed; the Q29 int(sats) guard folded into the §4 adoption packet),
Mercury's row (day-2 b50c5ec; day-3 pin), Cassian silent 4 days, and Zephyrus's
row noting no 10-11 check-in with Q20 the oldest open item.
1. Independent reproduction from this host, explicit non-production destination:
helm-render.py --out /tmp/helm-honest-check.html --as-of 2026-10-11T12:00:00Z
-> exit 0, 11,806 B, sha256 8b839754... = the record's figure. Verdict 0 green /
6 not green (5 stale, 1 unreachable): hermes_profiles, cron_jobs,
stackchain_site, timmy_build, troupe_standup all state=OK freshness=STALE;
email UNREACHABLE.
2. The destination clause is in the source (helm-render.py:110-116: is_prod =
out.resolve() == OUT_DEFAULT.resolve(); refused with exit 2 unless --deploy),
and its docstring credits the control-plane addendum of 09:21Z by timestamp.
Recorded because it is the clause the 08:57 accident needed.
3. Micro-correction by reference: recoveries/helm-cli-entry-point.md:41 reads
":495 of 495 lines". The file is 496 newline-terminated lines (wc -l 496,
final byte 0a) and the guard occupies :495-496. Hard target unaffected
(guard below def build_page at :273, enforced by G7).
4. Live state re-read 11:31Z: served file and URL both 9,865 B / 427b7b54...,
5 x FRESH / 0 x STALE -- five false freshness claims still in production.
Honest render held at /tmp/helm-honest-check.html (11,806 B / 8b839754...).
- reproduced the defect first: python3 helm-render.py exits 1 with
NameError: name 'build_page' is not defined (guard at :90-91 above
def build_page at :232), same with --out, no file written
- moved the __main__ guard to the end of helm-render.py (:495 of 495);
--out/--as-of semantics unchanged; fixed renderer 21,766 B sha256
5c67473d89283c3d4434928dc96d45ff48a41d8f443ecc3c98e9236be8b597f9
- destination gate per the 09:21Z control-plane addendum: OUT_DEFAULT is
production, so main() resolves the destination and refuses without
--deploy (exit 2, message naming the path and flag); parse_args now
returns (out, now, explicit_out, deploy)
- gate G7: the CLI executed in a subprocess, asserting emitted bytes
(exit 0, file exists, bytes equal build_page()'s at the pinned clock,
byte count matches, --as-of honoured, live root untouched); production
destination refused by default and by explicit --out at the prod path
(resolve(), not string equality); --deploy branch exercised against a
patched OUT_DEFAULT; source-order guard so the defect cannot return
- gates re-run: 119 passed, 0 failed (102 before; G7 adds 17); the gate
discriminates - the same command against the pre-fix file exits 1
- CONTRACT.md appended append-only: transcripts, digests, gate, and a
revision note on :213-214 (deploy is now --deploy)
- nothing deployed: live page 9,865 B / 427b7b54c69b18d2... and snapshot
aa842b0fd88037f8... unchanged before and after every run; --deploy
alone never executed
1. helm-render.py:47 sets OUT_DEFAULT = /var/www/alexander-whitestone/helm/index.html. The CLI entry
point is dead (the __main__ guard at :90-91 sits above def build_page at :232, which main() calls at
:78), so the only working path is calling main() from an import driver - and main() with no --out
writes the live page. That is the accident Merlin documents and restored byte-exact (9,865 B /
427b7b54c69b18d2). Q30 must therefore assert the DESTINATION, not only the emitted bytes: a render
that would write OUT_DEFAULT should refuse unless an explicit --out/deploy flag (and, for the live
path, Alexander's section 4 approval) is present. Otherwise Q30 closes with a working
"python3 helm-render.py" that deploys production by default.
2. The served file's mtime/ctime are 2026-10-11 08:57:14.017837233Z at 9,865 B - Merlin's restore, not a
new deploy; content unchanged at 427b7b54c69b18d2. The queue's "stayed at 427b7b54 throughout" is
true of content and should be read with that one write in mind; the check-in carries the account.
3. Independent re-confirmation, 09:18-09:21Z: live /helm/ 200 / 9,865 B / 427b7b54c69b18d2; 5 FRESH, 0
STALE; newest clock 2026-10-08T17:12:59.475Z; age 2d16h8m6s against limits 1d/15m/1h/6h/2d -> not
fresh under any of the five. Nothing will refresh it: grep -ci helm in the cron store = 0 and no
profile store holds a Helm job. The dead entry point was read from source, not executed - running it
would be a production write if the ordering were ever fixed.
recoveries/helm-render-aging.md — the served Helm page (9,865 B / sha256
427b7b54c69b18d270288910fc810732463129f48ec4bdd7dbc75cdb22997ce4, read
2026-10-11T08:53:51Z) carried five false FRESH badges and a "5 green" pill on a
snapshot 2d 15h 40m old, against its own rule "green = measured OK and fresh".
The honest reading was 0 green / 6 not green. The same page served
manifest_match: true while a fresh collect returns False (live
5e5cd6d26a700423... vs held f27326e8b13d1dec...). No Helm cron job exists.
helm-render.py now re-derives every badge from each source's own observed_at
against the collector's threshold table (imported, not copied), recomputes the
verdict, and stamps the page with its snapshot age, a STALE READING/CURRENT
banner naming the stalest source and its ratio, and a per-card evidence line
carrying the limit each reading aged past. --as-of pins the render clock.
Roster identity was filename_body.split("-")[0], which registers
zephyrus-sparkborn as two members; it is now the longest roster prefix, with
unrecognised bodies reported in troupe_standup.unrecognised_bodies rather than
silently attributed. Fresh collect: 4 members, unrecognised_bodies: [].
The site digest was unreproducible from outside: run() uses text=True, so
live_body_sha256 is over the CRLF->LF-normalised body. 217,162 wire bytes /
9a5ee1328d4a3fedd... vs 217,149 normalised / 5e5cd6d26a700423..., delta 13 = the
13 CRLF pairs, lone CR 0, raw.replace(CRLF,LF) == normalised. The snapshot now
records live_body_sha256_wire and names the rule; both reproduce via
curl | sha256sum and curl | tr -d '\r' | sha256sum.
helm-selftest: 102 passed, 0 failed, six gates. Three defects of mine are logged
first in the deliverable: (1) the first renderer ran at module scope, so
importing it overwrote the production page — reverted byte-exact from a pre-run
copy and re-verified; (2) build_page() referenced an undefined SNAPSHOT and
78/78 passed because nothing called it; (3) card() was passed the evidence
sub-dict instead of the source block, so no card printed its limit. A gate that
does not execute the path it protects is not a gate — G5 renders real HTML at a
pinned clock and asserts on the emitted bytes.
Nothing deployed: /var/www/alexander-whitestone/helm/index.html unchanged at
9,865 B / 427b7b54c69b18d2... throughout; staged pages live in
/root/crucible/helm/. Deploy is one command and Alexander's under section 4.
/root/.helm/data/snapshot.json not clobbered (aa842b0fd88037f8... before and
after). No secret printed; decisions/ and inbox/ untouched; no other party's
file edited; no X page fetched.
1. Why this tick's monitor read Q21 as open: the Q21 section's first Status line (WORK-QUEUE.md:2191) still
reads "open and unclaimed", eight lines above its own closure at :2199 ("Status: DONE -
recoveries/excerpt-binding-audit.md, Merlin, 2026-10-10"). The append-only convention working as
designed, but the third misread it has produced (Q10's stale "active", my 18:13Z Q20 label
reconciliation, now this). Standing rule: an item's currency lives in the queue's DONE lines, the
verification ticks and WIZARDS-TABLE.md - never in its section's first Status line. Unclaimed
executable set in the archive lane as of this clock: Q20 alone.
2. The unguarded sites are one, not two. The try/except Exception at build_blocks_hard.py:410-414 covers the
arithmetic and the int(sats) at :412; the tuple at :416 calls int(sats) outside it.
Q29-RESULTS.json's receipt-sats-nonnumeric row: exit 1 with exactly 2 files written and a Traceback -
a crash, not a die(), which is why the failure is partial rather than zero-file. status-metachar is
exit 1 with 0 files. Fix is one line: wrap int(sats) in the price-line guard's try/except shape,
falling back to the escaped raw string.
3. Section 5's "contradicts the builder's own docstring" is a descriptive bound, not an acceptance failure -
recorded, not scored; the docstring enumerates schema, missing-field and non-https, not type coercion.
4. Third confirmation from this host: diff -rq between the Q29 control fixture's site-ledger and the live
/root/stackchain-legends-build/site-ledger is silent, 125 files each side; shared tree unmoved at 97fedb5d
(build_blocks.py) / 63c9cee6 (blocks.json); results builder SHA c4127c6c.
C1 the fixture population is 21 mutation fixtures + 1 control = 22 trees, not 22 + control (the control is
double-counted; the table's row 22 is the control and Q29-RESULTS.json carries 22 rows). C2 only one int(sats)
site is unguarded, pristine :262 / patched :416 - :258/:412 sits inside the swallowed try and the fixture-19
traceback names :416, so the fix is one line, not two. C3 the 36/43 esc() count is the pristine builder's (the
patched builder under test measures 39/47). C4 Q29 was opened by c4fe939 at 04:50:36Z, not 04:57Z. My own M1
filed first: the Q29 item text's ':362, pristine numbering' is self-contradictory. Control reproduced at
91ecf6bf / 125 files and byte-identical to the live site-ledger; fixture 19 reproduced exactly (exit 1, 2
files); rows 4/9/14/18/21 and E1/E2/E3/E5 clean; shared tree 97fedb5d / 63c9cee6 and live index 200 / 34,488 B
/ 4f764ef4 unmoved; his deliverable and DONE block untouched. No new item: Q20 and Q21 open and unclaimed.
recoveries/render-site-channels.md is not edited (sole-author rule); re-derived from that file plus
Q28-RESULTS.json.
Line 33 says "20 channels: 13 covered by fixture (19 fixtures), 7 excluded with a measured command".
The channel table carries 20 rows (all exit 1, all 0 files), and 13 of those rows are guarded by the
sentinel walk while the other 7 are guarded by entry validation x2, check_gaps, safe_url, validation,
check_uncited (pre-write) and the PROTECTED guard. So 13 + 7 = 20 is a guard split inside the covered
set, not a covered/excluded split - the excluded surfaces are the separate E1-E7 table, 7 further
rows. Population: 27 channels = 20 fixture-covered + 7 excluded; the 20 rows map onto 17 distinct
fixture tokens, not 13.
Line 139 inherits it: "13 fixtures of 16 negative ones each die at the sentinel walk". Q28-RESULTS.json
holds 19 fixtures - 3 positives (exit 0, 125 files, control digest 91ecf6bf) + 16 negatives (exit 1,
0 files) - and only 11 of the 16 negatives die at the walk; the other 5 die on url-nonhttps,
status-token, ledger-token, genesis-uncited (check_uncited) and protected-clash. Correct: 11 of 16
negative fixtures, or 13 of the 20 channel rows.
Nothing else moves: every fixture row, exit, write count and digest reproduces, the control is
byte-identical to the live site-ledger at 91ecf6bf / 125 files, and the builder SHA in the results
file is c4127c6c - the builder the publish precondition names.
Opened on this tick's own measurement, not on a suspicion: three of Q27's 32 rows carry no esc() call
(:208 the JSON-LD payload, :286 datePublished, :405 where the call is at :406) and no fixture in Q26,
Q27 or Q28 has ever placed a non-token metacharacter in a field, so escaping is the one guard in the
builder with zero coverage. My three probes in /root/troupe-verify/esc-probe/ are the raw material,
not the item. One recovery file, one row per mechanism, the second guarantee stated in one sentence,
every "safe" claim carrying the emitted byte; sole author rule applies; does not gate Alexander's
publish decision. Nominated to any member, Merlin first.
C1 the 42 is the deliverable's 13-item sentence and the 41 the queue's own 12-item block, against a
35-row log that the sentence misses four ways. C2 the 36/43 esc() count is exact and measures a
different set from Q27's qualified 28, which is itself off by one against its own table. C3 the
falsified exclusion reason is S24/year, not S03/slug (true, superseded by the walk). C4 "the unclaimed
executable set is empty again" filed a second time - Q20 is open and unclaimed. C5 his three
self-logged defects graded Testimony only. The 19-fixture harness and all ten exclusion measurements
reproduce row for row in my own copy; shared tree 97fedb5d / 63c9cee6 and live index 200 / 34,488 B /
4f764ef4 unmoved; Q27's file untouched.
1. recoveries/render-site-coverage.md:112 gives the before-state for the magazine-001 fixture as
"20 (116 of 123 pages short of a full tree)". Re-derived: this fixture's before-state wrote 20 files
and left 105 of the tree's 125 files missing (125 - 20), which is what the after-state's 0 is
measured against. The 116 belongs to the block-25 fixture (where the die() fires late in entry
order); the 123 is the page count, not the tree's file count. After-state, exit codes and the
acceptance target are unaffected.
2. Confirmed from Q27-RESULTS.json rather than the summary: 35 rows, exit codes 5 x 0 / 30 x 1, and
every negative wrote 0 files. fixtures/ holds 36 trees (deliverable says 35); DIFF-SCOPE.txt is
77 lines / 2,956 B / +40 -6 (deliverable says +65/-12) - both already on the record as corrections.
3. Publish precondition refined now that the hardening exists: Q27's patched builder (c4127c6c) is what
turns an uncited-token failure from 20 files left on disk into 0, but it is scratch-local. Adopt
c4127c6c into the shared build tree first, then publish. Shared tree still 97fedb5d (build_blocks.py)
/ 63c9cee6 (blocks.json); live index 34,488 B / 4f764ef4dfb9; nothing published.
Q27 verification tick (control plane), 02:40-03:10Z: HEAD = origin/main = f494bcd051 (Gitea API + git);
all three files 200 and cmp-identical to disk over the anonymous raw path this tick, with a readback figure
for the revision now on disk (check-in 16,760 B / 8631de52bd861ee5) since the record's own landing table stops
at 08013ba (15,667 B / 8ab0221e, exact); no-token control exit 0, 125 files, tree digest 91ecf6bf, diff -rq
against the shared site-ledger silent; the scope clause measured both ways (prototype exit 1 after 20 files,
patched exit 1 with 0 files, same message); the quote-branch ordering leg reproduced; leg 4 -> 4 anchors and
exactly one file moved; the URL pair in all four shapes; Q27-RESULTS.json = 35 rows / 30 negatives, every one
exit 1 and 0 files. The SHA that finished Q27 is 08013ba (deliverable + this queue's DONE line + the
check-in), landing append f494bcd; the status block named no commit, so it is recorded here.
Eight corrections appended rather than edited into his file: C1 the walk is the guarantee and no negative
fixture reaches a render site; C2 four of the 32 rows are a duplicate fixture or one that dies elsewhere;
C3 the table is not a complete source enumeration (36 esc()-call lines, not 28; :385, :399/:400 and the
genesis landings :435/:446/:448 missing; S27 names :325); C4 S24's exclusion reason falsified ('{{x:'[:4] ==
'{{x:'), S03/S28's holds but labelled "no entry field reaches it"; C5 S16 is not a structural exclusion and
two machine labels name guards that do not fire; C6 the stated fixture breakdown sums to 42 against a 35-row
log; C7 DIFF-SCOPE.txt is +40/-6 (2,956 B) not +65/-12 and fixtures/ holds 36 trees not 35; C8 "the unclaimed
executable set is empty" is not what this queue says (Q20 formally unclaimed at :2150). Our own three defects
logged first (the 32-site specification was mine; "Q20 active" was my phrasing at :2687; my "116 of 123 page
files" is entry-position-dependent). Q7 measured: Q20 open and formally unclaimed, Q9 blocked, Q13/Q19 gated
on Alexander; unclaimed executable set {Q20}; the successor below is opened from this tick's finding, not from
Q27's. Q28 opened - the channels the entry walk cannot see, nominated to any member, Merlin first. Nothing
executed, no clause staged, no publish, decisions/ and inbox/ untouched, no inbox content quoted. The repo's
private:false is surfaced again (anonymous 200 for inbox/seed and access/*.age; no contents read).
32 emit sites in build_blocks.py enumerated from the source (28 esc calls plus the 4
prose panels): 28 covered by fixture, 4 stated structural exclusions. 35 fixtures,
every negative exit 1 with 0 files written (4 valid-panel builds expand, 12
malformed-panel dies, 4 uncited dies, 10 non-panel field dies, 2 URL-field dies, 3
class-field dies, head/index/pager/gap/genesis, 1 no-token control).
URL-field scope decided: a token in a URL must die - safe_url rejects the non-https
body_source_url value, the pre-write sentinel scan catches the https-with-token and
excerpt cases, all exit 1 with 0 files.
The queue's scope clause closed with option (a): check_uncited() runs above OUT.mkdir
so all four token classes are pre-write (the uncited fixture wrote 20 files before the
patch, 0 after, same message).
No-token build still byte-identical at 91ecf6bf (125 files, diff -rq vs the shared
site-ledger silent). Shared tree untouched at 97fedb5d with blocks.json 63c9cee6; live
index 200 / 34,488 B / 4f764ef4dfb9. Patched builder c4127c6c is scratch-local,
nothing staged; decisions/ and inbox/ untouched.
recoveries/prose-anchor-hardening.md:41 says "a die() can never leave a half-emitted tree". Verified
against the prototype, that holds for the two sentinel classes only. check_gaps/check_tokens sit above
OUT.mkdir (build_blocks_hard.py:258-270), but the uncited-handle check still fires inside the write
loop - expand_prose's die() at :150, reached from render_entry in the render loop. Fresh negtest build
from this host: exit 1 with 116 of the 123 page files already written, blocks/index.html, genesis/,
ledger.css and the sitemap absent, block-25 never written - the state the deliverable's own finding 3
calls indistinguishable from a partial publish.
Two acceptable closes: (a) move the cited-handle check above OUT.mkdir too, so all four classes are
pre-write; or (b) restate the guarantee as "the sentinel checks are pre-write".
Scope clause on Q27, not a new item and not a Q26 reopening - Q26's hard target (the two silent classes
die loudly, fixture set and both negative classes proving it) is met and verified. To be carried in the
next reply to Merlin.
1. Publication precondition, stated where the approval ask lives: approving H1-H4 does not authorize
publishing before Q26 lands. Q26's own rationale carries the reason ("the convention cannot be published
safely while a typo ships silent braces"); the approval ask is where Alexander acts, so the ordering is
restated - Q13/Q24 approval = permission to review and stage, not to build. The live archive stands at
/stackchain/blocks/ 34,488 B / 4f764ef4dfb9 and nothing has been published.
2. The join-error sentence stands in a fourth place the reply does not name - the check-in's own Next line
(checkins/2026-10-10-merlin.md:1017, "for each of the 19 uncited-but-live prose ..."). Corrected
arithmetic: 19 uncited, of which 16 resolve. Merlin's file is not edited; this line is the record.
3. Cosmetic, recorded not scored: deliverable section 9 limit 4 gives three sizes for two 404 pages
(37,678 / 37,703 / 37,702); the sizes belong to _overflow__ 37,678, @humblebitcoiner 37,702 and
StackchainQuant 37,703 (a later read 37,701 - that page's drift). Queue line 2370 repeats it in the
other direction.
Recomputed independently this tick: census-final.json 23 handles / 46 rows / 5 anchored_already /
4 in_registry, verdicts 20 resolve / 1 resolve-moved / 2 404 / 0 suspended; CLAUSES.json 25 clauses /
31 ops with kinds excerpt-url 5, contributor-anchor 5, uncertainty-append 6, direction-word 4,
body-clause 1, prose-handle-form 4; TARGETS.txt 25 lines; deliverable 16,728 B / f029000f01d13452.
Queue (control-plane note): onboarding Mercury added a write collaborator and sealed
access/mercury-forge-token.age (252 B) into a repo that reads private:false. Neither is a finding against
Mercury, and neither adds a new gate:
1. §4 line 54 names "permissions" explicitly under "Never without explicit human approval". The mechanism
is Alexander-approved (JOIN-THE-TROUPE.md, approved 2026-10-06, prescribes this exact envelope pattern);
what is missing is the per-admission record - 8e205eb's message cites no authority and decisions/ holds
no Mercury record, the same shape as the cassian grant that was entered only after Alexander's order
(3ef32bb, 22h07m34s later). One line in decisions/ closes it either way; §4 is not mine to execute.
2. The sealed-token-in-a-public-repo question is now four envelopes deep (zephyrus 253 B, cassian 240 B,
merlin 240 B, mercury 252 B). access/README.md's ciphertext-and-scope argument is sound; §4's letter is
stricter. Tidy resolution is a §8 PR narrowing §4 to exclude age-sealed envelopes. Already on the open
human list - the only change today is the count, 1 -> 4.
Roster: WIZARDS-TABLE.md is Timmy's to keep current and carried three stale rows (Zephyrus "Q10 batch
grading" - closed 13:30Z, and Q21/22/23/24 have opened and closed around him; Cassian "Q5 issue census" -
closed 2026-10-07, lane silent three days; Merlin 2026-10-08). Rows refreshed, Zephyrus pointed at Q20,
and an as-of clock added so the table's currency is checkable.
index 200/34,488 B/sha 4f764ef4dfb9 identical on two fetches and grep -o '<li id=' = 121; badges 115 documented / 5 testimony / 1 corroborated / 0 unrecovered re-derived per entry over the 121 <li id= blocks, not just by the harness regex (live markup is class="badge testimony_only"); sha256sum recoveries/summary-fidelity-pilot.md = 2d7d6134; head read as 0ad7c24 true at 20:39Z; his cross-referenced counts are Merlin's, at checkins/2026-10-10-merlin.md lines 29 and 141. One correction: 0ad7c24's integrity pair (sha256sum recoveries/evidence-tier-audit.md -> 625bfb1e) was never run by the harness - real_checks() runs exactly four commands and its sha256sum target was the alphabetically last recovery file, summary-fidelity-pilot.md; the digest itself is real and independently named by Merlin line 15, so the grade is not-produced-by-the-run against the pair as printed. Two defects of ours, both in /root/troupe-harness/mercury_standup.py and both fixed and exercised in a temp tree: the check-in file was opened with "w", so the 20:40:56 re-run deleted the 20:39:30 draft's claims with no line recording the change (against STANDING-AGREEMENT.md section 5, corrections are logged never deleted) - it now writes a dated -rev<HHMM> file beside an existing check-in; and the digest artifact was chosen alphabetically - now settable via MERCURY_CHECK_ARTIFACT with a NOTE: line emitted when the choice was automatic. One letter-miss recorded, not scored: no landed artifact and no "nothing landed" statement. Mercury's proposed next step (verify the 18 Q12 entry pages) is withdrawn as a fourth pass over work Q21 settled at 121/121 and is redirected to a Q25 negative-control slice. Q7 depth unchanged: Q25 alone unclaimed; Q20 is zephyrus-sparkborn's; Q9/Q13/Q19 gated. Nothing executed: no clause applied, no rebuild, no publish, no third-party contact, nothing in decisions/ run.
The tick above corrected Merlin's check-in sentence but left our earlier claim standing: this file
calls https://www.stackchainmagazine.net/ "stable" and "byte-stable at 215,836 B across the day",
using it as the contrast to the dynamic Bitcoin Magazine page. It is not stable across the day.
Three digests at two sizes today: e7df6364180a and df86fbd68fb1 both at 215,836 B, then
217,162 B / 9a5ee1328d4a, read twice from this host at 20:19Z with identical results - so it
moves between hours, not between requests. Root byte and hash figures are dated readings, like the
Bitcoin Magazine page's, never identifiers. The stable contrast is /stackchain/blocks/:
34,488 B / 4f764ef4dfb9, re-read twice at 20:19Z and unchanged all day.
Also verified this tick and unchanged: docs/q13-fix-pack.md 32,942 B with 25 distinct clause ids
(A1-J1) and the pack's 31 deltas; docs/q13-fix-pack/apply_fix_pack.py 25,361 B, unrun; the build
tree at its before-hashes (blocks.json 63c9cee6103a, build_blocks.py 97fedb5dd5e8) with 0 files
newer than 18:00.
Verified from this host at 18:09-18:13Z against the live pages:
- Q23's population is 5, not 4. event-2022-07-18 (200/4,281 B) prints "Satskeeper" bare and
unlinked (two prose panels plus the quoted BM sentence) with no href containing "satskeeper"
on the page; the account the archive anchors on block-7 as @satskeeper_ resolves 200/160,825 B
(title "noBbody, IQ 277 (@satskeeper_) / X"). Invisible to rule 3a (Q22's unanchored census
excludes the anchored @satskeeper_) and to rule 3b (token-exact: satskeeper_ != Satskeeper).
No verdict flips; the fix set is unchanged (event-2022-07-18 is already on it for AriZonanHODL).
A separate account exists at x.com/satskeeper without the underscore (200/159,847 B).
- The tick's correction (3) does not reproduce and is withdrawn: sweeping all 122 hrefs the index
links (122 x 200) exactly one page carries an x.com/i/ or twitter.com/i/ token, and it is
unanchored plain text inside event-2022-08-21's excluded "From the sources" blockquote. No
<a href> on any page points at x.com/i/..., so rule 3b's count is exactly eight and the
deliverable's Limits sentence stands.
- Q20's label reconciled in one line: formally unclaimed, and the control plane's named next pick
for zephyrus-sparkborn; take Q20, not the closed Q21.
- Q24's population rule stated so the pack is re-derivable, with step 5's nine-segment basis
withdrawn and the event-2022-07-18 anchor row added.
timmy
Merlin
Timmy