Documents only: docs/analysis/class-v6/amd-intel-energy.md and docs/analysis/class-v6/amd-intel-energy/ (the three job scripts, the Level Zero sampler source, the offline-compile prelude and ISA summary).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Documents-only replay of d9e91c5d7 (d9e91c5d7a) for the box mirror master
tools/fleet/box-prover.py point 6: each claimed segment is an eligible job and closes once as paid, expired (unpaid, held_expired) or cancelled (disk, export, cut, chain, timeout, shards, statement, sign, refused), active until then; the row carries outcome, cause, deadline, margin at the claim, seconds spent (wasted unless paid) and the deadline miss; the state carries the counters and the wasted seconds by cause; every close is a RESULT outcome line, the run ends with a RESULT ledger line.
tools/fleet/prover-outcomes.py: the report over state files and logs (a log from before the ledger is reconstructed from its RESULT lines; a state row wins over a log row): outcomes, paid completions (segments, shards, IGN, median end to end, median time to pay, median margin), missed deadlines by cause with the median miss (never negative, none on a stale tip), wasted work by cause, throughput per hour and the paid share of the seconds spent, the open jobs. --self-test to known numbers (known-failed first), run by the gate. tools/fleet/night.py sums the fleet's counters into its hourly row. docs/analysis/proving-outcome-ledger.md: the definitions and how to read the three ratios.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The verification rows re-run on the 2.0 devnet with the lock-state code: VER-03, VER-04, VER-06, VER-08 pass (coverage names
the F04 cases), VER-01 and VER-02 FAIL by design, VER-05 FAIL on this run because the public read node now reports
startedFrom snapshot (the reader on build-1 is still from genesis); VER-05 moves to harness:reference-apps-ver-availability
so its verdict never drags the other rows. Recorded through test-record.mjs; the harness map page regenerated.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Documents only. The master (292 pages) governs where it differs from the
plan PDF or the RTF; 18 INT gates and 44 R2 closure requirements become
suites INT and REV in the acceptance registry (CI steward).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
tools/ci/review-suite.mjs writes the REV suite from docs/analysis/review-2026-10-08-b/findings.json and dispatch.md: one case per required regression (REV-F01-1 onward), the regression line verbatim as title and accept, status NOT RUN, the owner lane from the dispatch table, the finding id and priority carried as fields; every unmapped case gets a NOT RUN reason in tools/ci/test-map.json naming its owner lane; the gate's check refuses a registry whose REV suite drifts from the findings. The founder's 19:57 rulings on F04 (the recovery lock kept, always labelled recovery) and F14 (the public miner from 2.0.2 without remote jobs; the lab build for our fleet) are dated notes on the FIN, UX and OPS suites through test-record.mjs --note, and resolved fields in F0. The harness page is regenerated.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Batch 201-7cfa422a-38351afd: node 7cfa422a (the miner base-unit fix, amended after 777214af's self-recursive connect failed to compile under the steward's read) green on the kaspad check and five suites on build-4 over the key-succession pairing; miner cut tip 38351afd (crate identical to 3c13a71c) green on pow and app on build-2. F0 names those pins and records the founder's 19:57 rulings on F04 (the recovery lock kept and always labelled recovery) and F14 (the public miner from 2.0.2 without remote jobs; the lab build for our fleet) as resolved. Tools: proof-rule-bypass-check.sh (F02: the test bypass cannot reach a release build; a cell of the node matrix from now, red until the proving lane's change lands); test-map-merge.py and the page regeneration at the merge (two lanes' cells no longer collide as text); push_race in merge-to-master.sh (a push that lost master's compare-and-swap retries without re-running the hook; twelve tries); review-suite.mjs (the REV suite generated from a review's findings and dispatch, written in the next commit once Review B is on master); test-record.mjs --note (a dated note on a suite, never an accept text).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
GPU-01, GPU-03 and POW-08 take run_status RUNNING with the evidence rows on build-1 under /srv/artefacts/tas/p02-rows; PASS waits on the AMD cells, the 1080 Ti cell and the re-exported v6 packs.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Documents only. Fourteen findings F01 to F14 with forty-four regressions,
dispatched by lane in dispatch.md; the regressions become suite REV in the
acceptance registry (CI steward).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The map gains harness:reference-apps-compat (EVM-02 to EVM-06, partial coverage named per case), harness:reference-apps-ver
(VER-03 to VER-06 and VER-08) and harness:reference-apps-ver-trust-anchor (VER-01 and VER-02, FAIL by design and disclosed).
Batches ra-20261008T1744-evm (22 of 22 rows on the 2.0 devnet, node 4cdcc488) and ra-20261008T1746-ver (evidence per case
under tools/reference-apps/ver/evidence) are recorded with node tools/ci/test-record.mjs --record; the harness map page is
regenerated; the registry rows move with their evidence (site/lc/verify-receipt.js rebuilt in this landing).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
