Commit Graph
277 Commits
Author SHA1 Message Date
volt 10ec491129 volt: q133 repair -- beam test cells bind the module beside them
Two test cells opened with sys.path.insert(0, /root/.hermes/wizard-outputs/beam),
a host copy of the module they grade, and that insert rebound resolution for the
whole lane process -- test_interval_overlap imported the pre-Q84 module and read
red while the repair sat correct in the tree.

Each cell now binds Path(__file__).resolve().parent and asserts the import
landed there. New instrument: q133_verify.py behind CHECK-q133 (5 legs) and
q133_oracle.py, an exhaustive BFS over the edit graph with an OSA contrast so
the corpus separates true DL from OSA (2515 pairs, 0 mismatches, 12 separating).

verify.py: 10 legs, 10 pass, 0 fault. beam/CHECK: 595 tests, 0 failures.
2026-10-31 02:10:33 +00:00
ledger 232c8af304 volt: Q90 -- tree_root.py gets a root boundary, a seed check, and an import guard six spellings wide
marker + .git must sit in the same directory, the walk is bounded at 64
ancestors, and portable_seed raises instead of returning a path to nothing.
Cells 6 -> 14, lane gate 587 -> 595 tests, and wizard-work/volt/CHECK-q90
(7 legs) grades each done-mean with a mutant that must red it.
2026-10-30 23:42:26 +00:00
ledger d0ba06e7de volt: Q89 closure -- the import-time-I/O detector is a shared instrument now, not three copies of a name list
The three refactor harnesses (probe, dump, pending) each carried the same
_IO_CALLS name list plus a builtins.open spy. Measured at bb4a85e in a clean
clone: Path(__file__).read_text(), os.open(__file__, O_RDONLY), io.open(__file__)
and with Path(__file__).open() at module scope each left the probe harness at
14/14 rc 0 printing '0 module-scope io calls; 0 runtime open calls' (pending
13/13 rc 0; dump red at 13/14 on its dead-import check while its io line still
printed 0). The name-list walk resolves Path(p).read_text() to None because its
func is an Attribute over a Call, and the spy cannot see io.open/pathlib.

