| .. |
|
200-417c4a57-b2.json
|
The master's status discipline in the writer: four decisions, the p.139 record, the four approvals, several records per case; the REV ids from the master; INT-07's V6-12; the two kills as FAIL
|
2026-10-08 19:34:09 +00:00 |
|
201-7cfa422a-aa0e0f45.json
|
The master's status discipline in the writer: four decisions, the p.139 record, the four approvals, several records per case; the REV ids from the master; INT-07's V6-12; the two kills as FAIL
|
2026-10-08 19:34:09 +00:00 |
|
201-ef0f2ed8-2826f37e.json
|
The master's status discipline in the writer: four decisions, the p.139 record, the four approvals, several records per case; the REV ids from the master; INT-07's V6-12; the two kills as FAIL
|
2026-10-08 19:34:09 +00:00 |
|
202-a284380b-5f50afd1.json
|
2.0.2 pair gate: node a284380b on the key-succession pairing with the class v5 freeze, the kaspad check and five node suites GREEN on build-4; pow and app GREEN on 2427ad1e (no crate move to 75367c3b); batch 202-a284380b-75367c3b (the suites' cases NOT RUN in progress with the green logs, never PASS by inference)
|
2026-10-08 22:04:35 +00:00 |
|
202-d657e490-6b17f951.json
|
2.0.2 kit 1 pair gate: node d657e490 on the key-succession pairing with the class v5 freeze, the kaspad check and five node suites GREEN on build-4; pow and app GREEN on 2427ad1e (no crate move to 678279aa); batch 202-d657e490-678279aa
|
2026-10-08 22:18:02 +00:00 |
|
adversary-20261008-placed-8lane.json
|
Batch adversary-20261008-placed-8lane: adversary:d2b's evidence cited at the document (section 13); the mf results file stays on the branch until it lands (the recorder's tree rule since f7c6d511); the batch recorded on master's registry
|
2026-10-08 20:32:56 +00:00 |
|
amd-intel-energy-20261008-01.json
|
The identity grep covers the served registry's sources; the map's and three batch notes' rig names scrubbed; the island label (main's word): every record measured on the 2.0 devnet after 20:00 UK reads 'on an island, not a network', stamped at record time and by --label-islands at replay
|
2026-10-08 21:23:28 +00:00 |
|
canary-20261008-01.json
|
Rule 33: the fresh-install canary record (tools/ci/canary/<sha>.json, one file per sha with an artefacts list) and its check; publish-manifest.sh and publish-public.sh refuse an entry whose sha has no PASS record for its own artefact; the canary cell under INT-07 (BLOCKED tonight); the merge replays modified batches too (the kills re-record reaches master's rows); the identity words out of the map
|
2026-10-08 20:46:09 +00:00 |
|
canary-miner-fix-7cfa422a.json
|
The zone word scrubbed from two batch notes (the served registry); a landing stopped by its pid file releases the master-landing lock (INT and TERM)
|
2026-10-08 21:33:51 +00:00 |
|
census-v6-20261008-2034.json
|
Registry: census:class-v6 PASS (run census-v6-20261008-2034: the freeze's object hl-v6-all 4de7b836cc40a4ea at class-v6 9415e9c89 through the sub-version 3 harness; evidence docs/analysis/class-v6/census-packs.md sections 0 to 7)
|
2026-10-08 19:47:22 +00:00 |
|
census-v6-chainseed-20261008-2230.json
|
Class v6 census: the chain-seed draw 2a1d6caab4c24564 on the frozen object (the engine's pair: seed af89be5d, era genesis, day 20730, node1 state) through the (c''') rule and the attempts census, PASS; the block-hash-era draw beside it as the comparison; registry run census-v6-chainseed-20261008-2230
|
2026-10-08 21:23:10 +00:00 |
|
census-v6-chainseed-trace-20261008-2305.json
|
Registry: census:class-v6 run census-v6-chainseed-trace-20261008-2305 (the chain-seed row with the signing program's window trace)
|
2026-10-08 22:04:43 +00:00 |
|
census-v6-live-20261008-2210.json
|
Class v6 census: the live-dataset census on the frozen object 21edd23c9 (Phase 1 item (j)): hl-v6-all 4de7b836cc40a4ea and sixteen chain seeds on the chain's dataset with the node1 leaves under header-bound init words, uniform inside every window to the Poisson floor, F8 form 0.999x of the window model; F06's live half LIVE on every register and load; the registry run census-v6-live-20261008-2210
|
2026-10-08 21:12:34 +00:00 |
|
eco-d4-20261008-01.json
|
Class v6: the genesis dataset size DECIDED at 4 GiB (the founder's word at 20:00 UK, FROZEN as class_v6_dataset_steps [(0, 4096 MiB)]); change (3) and the served policy sentence as decided; the chip line's a-node-ahead end 3.3x with the floor marked
|
2026-10-08 19:31:58 +00:00 |
|
eco05-20261008-01.json
|
The master's status discipline in the writer: four decisions, the p.139 record, the four approvals, several records per case; the REV ids from the master; INT-07's V6-12; the two kills as FAIL
|
2026-10-08 19:34:09 +00:00 |
|
eco05-20261008-01b.json
|
Test registry: floor lane 3's batch eco05-20261008-01b (ECO-05 FAIL, ECO-01 and ECO-08 RUNNING at manifest 24883757; the rows move with their evidence files carried by this landing; the same run as batch 01, no result changed), recorded on the lane's word
|
2026-10-08 19:47:37 +00:00 |
|
eco05-20261008-02.json
|
ECO-05 batch 02 on the RX 7600's class v6 cell (15.79 MH/s measured, the knee 5.4 modelled; the metered knee is batch 03) and the B580's class v6 cell (11.0 measured, watts estimated): one more sustainable world (10R at 0.10, by 1.6 percent on the 7600's entry), 0 of 108 cells pass the envelope, RUN FAIL unchanged; the driver's override hook carried; the cubes and the registry rows recorded at manifest efd03e2c
|
2026-10-08 20:00:11 +00:00 |
|
enforced-proving-20261008-01.json
|
The master's status discipline in the writer: four decisions, the p.139 record, the four approvals, several records per case; the REV ids from the master; INT-07's V6-12; the two kills as FAIL
|
2026-10-08 19:34:09 +00:00 |
|
enforced-proving-20261008-02.json
|
The succession case's evidence in the tree (docs/plans/proving-enforcement/succession-360-window-300-vcache-7.json); the batch names it (the registry's evidence rule: a PASS names a file at HEAD)
|
2026-10-08 21:23:06 +00:00 |
|
enforced-proving-20261008-03.json
|
Merge remote-tracking branch 'box/master' into cache-history
|
2026-10-08 22:06:59 +00:00 |
|
f0-manifest-20261008-b.json
|
The master's status discipline in the writer: four decisions, the p.139 record, the four approvals, several records per case; the REV ids from the master; INT-07's V6-12; the two kills as FAIL
|
2026-10-08 19:34:09 +00:00 |
|
f0-manifest-20261008.json
|
The master's status discipline in the writer: four decisions, the p.139 record, the four approvals, several records per case; the REV ids from the master; INT-07's V6-12; the two kills as FAIL
|
2026-10-08 19:34:09 +00:00 |
|
f0-signing-20261008-2330.json
|
F0: the signing block (the class v6 freeze candidate 2a1d6caab4c24564 of 21edd23c9 at its pairing, the same-work and acceptance rows, the 2.0.2 pair gate, the prover row, the canary state, the network label); GOV-01 moves with the page
|
2026-10-08 22:13:43 +00:00 |
|
f03-manifest-20261008-01.json
|
The recorder drops a lifted reason-only record when a real cell lands and never counts it in the combined decision (R2-F03-R01 read NOT RUN beside its PASS cell); the F03 batch re-recorded
|
2026-10-08 20:53:54 +00:00 |
|
f10-worker-20261008.json
|
F10 rows, I05 epoch tag, I06 pack geometry rule across the three hosts
|
2026-10-08 19:53:24 +00:00 |
|
family-gate-20261008.json
|
Class v6 family gate, 6.12: the final tree (class-v6 38128dff0, the packs' draw read back equal on both ids) through the acceptance under the harness's predicate and the crate's own, which agree on a2af73716's fix (r 0.144 and 0.137 at width 4, 0 exhausted in 6,000 eras, the floors at 0 to 0.5 percent, the fold's half of the bit-R class): PASS; the registry batch at manifest 38128dff0, method native
|
2026-10-08 20:05:56 +00:00 |
|
family-gate-20261008b.json
|
Merge build/master into class-v6-family-gate: the CI steward's family-gate cell and batch taken as master has them; this landing's batch family-gate-20261008b moves the rows with their evidence; 6.12's subset census at 64 of 64 (0 hot sets, 0 over 1.2x)
|
2026-10-08 20:13:17 +00:00 |
|
family-gate-20261008c.json
|
The zone word scrubbed from two more batch notes landed after the branch point (the served registry)
|
2026-10-08 21:42:28 +00:00 |
|
fin-boundary-20261008-02.json
|
The master's status discipline in the writer: four decisions, the p.139 record, the four approvals, several records per case; the REV ids from the master; INT-07's V6-12; the two kills as FAIL
|
2026-10-08 19:34:09 +00:00 |
|
fin-boundary-20261008.json
|
The master's status discipline in the writer: four decisions, the p.139 record, the four approvals, several records per case; the REV ids from the master; INT-07's V6-12; the two kills as FAIL
|
2026-10-08 19:34:09 +00:00 |
|
fin-v4-realnode-20261008T2025Z.json
|
Registry batch: FIN-08 through the finality-sim cell (RUNNING, the real-node rows joined to the simulator's; the combined-boundary runs are tomorrow's plan), so sim/results_v2.md and its rows move together
|
2026-10-08 19:35:40 +00:00 |
|
floor-k-20261008-rows-repeat.json
|
Merge box/master 36816182c into class-v6-floor-k-docs-2 (the steward's 36816182 under it; the repeat batch trimmed to floor lane 2's rows ADV-05 and ADV-06, method model; the registry master's with that batch recorded)
|
2026-10-08 21:02:08 +00:00 |
|
hash-lane-20261008-batch1.json
|
The master's status discipline in the writer: four decisions, the p.139 record, the four approvals, several records per case; the REV ids from the master; INT-07's V6-12; the two kills as FAIL
|
2026-10-08 19:34:09 +00:00 |
|
hash-lane-20261008-batch2.json
|
test registry: the hash lane's batch 2 (the fleet's F05 rows on the post-review object as bench:fleet-pods evidence; suite:pow on the review-fix tree)
|
2026-10-08 19:51:34 +00:00 |
|
hash-lane-20261008-batch3.json
|
test registry: the hash lane's batch 3 (the pairing class: the chain-paired packs, the signing object's P01 reference, the export tool's pairing check)
|
2026-10-08 21:04:30 +00:00 |
|
incident-u64-coinbase-2026-10-08.json
|
The zone word scrubbed from two batch notes (the served registry); a landing stopped by its pid file releases the master-landing lock (INT and TERM)
|
2026-10-08 21:33:51 +00:00 |
|
kills-20261008.json
|
Merge remote-tracking branch 'box/master' into ci-rule33-canary
|
2026-10-08 20:53:44 +00:00 |
|
kit-class-v6-20261008-01.json
|
registry: the kit batch cites paths only in its evidence field (the page, zip 4, the emulation log on build-1) with the reading in a note; recorded RUNNING on R2-F03-R02
|
2026-10-08 20:44:04 +00:00 |
|
p01-20261008-01.json
|
The identity grep covers the served registry's sources; the map's and three batch notes' rig names scrubbed; the island label (main's word): every record measured on the 2.0 devnet after 20:00 UK reads 'on an island, not a network', stamped at record time and by --label-islands at replay
|
2026-10-08 21:23:28 +00:00 |
|
p01-partb-20261008-01.json
|
The master's status discipline in the writer: four decisions, the p.139 record, the four approvals, several records per case; the REV ids from the master; INT-07's V6-12; the two kills as FAIL
|
2026-10-08 19:34:09 +00:00 |
|
p02-fleet-pods-20261008-01.json
|
The identity grep covers the served registry's sources; the map's and three batch notes' rig names scrubbed; the island label (main's word): every record measured on the 2.0 devnet after 20:00 UK reads 'on an island, not a network', stamped at record time and by --label-islands at replay
|
2026-10-08 21:23:28 +00:00 |
|
pool-2.0-20261008-01.json
|
test map: suite:pool (UX-05 and UX-04 partial coverage); batch pool-2.0-20261008-01 RUNNING at 72cc306e8; the harness page regenerated on master's map
|
2026-10-08 19:15:13 +00:00 |
|
pool-2.0-20261008-03.json
|
registry: pool batch 03 at 7ffd29af with its evidence page docs/analysis/pool/pool-pair-2026-10-08.md (UX-05 vote-key PASS in the crate; the devnet-4 live pair NOT RUN, its wrong_hash an unsynced node's unsettled class v5 state, not a generator skew; the guard on pool-2.0; two 2.0 gaps closed)
|
2026-10-08 20:41:26 +00:00 |
|
pool-review-b-20261008-01.json
|
Pool review B record (documents and the registry batch only): docs/plans/pool.md section 11 (F12, F13, INT-04, INT-15 closed by construction on pool-review-b 786e09cc: what was, what is, the regressions, the consequences per tier), spec 09 section 9.3 (the frame bound while reading; binding v2, the exact bytes; welcome, authorize, authorized fields; the job row carries master's vote_key_hash and the pool line's seed fields together), the test map's suite:pool cell and the batch pool-review-b-20261008-01 (51 of 51 on build-6 against successor-2.0.1 515ba674, cargo check green against the manifest's node 7cfa422a; evidence build-1:/srv/artefacts/tas/pool-review-b-20261008-01/). The code lands on the release tree (the coordinator's ruling, 20:5x UK): the pool line sits 581 commits off master with conflicts in app, workflows and tools, and master's igneum-pow fingerprint a65e4c5a differs from the freeze's cbc5bd0a, so the pool crate builds from release-2.0.1 or the pool line, never from master's own igneum-pow (F03)
|
2026-10-08 19:52:09 +00:00 |
|
ra-20261008T1744-evm.json
|
The master's status discipline in the writer: four decisions, the p.139 record, the four approvals, several records per case; the REV ids from the master; INT-07's V6-12; the two kills as FAIL
|
2026-10-08 19:34:09 +00:00 |
|
ra-20261008T1746-ver.json
|
The master's status discipline in the writer: four decisions, the p.139 record, the four approvals, several records per case; the REV ids from the master; INT-07's V6-12; the two kills as FAIL
|
2026-10-08 19:34:09 +00:00 |
|
ra-20261008T1915-ver.json
|
Reference apps F04 in the acceptance layer: run ra-20261008T1915-ver recorded, VER-05 in its own cell
|
2026-10-08 19:15:55 +00:00 |
|
review-harness-20261008T180034Z.json
|
The master's status discipline in the writer: four decisions, the p.139 record, the four approvals, several records per case; the REV ids from the master; INT-07's V6-12; the two kills as FAIL
|
2026-10-08 19:34:09 +00:00 |
|
same-work-20261008-01.json
|
same-work 01: the 4090 PASS on all three phases of the frozen object (read back on build-1 23:22 to 23:25 UK); the 3090's copy fault named on both rows
|
2026-10-08 22:30:35 +00:00 |
|
same-work-20261008-02.json
|
same-work 01: the 4090 PASS on all three phases of the frozen object (read back on build-1 23:22 to 23:25 UK); the 3090's copy fault named on both rows
|
2026-10-08 22:30:35 +00:00 |
|
same-work-20261008-03.json
|
same-work: the batch notes and contexts name no rig short name (the acceptance page rule, 22:4x UK); statuses unchanged
|
2026-10-08 21:43:02 +00:00 |
|
site-manifest-20261008-01.json
|
registry: OPS-03 manifest cell recorded with a real evidence path
|
2026-10-08 20:50:48 +00:00 |
|
ux-01-20261008-win-2.0.0.json
|
UX-01 batch: method team-reported (the recorder's rule since cba311f5: never conflated)
|
2026-10-08 20:20:58 +00:00 |
|
v607-floor-memory-20261008T2059Z.json
|
V6-07: the batch in the steward's current form (method GPU, release identity, claim impact) recorded into the merged registry
|
2026-10-08 22:13:20 +00:00 |
