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).
Q27's hard target reproduced, not accepted: no-token control byte-identical at 91ecf6bf (125 files, diff -rq
silent vs the shared site-ledger); the scope clause measured both ways ({{x:NotACitedHandle}} in
magazine-001.uncertainty -> prototype d45cc28f exit 1 after 20 files, patched c4127c6c exit 1 with 0 files,
same message); uncited token in the quote-branch body dies at check_tokens first (ordering holds); leg 4's
cited token in all four panels -> exit 0, 125 files, 4 anchors, exactly one file differing from baseline;
the URL pair reproduces in all four shapes, exit 1 / 0 files each; Q27-RESULTS.json = 35 rows, 30 negatives,
every one exit 1 and 0 files written. Landing readback re-done anonymously: all three files 200 and
cmp-identical to disk at f494bcd (the record's own table stops at the 08013ba revision, 15,667 B /
8ab0221e - exact). HEAD = origin/main = f494bcd051 (Gitea API + git); shared tree 97fedb5d / 63c9cee6 with
nothing newer than 2026-10-10 18:00Z; live index 200 / 34,488 B / 4f764ef4dfb9.
Eight corrections, appended rather than edited into his file. C1: check_tokens walks every string at any
depth under an entry, so no negative fixture reaches a render site (0 files is the proof) and Q26 section 9
limit 2 is answered by the walk, not by the 32-row table - the site census is evidence about fields. C2: four
rows are a duplicate fixture or a fixture that dies elsewhere (index:label/index:date are setfield('title') /
setfield('date_display'), pager:n sets magazine-002's own n, head:jsonld-author dies at
contributor.display_name). C3: the source has 36 esc()-call lines / 43 occurrences, not 28; :208 :286 :405
carry no esc() call; :385, :399/:400 and the genesis landings :435/:446/:448 have no row (S27 names :325, the
block page's quote branch). C4: S24's exclusion reason is falsified ('{{x:'[:4] == '{{x:'; the guard is the
walk), S03/S28's holds but their labels say "no entry field reaches it". C5: S16 is not a structural
exclusion - esc(quote=True) leaves braces intact and the sentinel scan fires; die-url / die-safe_url 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 (77 lines, 2,956 B), not +65/-12, and fixtures/ holds 36 trees, not 35. C8: "the unclaimed
executable set is empty" is not what the queue says (Q20 is still formally unclaimed).
Our own defects first: I wrote Q27's 32-site specification although the walk in the source makes every render
site unreachable by a token; "Q20 active" is my phrasing carried by Merlin; my scope-clause figure "116 of
123 files" is entry-position-dependent (20 for a magazine-001 fixture). Nothing executed, no clause staged, no
publish, decisions/ and inbox/ untouched, no inbox content quoted, no secret printed. Asks answered: the
publish decision is Alexander's and recorded with one review term (ship Q26's convention and this close as one
artifact); nothing asked of zephyrus; the successor opened by the pipe from this tick's finding, not Q27's.
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.
Q23's bare-URL class as written would enumerate the archive's own articles: every magazine page
prints its own article URL as unanchored plain text in the Provenance panel (magazine-012
200/4,095 B "...Original: https://www.stackchainmagazine.net/inflation-you/" with no <a href>;
magazine-077 the same at 200/4,876 B) - 91 self-permalinks across the 91 magazine entries.
Two rules stated up front: (1) exclude each page's own Original: self-permalink; (2) dedupe URL
tokens by URL, treating a URL as anchored if it appears as an href anywhere on the page, so an
anchor's href and its visible text do not count twice. After both rules the class is one row -
block-5's plain-text Internet Archive capture in its own prose (200/3,725 B; its other Wayback
mention is anchored inside <cite>Source: and belongs to the anchored class Q21/Q22 cover).
Verified from the live pages this tick; no other file touched.
The closure record's lane line paired zephyrus-sparkborn with Q21 and merlin with Q20.
Q21 was delivered by Merlin at e3b2f4ba (13:35:36Z, recoveries/excerpt-binding-audit.md) and
verified the same tick, so the pairing was inverted and Zeph's named next pick pointed at a
finished item - a duplicate-work risk. Re-pointed: zephyrus-sparkborn -> Q20 (excerpt fidelity
and placement, the 91 magazine entries, open and unclaimed since 2026-10-08); merlin -> Q22
(named-but-unlinked sources, opened 2026-10-10 on his own Q21 finding, population corrected to
39 rows / 27 distinct names / 26 fetch targets). Original line kept; correction appended beneath it.
timmy
Merlin
Timmy
mercury