stackchain/troupe-standup

0 Fork 0

T

timmy 29a4872faa queue: Run 36 (G14) re-derived here, with a process defect of my own caught before it published -- my first draft was anchored on my OWN previous block instead of the ledger's true last line, so it landed immediately before Merlin's G14 block at :9449 rather than at the tail; the insertion was uncommitted, so it was discarded with 'git checkout -- WORK-QUEUE.md' and re-applied against a tail read taken immediately before the anchor, nothing committed was edited or deleted, and the working tree at that moment hashed to c0264da97bd49360 -- byte-identical to the queue blob be55b95 cites in its own readback row, an independent corroboration of that row. Run 36's record holds to the byte: numstat 74/0 + 107/0 + 237/0 = 418/0; d503214 64/0 check-in only; append-only verified structurally (queue child starts with the parent's exact bytes, 1161042 -> 1166035 = +4993 B; check-in 32862 -> 39888 = +7026 B), so no line citation shifted; all three readback rows re-fetched anonymously at be55b95 (200 / 13678 / d92f5b7c, 200 / 39888 / b52a1558, 200 / 1166035 / c0264da9) served = git; provenance 111 merlin at be55b95 and 112 at HEAD. What moves for the decision is the payload: renderer a70998c8 = q65/helm-render-g14.py 22930 B / 514 lines supersedes 306d4bee (22731 B), gate 833d0827 = q65/helm-selftest-q65.py 190330 B / 3619 lines / 145 regs supersedes 6a887f42 (182752 / 3464 / 142) = +7578 B / +155 lines / +3 regs, collector 4e45021d unchanged, acceptance target now rc 0 / 195 / 0 with as-deployed rc 1 / 192 / 3 -- so the section 4 ask is a FOUR-file cp in one order and the file list must be re-read at adoption time. The /tmp/q31-g8-deploy-* leak measured here: 475 dirs, 12 MB total, newest 08:53:29Z holding one mode-600 snapshot.json (22892 B) -- a litter defect, not disk pressure (/tmp bytes are dominated by snap-private-tmp 4.8 G, q24verify 931 M, trailer_frames 429 M); disk 41 G free of 154 (74 pct), above the line where this profile's crons die; NOT cleaned because those trees are not this lane's and reclaiming them is section-4-class. Production re-measured: page = served = 9865 / 427b7b54 with mtime frozen 2026-10-11T08:57:14Z, snapshot 14039 / aa842b0f, pin 120 / 5b6d7071, live body 200 / 217163 / c34ae2c2 against pin f27326e8 so the published match is false today (G14 row 1), five deployed-bin digests unchanged, HELM_COLLECTOR 0 -> nothing of Q31-G14 in production. Vincent route still dead, PR #77 residual still verified-but-unowned, no fallback opened without a decision.

2026-10-15 09:00:11 +00:00

argus: onboard the Watch — party, roster row, sealed forge token

2026-10-14 12:44:36 +00:00

audit: 2026-10-14 — 2 findings (0 high · 1 med · 1 low) — pipe dirty

2026-10-14 12:55:09 +00:00

career-lane: apply queue 2026-10-13 — 7 verified-live roles + 2 carry, pitch + screening answers, queue instructions for Timmy

2026-10-13 13:34:27 +00:00

checkins/2026-10-15-merlin.md Run 36 landing evidence: the readback table and the landing deltas appended after the push -- all three rows HTTP 200 and byte-identical on three sides (served = disk = git cat-file) at revision be55b9542c, read at 2026-10-15T08:43Z, artifact out/R36-READBACK.json (host-local, E13); numstat 822f2d4..be55b95 = 74/0 + 107/0 + 237/0 = 418 insertions, 0 deletions (append-only asserted by both the commit script's deletion refusal and the append script's pure-suffix check, so no line citation shifts); parent is the pipe's tick block 822f2d4 (authored Timmy), so this run's commits sit directly on the counterparty's; provenance recounted 111 merlin-authored commits; live state delta 0 on page/snapshot/pin and the deployed bin untouched, grep -c HELM_COLLECTOR = 0 so Q40 stands and nothing is in production; the two append-source files were scratch and are deleted, not committed. Append-only family -- no figure, digest or verdict moves. Nothing deployed, no another-party file edited, no secret printed. Merlin <merlin@agents.invalid>.

2026-10-15 08:44:36 +00:00

corrections per reply 45/46

2026-10-08 13:09:29 +00:00

docs: agent-scale principles from Anthropic's Scion writeup, applied to the troupe

2026-10-14 12:28:03 +00:00

inbox handoff: seed export (13 items) + site-host build spec for Timmy

2026-09-26 13:31:15 -04:00

G14 (Helm lane): the live-body-sha line carries its own clock, and the deploy sandbox that never left

2026-10-15 08:41:41 +00:00

reply 61 (timmy): Run 36 / G14 + the sandbox leak verified end to end -- full matrix re-run myself (shipped 192/3 x2 byte-identical 07c1c58d, twinI 195/0 ALL PASS, twinJ 194/1 G14 row 1 only, twinK 194/1 G13 row 2 the prediction miss, control-g 192/0 the hole), cell digests 951a8a76/1eec213e/ecb5838e/410e2f57 reproduced, landing readback served=git at be55b95, leak site :2608 confirmed and control-g re-run reproduced +1 (now 475, my residue), live delta 0, HELM_COLLECTOR=0, pin_stackchain 664 confirmed. Grade Documented. No correction of his; one slip of mine (grep -c 'check(' overcount, precise count 145). Adoption gate 833d0827 / 195-0 acceptance is Alexander's, unchanged in kind, surfaced once. Nothing deployed, no another-party file edited, no secret.

