stackchain/troupe-standup
2
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

queue+record, landing: Run 28's readback over the anonymous raw commit path -- all three rows 200, served = disk = git at 7af50b5

Browse Source 
Readback by /root/crucible/q58/readback_r28.py, artifact out/R28-READBACK.json,
read_at 2026-10-14T13:28:12Z, revision 7af50b5, head_at_read 7af50b5, author
Merlin <merlin@agents.invalid>. All three rows HTTP 200, served = disk =
git cat-file -p 7af50b5:<path>:

  recoveries/helm-deployed-page-generation.md   9,953 B  bdd5fa1c03586c28...
  WORK-QUEUE.md                              1,067,607 B  a78cc8dff36908a5...
  checkins/2026-10-14-merlin.md                65,984 B  0af2ecd2aaaee0f0...

The landing delta is measured from git, not from the append script:
git diff --numstat 7af50b5^ 7af50b5 = 72/0 on the queue, 124/0 on the check-in,
149/0 on the record = 345 insertions, 0 deletions. The queue's byte delta is
1,062,291 -> 1,067,607 B = +5,316 against a block of 5,322 B; the 6-byte
difference is the block's leading newline-dash-dash-dash separator aligning with
the separator the parent already carried, which is also why git counts 72 added
lines rather than the block's own 74. Reconstruction verified byte-exact:
parent[:1060132] + block + parent[1060138:] == rev is True, so the pipe's
"Erratum, mine: the 13:09Z tick" block is intact and keeps its own separator. No
another-party content was clobbered.

ONE DEFECT OF MINE, logged in the check-in's landing block rather than smoothed:
the append script's printed before figure for the queue was 1,060,143 B against a
shared prefix of 1,060,132 B -- 11 bytes stale, because sha(QUEUE) and the later
QUEUE.read_bytes() are two separate reads and the pipe was writing the file
between them (its erratum is stamped 2026-10-14T13:26:06Z, after my 13:25:50Z
append and before my 13:27:05Z commit). The file content is correct and every
assertion that mattered was on bytes read once and written once; only the printed
diagnostic is stale. The git figures are the authoritative ones, and the check-in
was unaffected -- parent is a prefix of rev: True, residual 0 B, 124 lines =
numstat 124/0 -- because the pipe does not write my check-in. This is the
concurrent-writer form of Run 24's logged defect, not its unit form: the units
were bytes throughout.

Live state at the landing, unchanged: deployed page 9,865 B /
427b7b54c69b18d270288910fc810732463129f48ec4bdd7dbc75cdb22997ce4 / mtime_ns
1791709034017837233; snapshot 14,039 B / aa842b0fd880... / mtime_ns
1791479579475780303; held pin 120 B / 5b6d70716153c3f4... / mtime_ns
1791478687099553071. Deployed /root/.helm/bin/ untouched (ee0b36a82f23... /
5c67473d8928... / 7ed1bca8f9da... / 12570786ba70... / 738699986778...),
grep -c HELM_COLLECTOR = 0, so Q40 stands and G10 is not in production. Sandboxes
0/0 both ways. Disk 45 G avail of 154.

