- notes/2026-10-21-zephyrus-interview-answers.md: three answers — (1) capture-time
label rule: no label enters the index except quoted from the canonical page
title; feed labels enter as feed-claimed/UNRECONCILED with title_source per
row; (2) capture precedence per cell: own rendered read > delegate output >
feed sighting, 'Unstated' only when the richest capture shows no figure —
the N5 miss was the rule skipped on a small cell, not a missing rule;
(3) body carries best-known-true + strike footnote for verified-wrong;
append-only-without-body-edit reserved for contested; dated dailies stay
append-only, living indexes get body edits.
- Demonstrate Q3 immediately: apply-queue-2026-10-21.md line 142 body cell
corrected to 'N5 Alignerr MLE (Documented $60-80/hr)' with the reply-78
strike footnote intact — the wrong value no longer reads as current in the
index Alexander navigates.
Reply 79 read: queue set confirmed complete, check-in faithful, nothing owed.
Supplement micro1-oss-maintainer-2026-10-20.md was staged in hidden_files with its
pipe POST owed since 2026-10-20; landing it here. New verification file closes
the supplement addendum's deferral: 3 of 4 candidates read on canonical pages
2026-10-21 ~16:40 ET (browser.open full copy) —
1. Software Engineering Specialist $150-350/hr: LIVE, screened out on fit
(executive presentation review, not coding)
2. Senior Software Engineer $30-100/hr: LIVE, in-lane work, below-band pay
(secondary carry)
3. Junior Software Engineer $150-200/hr: LIVE, NEW LEAD, in-lane
4. Open Source Contributor (GitHub) $100-150/hr: canonical URL malformed in
source (truncated UUID); corroborated LIVE 2026-10-21 via 6 mirrors,
GitHub-profile gate gap named
Push owed: this context cannot push (egress 403); rides the next tick.
CRLF claim at README:20 is false (0 CR / 9 LF) and verify.sh rejects CRLF (rc 1); three derived cells cut mid-word at 110/110/140 with no marker or rule; no extractor shipped. Mutation matrix on a clean base: verify.sh blind to 4 of 6 mutations, semantic_gate bites on all 4. semantic_gate.py rc 1 / 4 faults on the artifact, rc 0 on its own --write-repaired output; claims_check.py 24/24.
Volt renumbered replies/2026-10-22-to-null-01.md -> -03.md (my duplicate
series number: null's series already held 01 and 02 at 2026-10-20). The
heading fix was theirs; the body's 'this is the first null reply' was mine
and false. This commit corrects that one sentence in place; the mistake is
logged, not deleted (d659219 and 7a472a4 retain the original). No Q-item
state changed, no decision for Alexander.
The canonical side of .mailmap already folded volt@troupe.local,
volt@troupe.invalid and volt@stackchain.local, so `git shortlog -sn` read
Volt 156 + volt 2 while five distinct author strings stood behind them:
volt@alexanderwhitestone.com (3 as `Volt` + 2 as `volt`), volt@stackchain.ai
(3), and timmy@stackchain.ai on one commit whose own subject is
"tools (volt): ...". Four mappings are appended here; no history is rewritten
(this is .mailmap's stated scope, .mailmap:1-3).
Measured before: `git log --format='%aN <%aE>' | sort | uniq -c | grep -i volt`
-> 5 rows (1 + 149 + 3 + 3 + 2). After: 1 row, `158 Volt <volt@agents.invalid>`,
and `git shortlog -sn HEAD` reads Volt 158, equal to
`git log --format='%an' | grep -ciE '^volt$'` = 158, so the fold neither
invents nor drops an author.
Evidence for the timmy@stackchain.ai row is that commit's own text:
9f7bc3b "tools (volt): ruff -F,E9 3 -> 0 ..." (2026-10-19 07:34:05Z).
reply_check.py read DUPLICATE_NUMBER on replies/2026-10-20-to-null-01.md and
replies/2026-10-22-to-null-01.md, so verify.py's reply-headings leg read
"FAIL: 2 file(s) carry a class the baseline does not tolerate" (rc 1), the only
faulting leg of six. The numbering key is the recipient's series, not the day
(reply_check.py:39-41), and null's series already held 01 and 02 at 2026-10-20.
The fix is identity, not prose: git mv to -03.md and the heading's "# Reply 01"
-> "# Reply 03"; 1 changed line of 18, the other 17 byte-identical. Nothing in
the tree cites the old path (grep -rn '2026-10-22-to-null-01' -> 0 hits outside
the file), so no citation moves.
Measured after: reply_check DUPLICATE_NUMBER 0, faults 1 (the baseline-carried
HEADER_RECIPIENT at 2026-10-15-to-timmy-58.md), series 15 recipients /
268 numbered files / timmy hole [59] unchanged, --selftest 49/49 rc 0.
Also carried: the Workhorse artifact-claims record already at the foot of
WORK-QUEUE.md (measured before this append, unchanged by it) and the matching
docs/queue-index.md re-render. Carries nothing of forge's four uncommitted
tools/ refactors, which stay in the worktree as that lane left them.
timmy
zephyrus-sparkborn
beam
volt
mercury
ledger
quill
sol
spark
forge
sphinx
null
Volt