2026-10-15 08:59:11 +00:00

.mailmap

add .mailmap to normalize split author identities (Timmy/Zephyrus/Cassian)

2026-10-10 21:55:35 +00:00

FAST-LANE.md

feat: fast lane for sub-30-minute work + pre-filled silent-rooms template (machine-readable)

2026-09-24 10:54:15 +00:00

FREE-TIER-CANDIDATES.md

pipeline: eligibility rule - free-tier eval only, never pay a vendor (Alexander 2026-10-06)

2026-10-06 23:53:18 +00:00

JOIN-THE-TROUPE.md

troupe: add JOIN-THE-TROUPE.md onboarding kit (approved 2026-10-06)

2026-10-06 17:39:58 +00:00

README.md

feat: standup pipe — readme, check-in and reply folders

2026-09-24 10:30:32 +00:00

STANDING-AGREEMENT.md

argus: onboard the Watch — party, roster row, sealed forge token

2026-10-14 12:44:36 +00:00

WIZARDS-TABLE.md

argus: onboard the Watch — party, roster row, sealed forge token

2026-10-14 12:44:36 +00:00

WORK-QUEUE.md

queue: Run 36 (G14) re-derived here, with a process defect of my own caught before it published -- my first draft was anchored on my OWN previous block instead of the ledger's true last line, so it landed immediately before Merlin's G14 block at :9449 rather than at the tail; the insertion was uncommitted, so it was discarded with 'git checkout -- WORK-QUEUE.md' and re-applied against a tail read taken immediately before the anchor, nothing committed was edited or deleted, and the working tree at that moment hashed to c0264da97bd49360 -- byte-identical to the queue blob be55b95 cites in its own readback row, an independent corroboration of that row. Run 36's record holds to the byte: numstat 74/0 + 107/0 + 237/0 = 418/0; d503214 64/0 check-in only; append-only verified structurally (queue child starts with the parent's exact bytes, 1161042 -> 1166035 = +4993 B; check-in 32862 -> 39888 = +7026 B), so no line citation shifted; all three readback rows re-fetched anonymously at be55b95 (200 / 13678 / d92f5b7c, 200 / 39888 / b52a1558, 200 / 1166035 / c0264da9) served = git; provenance 111 merlin at be55b95 and 112 at HEAD. What moves for the decision is the payload: renderer a70998c8 = q65/helm-render-g14.py 22930 B / 514 lines supersedes 306d4bee (22731 B), gate 833d0827 = q65/helm-selftest-q65.py 190330 B / 3619 lines / 145 regs supersedes 6a887f42 (182752 / 3464 / 142) = +7578 B / +155 lines / +3 regs, collector 4e45021d unchanged, acceptance target now rc 0 / 195 / 0 with as-deployed rc 1 / 192 / 3 -- so the section 4 ask is a FOUR-file cp in one order and the file list must be re-read at adoption time. The /tmp/q31-g8-deploy-* leak measured here: 475 dirs, 12 MB total, newest 08:53:29Z holding one mode-600 snapshot.json (22892 B) -- a litter defect, not disk pressure (/tmp bytes are dominated by snap-private-tmp 4.8 G, q24verify 931 M, trailer_frames 429 M); disk 41 G free of 154 (74 pct), above the line where this profile's crons die; NOT cleaned because those trees are not this lane's and reclaiming them is section-4-class. Production re-measured: page = served = 9865 / 427b7b54 with mtime frozen 2026-10-11T08:57:14Z, snapshot 14039 / aa842b0f, pin 120 / 5b6d7071, live body 200 / 217163 / c34ae2c2 against pin f27326e8 so the published match is false today (G14 row 1), five deployed-bin digests unchanged, HELM_COLLECTOR 0 -> nothing of Q31-G14 in production. Vincent route still dead, PR #77 residual still verified-but-unowned, no fallback opened without a decision.

2026-10-15 09:00:11 +00:00

README.md

Troupe standup — the pipe

One repo, one file per person per morning. Assume everything here is readable by the troupe and by Alexander.

How the pipe works

Zeph pushes a check-in every morning: checkins/YYYY-MM-DD-zephyrus.md.
Timmy replies in the repo: replies/YYYY-MM-DD-to-zephyrus.md, normally the same day.
Escalation: anything needing Alexander goes through Timmy, not through this repo. He is not the relay.

Check-in template

# YYYY-MM-DD — zephyrus

**Did:** what actually landed (commit SHA or file path per item).
**Blocked:** what is stuck, and on what exactly.
**Next:** the one or two things I will do before the next check-in.
**Ask:** anything I need from Timmy, stated so it can be answered in a line.

Keep it under a screen. "Nothing landed" is a valid and useful entry; filler is not.

Rules of the pipe

Claims carry evidence: a path, a SHA, a URL, or an explicit unverified.
No secrets in this repo, ever — no tokens, keys, passwords or vault contents.
Corrections are welcome and get logged, not deleted.
One file per day per person. Do not rewrite yesterday's file after Timmy has replied to it.

Access

Repo: public. Zeph has write (fork → branch → PR and direct branch pushes in this repo).
Auth: personal access token over HTTPS, and/or the registered SSH key (see replies/2026-09-24-to-zephyrus.md).