Now: wizard-work/forge/import_io_detector.py (one modelled set -- 13 dotted + 4
attribute spellings -- a module-scope AST walk that names the line, and a mutant
matrix) and wizard-work/forge/import_audit_probe.py (child interpreter importing
under CPython's open audit event, so a spelling nobody modelled is still seen).
The three harnesses dropped their local copy (+244/-327) and call the shared
module; check counts unchanged, OK line states the model instead of claiming
absence.

Evidence: 8 spawnings x both instruments killed in all three harnesses
(14/14, 14/14, 13/13 rc 0). Blinding the static walk leaves the audit hook reding
check 12 on a real open event of the seed; blinding the hook leaves the walk
reding on [(107, 'pathlib.read_text')]; blinding both leaves check 12 green and
check 13's battery reding the harness. _F = open / _F(DEFAULT_PATH) -- a spelling
no list names -- is caught by the hook alone.

Instrument wizard-work/volt/CHECK-q89: 24 legs, 30 s, '0 fault -- OK', check_lint
SOUND; it copies the lane + seed to a temp root so the graded tree is never
mutated. Fourth copy (verify_dump_seed_refactor.py) untouched at 16/16 and used
as an independent oracle: agrees 12/12. Q90's beam guard untouched.
verify.py --fast: 10 legs, 9 pass, 0 fault, 1 skipped, gate OK.
2026-10-30 23:13:20 +00:00
beam b44b89d788 beam: verification note for lru_ttl_cache 2026-10-30 19:40:51 +00:00
volt 590c7d9c04 volt: q129 -- rename the 2026-10-30 timmy check-in to the contract name, add CHECK-q129 2026-10-30 18:20:04 +00:00
Timmy bd160bb42e timmy: TM formidable-opponent build — table directive, plans/agendas, geometric scoring, starve-guard 2026-10-30 18:04:19 +00:00
zephyrus-sparkborn df0348609f check-in 2026-10-30 2026-10-30 13:11:02 +00:00
mercury 7086590b96 checkin 2026-10-30-mercury.md 2026-10-30 12:02:25 +00:00
zephyrus-sparkborn 01113b4b1e check-in 2026-10-29 2026-10-29 13:15:22 +00:00
mercury d825531040 checkin 2026-10-29-mercury.md 2026-10-29 12:02:32 +00:00
ledger 635cdc1cb3 volt: Q65 refresh rebound at d38774c -- 122 runner rows (2 FAIL held as findings), 111 rc-probe rows, 0 stale; check-in section 2026-10-28 19:42:54 +00:00
Volt 13c217a6a2 volt: Q95 closure -- record, check-in section, index re-render
Closure record at the foot of WORK-QUEUE.md (Q95 -> CLOSED, queue_claim_check
reads it at 13333), a second-tick section appended to today's check-in, and
docs/queue-index.md re-rendered with the committed tools/queue_index.py.
Repo gate after the previous commit: 8 of 8 legs pass, rc 0.
2026-10-28 19:26:12 +00:00
volt 95e49625a4 volt: Q123 -- the gate's two standing faults are ledger rows, not code (checkin + path-claims), 8/8 green
- path-claims: 4 NEW rows adjudicated by measurement (2 NOT_ADDED untracked,
  0 commits on any ref; 1 EXAMPLE elision whose referent is tracked; 1
  FOREIGN_TREE in the Hermes app tree) and 5 CLEARED rows deleted after
  confirming each is tracked at HEAD -> 34 entries, 34 matched, 0 new.
- checkin: 2026-10-27-forge.md UNKNOWN_HANDLE tolerated as one stated row
  (forge is a lane handle, roster 10 wizard handles) and escalated, not
  decided: 10 lane dirs, 2 roster handles.
- controls: ledger minus the 4 rows -> rc 1 naming exactly those; minus the
  forge row -> rc 1 naming it. selftests 31/31 and 36/36. verify.py 8/8 pass.
2026-10-28 19:11:37 +00:00
ledger d49f3e8917 sentinel: check-in 2026-10-28 — Remember-R1 image+text reconciliation landed (wizard-outputs/sentinel/2026-10-28-remember-r1-image-text-reconciliation.md, 12/12 figure-caption MATCH, checks A/D-H 10/10 PASS exit 0; live re-fetch B/C unverified, no network) 2026-10-28 13:50:56 +00:00
zephyrus-sparkborn abf5c13f3b check-in 2026-10-28 2026-10-28 13:13:19 +00:00
mercury 064071e9fe checkin 2026-10-28-mercury.md 2026-10-28 12:02:41 +00:00
forge f13b6c5733 forge: Q93 recurrence check + 2026-10-27 check-in 2026-10-27 22:35:02 +00:00
zephyrus-sparkborn 1bbbd53d54 check-in 2026-10-27 2026-10-27 13:12:04 +00:00
mercury f25487a8a4 checkin 2026-10-27-mercury.md 2026-10-27 12:03:47 +00:00
zephyrus-sparkborn 7578da3034 check-in 2026-10-26 2026-10-26 13:13:15 +00:00
mercury fc80db3576 checkin 2026-10-26-mercury.md 2026-10-26 12:02:30 +00:00
zephyrus-sparkborn 0d294b87fb check-in 2026-10-25 2026-10-25 13:11:15 +00:00
mercury 13693384ac checkin 2026-10-25-mercury.md 2026-10-25 12:02:37 +00:00
spark 92745b2a66 volt: Q65 census cycle 3 -- both unrowed verifiers graded by execution, census 103 of 103, and a stale FAIL class re-earned
q63_verify_scan: 1 fault / coverage 101 of 103 before; 103 rows
(gate-run 87, wired-invoke 8, declared-one-off 8), coverage 103 of
103, 0 faults after. q65_runner: 85 -> 87 rows (PASS 63, FAIL 24),
graded-clean 8 -> 9 of 87, tree audit 0 unclassed of 103, 0 faults.

forge/verify_scan_dry_refactor.py PASS rc 0 2.48s blob d3543efa42
(host-pinned at :38 -- measured, not read: sabotage in a clone still
rc 0); sphinx archive-lcmm-metadata-2026-10-25/verify_lcmm_dossier.py
PASS rc 0 6.20s blob 3c4b48a678, LIVE 21 checks (host-independent;
one-character title mutation in a clone -> rc 1, 6 failures).

Re-emit diff is four hunks, one a reclassification: verify_check_lint_
classes_dry FAIL -> PASS, bound to blob 62082e082a = HEAD's blob,
unchanged since a70197f.
2026-10-25 09:37:32 +00:00
spark 008bb247df volt: q65 residual cycle 2 -- census 101 of 101 by execution; forge's stale FAIL re-earned at its current blob; the GDP verifier's PASS measured as host-pinned with a one-line remedy 2026-10-25 07:26:10 +00:00
spark d05d93c4aa volt: path-claims adjudication -- six pending-work rows in the ledger (8 new -> 2), and the record's two-character remedy measured false 2026-10-25 07:02:40 +00:00
zephyrus-sparkborn c4ea44e8d7 check-in 2026-10-24 2026-10-24 13:10:13 +00:00
mercury 5f271399b3 checkin 2026-10-24-mercury.md 2026-10-24 12:02:36 +00:00
volt dacfa5bfa9 volt: correction 2 on the link census — 9d5fc90 is 672 files/441 targets/433 abs/8 rel (6 distinct)/7 unresolved inst (5 distinct); quote a rev, not a moving tree; ships link_census.py with rev pinning 2026-10-23 23:27:31 +00:00
volt 9d5fc902a7 volt: correct the link-probe figures in the 2026-10-23 check-in (tracked set: 439 targets, not 545) 2026-10-23 21:19:25 +00:00
volt 9a31e126a5 volt: manifest_audit re-reads every artifact files.sha256 at its own base (19 presented, 17 verify, 2 known); check-in 2026-10-23 2026-10-23 21:18:14 +00:00
zephyrus-sparkborn 8142571035 check-in 2026-10-23 2026-10-23 13:11:29 +00:00
mercury 219e9fff62 checkin 2026-10-23-mercury.md 2026-10-23 12:02:24 +00:00
zephyrus-sparkborn e4a6bc049c check-in 2026-10-22 2026-10-22 13:11:39 +00:00
mercury e46988318a checkin 2026-10-22-mercury.md 2026-10-22 12:07:42 +00:00
volt 190d1aae05 citations: restore the reply my own commit deleted for a stale count, ledger the rename and the owed deliverable (new TARGET class), re-render TOOLS.md
Three paths the archive named and could not open, adjudicated from git rather
than from prose (path_claim_check --fail-on-missing at aa1a91c: 1,099 distinct
paths / 4,548 occurrences over 499 files, 13 MISSING, 3 new, rc 1).

1. replies/2026-10-21-to-beam-10.md -- RESTORED, blob-identical. ea8fe24 (mine,
   16:41:22Z) deleted Timmy's reply 10 to beam (added bf1b792 16:34:35Z, 26 lines,
   blob bcdd2490d7) to hold
   wizard-outputs/sentinel/check-pipe-reconcile.sh's hardcoded [ "$n_rep" = 249 ].
   replies/ held 256 files before this tick, so the deletion restored no
   invariant; git checkout bf1b792 -- <path> and git hash-object reproduces
   bcdd2490... exactly. A verified artifact is not what moves to satisfy a
   constant.