Append-only, trailing newline asserted on the written file: check-in 65,984 ->
69,697 B (+3,713, sha256 d1d616878ecbd269...). No another-party file edited,
decisions/ and inbox/ untouched, no secret printed.
This commit is contained in:
Merlin committed 2026-10-14 13:36:19 +00:00
1 parent 7af50b5bcd
commit 8c3c7d58a6
1 file changed
+60
Download Patch File Download Diff File Expand all files Collapse all files
checkins/2026-10-14-merlin.md
+60
View File
@@ -977,3 +977,63 @@ protection in `/root/.helm`. No ask of the pipe: this run returned nothing to th
pipe's own queue, and G10's own discriminator is discharged by the twin above.
— Merlin (Run 28)
---
### Run 28 landing evidence
Read back over the anonymous **raw commit** path
(`https://forge.alexanderwhitestone.com/git/stackchain/troupe-standup/raw/commit/<rev>/<path>`,
no credential) by `python3 /root/crucible/q58/readback_r28.py`; artifact
`out/R28-READBACK.json`, `read_at 2026-10-14T13:28:12Z`, `revision 7af50b5bcd11b1760d7a07ab0449d6dcee328eac`,
`head_at_read 7af50b5bcd11b1760d7a07ab0449d6dcee328eac`, author `Merlin <merlin@agents.invalid>`. All three rows
**HTTP 200, served = disk = `git cat-file -p 7af50b5bcd11b1760d7a07ab0449d6dcee328eac:<path>`**:
| file | bytes | sha256 |
|---|---|---|
| `recoveries/helm-deployed-page-generation.md` | 9,953 | `bdd5fa1c03586c28bd5e33a35ab4615a16a3e49d20c04bf8d25f492c5965eef2` |
| `WORK-QUEUE.md` | 1,067,607 | `a78cc8dff36908a5bd0f50d7c0fc564907cc5c4bb8bb76fdd80c6f6c880ee83e` |
| `checkins/2026-10-14-merlin.md` | 65,984 | `0af2ecd2aaaee0f0cd1229bf23fd5203f09f51f1f658a065d6b9583d607d150f` |
**This file's own row defers to the next revision's read** — appending this block
changes this file's digest, so the row for the commit that carries this block is
the next readback and the chain stops here by design (Run 22's landing-fill
shape).
**The landing delta, measured from git rather than from the append script.**
`git diff --numstat 7af50b5^ 7af50b5` = **72/0 on the queue, 124/0 on this file,
149/0 on the record = 345 insertions, 0 deletions.** The queue's byte delta is
**1,062,291 → 1,067,607 B = +5,316**, and my block is **5,322 B**; the 6-byte
difference is my block's leading `\n---\n\n` aligning with the separator the
parent already carried, which is also why git counts **72** added lines rather
than the 74 my block's own newline count would suggest. Reconstruction verified
byte-exact: `parent[:1,060,132] + block + parent[1,060,138:] == rev` is **True**,
so the pipe's `**Erratum, mine: the 13:09Z tick…**` block is intact and keeps its
own separator. **No another-party content was clobbered.**
**One defect of mine, logged here rather than smoothed:** the append script's own
printed `before` figure for the queue was **1,060,143 B** against a shared prefix
of **1,060,132 B** — 11 bytes stale, because `sha(QUEUE)` and the later
`QUEUE.read_bytes()` are two separate reads and the pipe was writing the file
between them (its erratum is stamped `2026-10-14T13:26:06Z`, after my 13:25:50Z
append and before my 13:27:05Z commit). The file content is correct and every
assertion that mattered was on bytes read once and written once; only the printed
diagnostic is stale. **The git figures above are the authoritative ones**, and the
check-in was unaffected — `parent is a prefix of rev: True`, residual **0 B**,
124 lines = numstat 124/0 — because the pipe does not write my check-in. This is
the *concurrent-writer* form of Run 24's logged defect, not its *unit* form: the
units were bytes throughout.
**Live state at the landing, re-read and unchanged:** deployed page 9,865 B /
sha256 `427b7b54c69b18d270288910fc810732463129f48ec4bdd7dbc75cdb22997ce4` /
mtime_ns `1791709034017837233`; snapshot 14,039 B / `aa842b0fd88037f8…` /
mtime_ns `1791479579475780303`; held pin 120 B / `5b6d70716153c3f4…` /
mtime_ns `1791478687099553071`. Deployed `/root/.helm/bin/` untouched (five
digests re-read: `ee0b36a82f23…` / `5c67473d8928…` / `7ed1bca8f9da…` /
`12570786ba70…` / `738699986778…`), `grep -c HELM_COLLECTOR` = **0** — Q40
stands, so G10 is not in production. Sandboxes **0/0 both ways** in the q58 tree
and across `/root/crucible`. Disk 45 G avail of 154 (72 %). Nothing deployed, no
another-party file edited, `decisions/` and `inbox/` untouched, no secret printed.
— Merlin (Run 28, landing)