volt
b0529e4592
The write-axis leg grades ONE surface per tool: `--json PATH`. Measured atc3ffee9with caller_write_flags.py (asset below), tools/ offers 22 flags a caller can aim for a write, across 21 tools: 19 are `--json` -- guarded, and graded by the leg -- and three are named otherwise, none of them wrapped: tools/queue_index.py :581 --write BARE tools/tool_map.py :510 --write BARE tools/doc_census_check.py :1831 --save-vocab BARE BARE = `open(path, "w")` with no try. Aimed at a target inside a directory that does not exist, each raised FileNotFoundError at rc 1 -- the exact defect class2556dbbremoved from 18 tools, still present on the surfaces the leg cannot see because it asks for `--json`. Each write is now wrapped in the same guard the `--json` path already uses: one line on stderr naming the path, rc 2 ("could not grade"), no traceback. Nothing else changed: no argument, no output format, no exit code on any other path. VERIFIED, both directions, in a throwaway worktree (never this tree): /root/.hermes/wizard-outputs/volt/2026-10-21-write-axis-bites/write_flag_probe.py --revc3ffee93 refusal rows TRACEBACK, rc 1 -> rc 1 (RED) (this tree) 3 refusal rows OK, rc 2, one stderr line naming the path, and all 3 still deliver at a writable target (rc 0, file non-empty) -> rc 0 (GREEN) Evidence: evidence/write_flag_red.json, evidence/write_flag_green.json. Selftests, unchanged counts: queue_index 58/58, tool_map 16/16, doc_census_check 104/104 (including its gate e2e --save-vocab cells). repo gate: 6 legs, 6 pass, 0 fault, rc 0 (selftest-sweep 21 tools 0 fatal). REMAINING BLIND SPOT, stated so it is not read as closed: write_probe.py's WRITE_PROBES table still probes `--json` only, so the next tool to add a `--write` is ungraded by the gate until that table grows a second axis. The static audit above (asset, 22/22 classified, 0 bare after this commit) is the interim instrument.
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).