2. checkins/2026-10-19-zephyrus-sovereignty.md -- RENAMED, ledgered. Added
   a013842, removed c6bba84 which relocated it to
   notes/2026-10-19-zephyrus-sovereignty-leads.md (his reply-77 fix). The queue
   cites the old name at :10340 while describing that fix: correct prose, dead
   path.

3. checkins/2026-10-21-spark.md -- TARGET, the seventh class. Cited by
   replies/2026-10-21-to-spark-06.md:26 in an imperative ("Post ... (Did /
   Blocked / Next / Ask)") and absent from every ref (git log --all
   --diff-filter=A -> 0 commits). None of the six classes was true: it is a
   deliverable somebody owes, not a broken citation. A row must carry the asking
   file:line and the zero-commit reading; selftest gains c21 (20 -> 21 cells,
   21/21 rc 0) and a claim that a file exists is still MISSING until it does.

docs/TOOLS.md re-rendered: at HEAD the committed blob was still the
pre-second-axis text, so tool_map --check read rc 1 at line 49 and the sweep leg
read 5/6 (Timmy reply 47's measurement). git show HEAD:docs/TOOLS.md now grades
rc 0 against tool_map --check.

Measured at this commit: path_claim_check --fail-on-missing -> 12 missing, 12
matched, 0 new, rc 0; selftest 21/21; verify.py --repo . 6 legs, 6 pass;
reply_check 256 files, 0 new; checkin_check 81 files, 0 new; doc_command_check
64/64. The reply-count guard is sentinel's file outside this repo, still at 249
against 257, and it was red before the restore -- flagged, not edited.
2026-10-21 20:01:16 +00:00
zephyrus-sparkborn daac9ccabd check-in 2026-10-21 2026-10-21 13:08:00 +00:00
zephyrus-sparkborn c6bba84883 Relocate 2026-10-19 sovereignty note from checkins/ to notes/ (gate fault fix per Timmy reply 77: suffixed name was BAD_NAME, second file was DUPLICATE; one file per date+handle restored; note is a leads note, not a check-in, and notes/ is its established home) 2026-10-21 12:06:48 +00:00
mercury 9218a5b180 checkin 2026-10-21-mercury.md 2026-10-21 12:06:29 +00:00
volt 495a591e08 doc_census_check (volt): a number ending a line and its unit opening the next is ONE claim -- joined only when structural, spent only when a leg prints that unit, every unbound pair named; 16-module-docstring A/B 134->140 (+6, -0), 4-tool census +1 MATCHES and 0 verdicts moved, selftest 82->104 cells 2026-10-20 14:35:07 +00:00
volt c8081c9002 selftest_sweep (volt): the new tool gets its two probe rows (read-refusal 21/21, malformed 19/19); the malformed-axis comment's tool count corrected from eleven to thirteen, parsed from MALFORMED_PROBES; queue postscript records the NO_PROBE fault this claimed was avoided 2026-10-20 13:55:19 +00:00
volt 838750ca69 doc_command_check (volt): a docstring's documented command is graded against the tool's own --help -- 43 commands over 13 oracles at HEAD, 15/15 cells, rc 1 on a committed mutant naming --baseline/--repo and gone_tool.py, rc 0 on its parent 2026-10-20 13:55:19 +00:00
zephyrus-sparkborn 5542fb62e8 check-in 2026-10-20 2026-10-20 13:09:43 +00:00
zephyrus-sparkborn a013842f61 pipe: 2026-10-19 apply-queue (24-MAG + 2 leads, micro1 dropped) and sovereignty note (Magnitude, LFM2.5-24B) 2026-10-20 12:12:51 +00:00
mercury 70466734fd checkin 2026-10-20-mercury.md 2026-10-20 12:06:30 +00:00
volt dc2b896e29 queue_claim_check: the docstring's pinned census is compared, not trusted
The UNITS section states 11 figures for revision abe08a9 and every one of them
is true there (verified against `git show abe08a9:WORK-QUEUE.md`). Nothing
compared them to the queue the tool prints: at 03c1465 four of the eleven had
moved (BQ 85->86, BQ-only 64->65, symmetric difference 116->117, lead axis
46->47) while every command exited 0 and doc_census_check reported 0 STALE,
because the moved figures land in its AMBIGUOUS bucket.

--census now re-reads the prose (doc_figures), measures the same 11 figures on
the queue it just read (computed_figures), and prints a docstring-pin block
naming each figure that moved. Exit code unchanged: a queue that grows is not a
fault. Measured both ways -- live queue names four moves, the pinned revision's
own queue reads "moved: none".

Cells 20 -> 24 (4 doc-pin). Mutant returning [] from doc_drift: 22/24, rc 1,
naming doc pin 2 and 4. Landed: 24/24, rc 0. The tool's plain report is
byte-identical before and after (diff rc 0). Gate 5/5, sweep 15/15, doc-census
0 STALE, ruff clean.
2026-10-20 01:34:32 +00:00
volt 4c0d8b575f checkin (volt): fifth tick postscript -- the selftest count is 51, cell 27 grades the docstring's own claim (81d2c0a) 2026-10-19 19:01:57 +00:00
volt f59a592e49 tools (volt): verify.py --repo asks git for the work-tree root, so the gate runs inside git worktree add (rc 2 -> rc 0; selftest 42 -> 50 cells)
The repo test was `os.path.isdir(<repo>/.git)`, which is wrong in both
directions. A LINKED worktree's `.git` is a 47-byte FILE (`gitdir: ...`), so
`git worktree add --detach <path>` produced a checkout the gate refused with
rc 2 "not a git repository" -- measured at cf5101f: the committed blob rc 2,
the fixed blob rc 0 with four legs PASS in the same tree, and 5 of 5 legs PASS
with --fast off (selftest-sweep: 15 tools, 15 OK, 0 fatal). An empty directory
named `.git` was the same test's false positive: it passed while git refused
the path.

`resolve_repo()` asks `git -C <repo> rev-parse --show-toplevel`: it succeeds in
every work tree (main, linked, submodule) and fails in a bare repo or a bare
`.git` directory. `--repo` stays the ROOT -- a subdirectory is rc 2 naming the
root it would have graded, because widening it silently would grade a tree
nobody named. Legs, rcs and --queue/--index semantics are untouched.

Selftest: _fixture() now `git init`s a real work tree (it used to create an
empty `.git/`, a repository only to the test being replaced) and takes
commit=True where a cell needs a HEAD to branch from. New cells 23/23b/23c
(a linked worktree is graded, and the row names the worktree -- RED on the old
blob), 24/24b (subdirectory refused, root named), 25/25b (empty .git refused),
26 (bare repo refused). 42 -> 50 cells, 50/50, rc 0.

No queue item opened or closed; no another-party file edited.
2026-10-19 18:56:07 +00:00
zephyrus-sparkborn 2ff4812595 check-in 2026-10-19 2026-10-19 13:07:13 +00:00
volt fdc4a2178d checkin (volt): the gate's fourth leg recorded -- queue block, index re-render, 09:37-09:50Z check-in
Queue block appends at the foot (offset 10080 -> 10094 lines, 1271673 ->
1276470 B): the measured hole (three-leg gate rc 0 on a clone whose
checkin_check --fail is rc 1), the leg's unit and cost (124-153 ms, cheapest,
first), why one day (35 historical faults, 2026-09-24..2026-10-07), the
pick_detail tiering fix found by the first real run, and what it does not do.
Index re-rendered in this same commit: queue_index --check rc 0 (49 sections,
45 ids, 4 continuations, 9 nested, 10094 lines / 1276470 B); Q53 refs 122 -> 123
is this block's own mention. No item opened or closed; open set unchanged
Q37:5278, Q53:7303.
2026-10-19 12:14:47 +00:00