The registry rebuilt on master 259f799e: normalised to the four decisions, the kills as FAIL, REV with the master ids, INT with V6-12, the notes
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs
parent
062931f6e5
commit
bbdc4eb14c
2 changed files with 6728 additions and 655 deletions
|
|
@ -1,6 +1,6 @@
|
|||
# Igneum 2.0 test harness map
|
||||
|
||||
Generated from tools/ci/test-map.json by tools/ci/test-map-doc.mjs; edit the JSON, never this page. Registry: docs/plans/igneum-2.0-test-registry.json (172 cases).
|
||||
Generated from tools/ci/test-map.json by tools/ci/test-map-doc.mjs; edit the JSON, never this page. Registry: docs/plans/igneum-2.0-test-registry.json (190 cases).
|
||||
|
||||
Rule: a case maps to a cell only where the cell's tests visibly answer it; coverage names what the cell proves and what remains; a mapped cell's green writes RUNNING, PASS only when coverage is full and the evidence file exists; an automated case with no cell reads NOT RUN with its reason, never PASS by inference.
|
||||
|
||||
|
|
@ -13,7 +13,6 @@ Rule: a case maps to a cell only where the cell's tests visibly answer it; cover
|
|||
- Fixtures: F0, F1
|
||||
- Cases:
|
||||
- POW-02 Validate generated programs and index folding: partial: program derivation, ds55 geometry, the v6 fold, the packs and the spec read-back tests; the independent re-implementation and the index-fold census are the hash lane's harnesses
|
||||
- POW-07 Constrain any mixed-resource or FP32 branch: the mixed FP32 branch is excluded and unreachable: no class flag reaches an FP op in igneum-pow on master (the mixedfp lane's branch is not on master); evidence the grep of the emitters on master, recorded by the hash lane
|
||||
- POW-08 Keep rejected mechanisms out of the shipped claim: partial: the freeze list and the generator version pin; the public-claim scrub is the site gate's
|
||||
|
||||
### suite:app
|
||||
|
|
@ -268,6 +267,22 @@ Rule: a case maps to a cell only where the cell's tests visibly answer it; cover
|
|||
- UX-05 Keep voting keys with the miner through pooling: partial: the vote-key commitment on the wire (verify::tests::a_share_under_another_key_is_refused_before_the_hash: known-pass the member's key, known-fail another key on the share and a job naming another key, refused with code vote_key before the hash), the open pool's sidechain::check_key (the claimed key, the header's key and the reveal are one key), the same-nonce-other-template wrong_hash test, the TLS binding test; the malicious-pool run and the leave-and-retain run on the devnet-4 pair are the UX-05 batch's other evidence
|
||||
- UX-04 Pay small operators without hidden custody: partial: PPLNS distribution tests (fee first, never overpays, late joiner), the payout key file round trip, the signed transfer decode; the live payout path on the devnet-4 pair is the UX-04 batch's evidence
|
||||
|
||||
### experiment:connected-state
|
||||
|
||||
- Command: `the connected-state experiment (the class v6 cs64 research class and its liveness tool; the lane's rows in docs/analysis/class-v6/), KILLED 8 October 2026: live state is free for a chip, only width counts`
|
||||
- Box class: experiment (rented pods)
|
||||
- Fixtures: F2, F3
|
||||
- Cases:
|
||||
- POW-03 Test whether live state is unavoidable: the experiment ran and its claim failed: live state does not make the work unavoidable for a chip; the master's register row 18 reads FAIL, published, never PASSED
|
||||
|
||||
### experiment:mixed-fp32
|
||||
|
||||
- Command: `the mixed-FP32 candidate (determinism proved CPU against CUDA, +15 to 26 percent card energy, the chip edge grows), KILLED 8 October 2026`
|
||||
- Box class: experiment (rented pods)
|
||||
- Fixtures: F2, F3
|
||||
- Cases:
|
||||
- POW-07 Constrain any mixed-resource or FP32 branch: the branch ran and its claim failed: the FP32 branch costs the card more energy and widens the chip edge; the master's register row 12 reads FAIL, published; the branch is excluded and unreachable on master (the grep evidence stays)
|
||||
|
||||
## Automated cases with no harness in the matrix (NOT RUN, the reason)
|
||||
|
||||
- GOV-02 Approve thresholds before results: the approval is recorded in the registry's approval field; the automated half (thresholds frozen before any run_status) is the gate rule landing by 21:00
|
||||
|
|
@ -328,51 +343,113 @@ Rule: a case maps to a cell only where the cell's tests visibly answer it; cover
|
|||
- LEAD-05 Measure control and dependency concentration: observation window
|
||||
- LEAD-06 Complete the reliability observation window: observation window
|
||||
- LEAD-08 Keep leadership claims valid after release: observation window
|
||||
- REV-F01-1 Valid proof A, warm cache, carried statement B: refuse exactly as a cold node does.: F01 (P0, the external review): the regression's harness is the owner lane's (proving lane, node lane); not yet named in the map
|
||||
- REV-F01-2 Run valid/invalid contexts in both orders, concurrently and across cache eviction/restart.: F01 (P0, the external review): the regression's harness is the owner lane's (proving lane, node lane); not yet named in the map
|
||||
- REV-F01-3 Change payout, network, kind, program ID and activation context; no accepted misbinding.: F01 (P0, the external review): the regression's harness is the owner lane's (proving lane, node lane); not yet named in the map
|
||||
- REV-F01-4 A native two-node test must agree on block validity and payouts despite different cache histories.: F01 (P0, the external review): the regression's harness is the owner lane's (proving lane, node lane); not yet named in the map
|
||||
- REV-F02-1 Release build cannot activate test bypass.: F02 (P0, the external review): the regression's harness is the owner lane's (proving lane, CI steward); not yet named in the map
|
||||
- REV-F02-2 Missing oracle or pinned keys prevents service readiness after enforcement activation.: F02 (P0, the external review): the regression's harness is the owner lane's (proving lane, CI steward); not yet named in the map
|
||||
- REV-F02-3 Missing proof bytes retry without incorrectly marking a valid block permanently invalid.: F02 (P0, the external review): the regression's harness is the owner lane's (proving lane, CI steward); not yet named in the map
|
||||
- REV-F03-1 Clean build from one manifest, including the pool and workers, with no unpublished vendor tree.: F03 (P0, the external review): the regression's harness is the owner lane's (CI steward, hash lane (ProgramClass::V6 on freeze), pool lane); not yet named in the map
|
||||
- REV-F03-2 Same job context produces identical accepted work in node, CPU reference, CUDA, Metal, OpenCL and pool.: F03 (P0, the external review): the regression's harness is the owner lane's (CI steward, hash lane (ProgramClass::V6 on freeze), pool lane); not yet named in the map
|
||||
- REV-F03-3 Cross every scheduled transition with old/new client behavior documented and identical rule identities.: F03 (P0, the external review): the regression's harness is the owner lane's (CI steward, hash lane (ProgramClass::V6 on freeze), pool lane); not yet named in the map
|
||||
- REV-F04-1 Native multi-node 40/40/20 partition, equivocation and dust-valid mining on both sides past the window.: F04 (P0, the external review): the regression's harness is the owner lane's (node lane, reference apps, site (explorer)); not yet named in the map
|
||||
- REV-F04-2 Proof that the chosen recovery guarantee matches the public finality claim; two valid contradictory certificates are a hard failure for strong finality.: F04 (P0, the external review): the regression's harness is the owner lane's (node lane, reference apps, site (explorer)); not yet named in the map
|
||||
- REV-F04-3 Pause-only resume with historical backfill, missing historical data and all old keys returning.: F04 (P0, the external review): the regression's harness is the owner lane's (node lane, reference apps, site (explorer)); not yet named in the map
|
||||
- REV-F04-4 Wallet, receipt and oracle consumers distinguish any weaker recovery state.: F04 (P0, the external review): the regression's harness is the owner lane's (node lane, reference apps, site (explorer)); not yet named in the map
|
||||
- REV-F05-1 Native reference-vs-incremental expression equivalence across all source registers and real instruction updates.: F05 (P1, the external review): the regression's harness is the owner lane's (hash lane, adversary lane, floor lane 3); not yet named in the map
|
||||
- REV-F05-2 Full-kernel output equivalence, registers, spills, wall power and accepted throughput across target GPUs.: F05 (P1, the external review): the regression's harness is the owner lane's (hash lane, adversary lane, floor lane 3); not yet named in the map
|
||||
- REV-F05-3 Adversary physical design includes prefix caching/recomputation cost; no assumed full 63-read cost on every load.: F05 (P1, the external review): the regression's harness is the owner lane's (hash lane, adversary lane, floor lane 3); not yet named in the map
|
||||
- REV-F06-1 Acceptance/reference/emitter evaluate the same activated schedule.: F06 (P1, the external review): the regression's harness is the owner lane's (hash lane, research lane D); not yet named in the map
|
||||
- REV-F06-2 Full live-dataset census on unseen seeds and the complete v6 pack.: F06 (P1, the external review): the regression's harness is the owner lane's (hash lane, research lane D); not yet named in the map
|
||||
- REV-F06-3 A failed experimental rule does not silently exhaust generation or bypass the intended resource requirement.: F06 (P1, the external review): the regression's harness is the owner lane's (hash lane, research lane D); not yet named in the map
|
||||
- REV-F07-1 Same final v6 configuration: mine -> evict -> prove -> aggregate -> submit -> rebuild -> resume; no leaked reservations.: F07 (P1, the external review): the regression's harness is the owner lane's (app lane, fleet lane); not yet named in the map
|
||||
- REV-F07-2 OOM, process crash and stale work recover without losing wallet state or silently consuming power.: F07 (P1, the external review): the regression's harness is the owner lane's (app lane, fleet lane); not yet named in the map
|
||||
- REV-F07-3 16 GB+ simultaneous mode only after measured peak plus next-epoch headroom; smaller-card modes labelled separately.: F07 (P1, the external review): the regression's harness is the owner lane's (app lane, fleet lane); not yet named in the map
|
||||
- REV-F08-1 Report every eligible job outcome, including expired work; a bounded list cannot hide losses.: F08 (P1, the external review): the regression's harness is the owner lane's (proving lane, fleet lane, site (ops page)); not yet named in the map
|
||||
- REV-F08-2 Consumer tiers complete and receive payment for declared jobs before claims about income.: F08 (P1, the external review): the regression's harness is the owner lane's (proving lane, fleet lane, site (ops page)); not yet named in the map
|
||||
- REV-F08-3 Sustained real workload across class transitions, with restart/retry and no publisher intervention.: F08 (P1, the external review): the regression's harness is the owner lane's (proving lane, fleet lane, site (ops page)); not yet named in the map
|
||||
- REV-F09-1 Generate all pass/fail cells directly from the declared inequalities and inputs.: F09 (P1, the external review): the regression's harness is the owner lane's (research lane, floor lane 3, coordinator); not yet named in the map
|
||||
- REV-F09-2 Independent feasibility and cost evaluation of the strongest modeled SRAM/hybrid opponent.: F09 (P1, the external review): the regression's harness is the owner lane's (research lane, floor lane 3, coordinator); not yet named in the map
|
||||
- REV-F09-3 GPU owners and entrants remain viable under the approved scenario envelope without assuming chip absence or death.: F09 (P1, the external review): the regression's harness is the owner lane's (research lane, floor lane 3, coordinator); not yet named in the map
|
||||
- REV-F10-1 Compare exact found nonce/hash sets with full-read mode, including all-hit overflow and zero-hit cases.: F10 (P2, the external review): the regression's harness is the owner lane's (worker lane (new)); not yet named in the map
|
||||
- REV-F10-2 Test stale jobs, high-32 rollover, tail batches and asynchronous buffer reuse.: F10 (P2, the external review): the regression's harness is the owner lane's (worker lane (new)); not yet named in the map
|
||||
- REV-F10-3 Compare production throughput and wall energy, not only the isolated kernel timer.: F10 (P2, the external review): the regression's harness is the owner lane's (worker lane (new)); not yet named in the map
|
||||
- REV-F11-1 Goal switch from an efficiency prior can explore higher core/power when policy allows.: F11 (P2, the external review): the regression's harness is the owner lane's (Ember lane (new)); not yet named in the map
|
||||
- REV-F11-2 Driver, workload, dataset, compiler and device changes invalidate certification while retaining optional hints.: F11 (P2, the external review): the regression's harness is the owner lane's (Ember lane (new)); not yet named in the map
|
||||
- REV-F11-3 Thermal/error/late-share events revert safely, including process or machine crash.: F11 (P2, the external review): the regression's harness is the owner lane's (Ember lane (new)); not yet named in the map
|
||||
- REV-F12-1 Crash before/after broadcast, response timeout, restart before snapshot: no duplicate payment or silent debt loss.: F12 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- REV-F12-2 Same signed transaction retried, fee replacement reconciled by intent, not a new payment.: F12 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- REV-F12-3 Receipt reorg and finality pause leave correct pending obligations.: F12 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- REV-F13-1 Repeated authorization rejected or atomically replaces and cleans prior state.: F13 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- REV-F13-2 Oversized unterminated frame rejected within fixed memory/time budget.: F13 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- REV-F13-3 Slow clients and invalid share floods cannot grow unbounded member, nonce or outgoing state.: F13 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- REV-F14-1 Public build has no default arbitrary remote execution and a documented least-privilege boundary.: F14 (P1, the external review): the regression's harness is the owner lane's (app lane, relay lane); not yet named in the map
|
||||
- REV-F14-2 Automatic updates off remains off for urgent manifests until explicit action.: F14 (P1, the external review): the regression's harness is the owner lane's (app lane, relay lane); not yet named in the map
|
||||
- REV-F14-3 A compromised fleet/update signing key cannot silently acquire wallet access or activate a consensus change.: F14 (P1, the external review): the regression's harness is the owner lane's (app lane, relay lane); not yet named in the map
|
||||
- REV-F01-1 : F01 (P0, the external review): the regression's harness is the owner lane's (proving lane, node lane); not yet named in the map
|
||||
- REV-F01-2 : F01 (P0, the external review): the regression's harness is the owner lane's (proving lane, node lane); not yet named in the map
|
||||
- REV-F01-3 : F01 (P0, the external review): the regression's harness is the owner lane's (proving lane, node lane); not yet named in the map
|
||||
- REV-F01-4 : F01 (P0, the external review): the regression's harness is the owner lane's (proving lane, node lane); not yet named in the map
|
||||
- REV-F02-1 : F02 (P0, the external review): the regression's harness is the owner lane's (proving lane, CI steward); not yet named in the map
|
||||
- REV-F02-2 : F02 (P0, the external review): the regression's harness is the owner lane's (proving lane, CI steward); not yet named in the map
|
||||
- REV-F02-3 : F02 (P0, the external review): the regression's harness is the owner lane's (proving lane, CI steward); not yet named in the map
|
||||
- REV-F03-1 : F03 (P0, the external review): the regression's harness is the owner lane's (CI steward, hash lane (ProgramClass::V6 on freeze), pool lane); not yet named in the map
|
||||
- REV-F03-2 : F03 (P0, the external review): the regression's harness is the owner lane's (CI steward, hash lane (ProgramClass::V6 on freeze), pool lane); not yet named in the map
|
||||
- REV-F03-3 : F03 (P0, the external review): the regression's harness is the owner lane's (CI steward, hash lane (ProgramClass::V6 on freeze), pool lane); not yet named in the map
|
||||
- REV-F04-1 : F04 (P0, the external review): the regression's harness is the owner lane's (node lane, reference apps, site (explorer)); not yet named in the map
|
||||
- REV-F04-2 : F04 (P0, the external review): the regression's harness is the owner lane's (node lane, reference apps, site (explorer)); not yet named in the map
|
||||
- REV-F04-3 : F04 (P0, the external review): the regression's harness is the owner lane's (node lane, reference apps, site (explorer)); not yet named in the map
|
||||
- REV-F04-4 : F04 (P0, the external review): the regression's harness is the owner lane's (node lane, reference apps, site (explorer)); not yet named in the map
|
||||
- REV-F05-1 : F05 (P1, the external review): the regression's harness is the owner lane's (hash lane, adversary lane, floor lane 3); not yet named in the map
|
||||
- REV-F05-2 : F05 (P1, the external review): the regression's harness is the owner lane's (hash lane, adversary lane, floor lane 3); not yet named in the map
|
||||
- REV-F05-3 : F05 (P1, the external review): the regression's harness is the owner lane's (hash lane, adversary lane, floor lane 3); not yet named in the map
|
||||
- REV-F06-1 : F06 (P1, the external review): the regression's harness is the owner lane's (hash lane, research lane D); not yet named in the map
|
||||
- REV-F06-2 : F06 (P1, the external review): the regression's harness is the owner lane's (hash lane, research lane D); not yet named in the map
|
||||
- REV-F06-3 : F06 (P1, the external review): the regression's harness is the owner lane's (hash lane, research lane D); not yet named in the map
|
||||
- REV-F07-1 : F07 (P1, the external review): the regression's harness is the owner lane's (app lane, fleet lane); not yet named in the map
|
||||
- REV-F07-2 : F07 (P1, the external review): the regression's harness is the owner lane's (app lane, fleet lane); not yet named in the map
|
||||
- REV-F07-3 : F07 (P1, the external review): the regression's harness is the owner lane's (app lane, fleet lane); not yet named in the map
|
||||
- REV-F08-1 : F08 (P1, the external review): the regression's harness is the owner lane's (proving lane, fleet lane, site (ops page)); not yet named in the map
|
||||
- REV-F08-2 : F08 (P1, the external review): the regression's harness is the owner lane's (proving lane, fleet lane, site (ops page)); not yet named in the map
|
||||
- REV-F08-3 : F08 (P1, the external review): the regression's harness is the owner lane's (proving lane, fleet lane, site (ops page)); not yet named in the map
|
||||
- REV-F09-1 : F09 (P1, the external review): the regression's harness is the owner lane's (research lane, floor lane 3, coordinator); not yet named in the map
|
||||
- REV-F09-2 : F09 (P1, the external review): the regression's harness is the owner lane's (research lane, floor lane 3, coordinator); not yet named in the map
|
||||
- REV-F09-3 : F09 (P1, the external review): the regression's harness is the owner lane's (research lane, floor lane 3, coordinator); not yet named in the map
|
||||
- REV-F10-1 : F10 (P2, the external review): the regression's harness is the owner lane's (worker lane (new)); not yet named in the map
|
||||
- REV-F10-2 : F10 (P2, the external review): the regression's harness is the owner lane's (worker lane (new)); not yet named in the map
|
||||
- REV-F10-3 : F10 (P2, the external review): the regression's harness is the owner lane's (worker lane (new)); not yet named in the map
|
||||
- REV-F11-1 : F11 (P2, the external review): the regression's harness is the owner lane's (Ember lane (new)); not yet named in the map
|
||||
- REV-F11-2 : F11 (P2, the external review): the regression's harness is the owner lane's (Ember lane (new)); not yet named in the map
|
||||
- REV-F11-3 : F11 (P2, the external review): the regression's harness is the owner lane's (Ember lane (new)); not yet named in the map
|
||||
- REV-F12-1 : F12 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- REV-F12-2 : F12 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- REV-F12-3 : F12 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- REV-F13-1 : F13 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- REV-F13-2 : F13 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- REV-F13-3 : F13 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- REV-F14-1 : F14 (P1, the external review): the regression's harness is the owner lane's (app lane, relay lane); not yet named in the map
|
||||
- REV-F14-2 : F14 (P1, the external review): the regression's harness is the owner lane's (app lane, relay lane); not yet named in the map
|
||||
- REV-F14-3 : F14 (P1, the external review): the regression's harness is the owner lane's (app lane, relay lane); not yet named in the map
|
||||
- INT-01 Real proof H cannot authenticate a different statement under a warm cache.: INT-01 (R1 integration gate): the gate's harness is the owner lane's (proving lane (a6e8f84588b809d62)); not yet named in the map
|
||||
- INT-02 Warm/cold/relay/restart/concurrent cache order does not change block or payout decisions; negative cache isolated.: INT-02 (R1 integration gate): the gate's harness is the owner lane's (proving lane (a6e8f84588b809d62)); not yet named in the map
|
||||
- INT-03 Durable payout outbox survives every crash/RPC boundary without duplicate or lost liabilities.: INT-03 (R1 integration gate): the gate's harness is the owner lane's (pool lane (a1c484c48a62948c2)); not yet named in the map
|
||||
- INT-04 Corrupt existing pool state, disk-full and reorg cause safe recovery, not silent empty balances.: INT-04 (R1 integration gate): the gate's harness is the owner lane's (pool lane (a1c484c48a62948c2)); not yet named in the map
|
||||
- INT-05 The supplied finality implementation matches the approved anchor rule after >window healing.: INT-05 (R1 integration gate): the gate's harness is the owner lane's (node lane (a283f5f0d364ceef0)); not yet named in the map
|
||||
- INT-06 Recovery tests state and preserve their weaker fault bound; interfaces never label it as a stronger guarantee.: INT-06 (R1 integration gate): the gate's harness is the owner lane's (node lane (a283f5f0d364ceef0)); not yet named in the map
|
||||
- INT-07 One v6 object agrees in node, pool, CPU verifier and each supported GPU host across activation.: INT-07 (R1 integration gate): the gate's harness is the owner lane's (CI steward with the hash lane (a690540514aa453d7) and the worker lane (a9e87343f008e0edd)); not yet named in the map
|
||||
- INT-08 Census, production acceptance, schedule counters and live-dataset tests use the identical frozen contract.: INT-08 (R1 integration gate): the gate's harness is the owner lane's (CI steward with the hash lane (a690540514aa453d7) and the worker lane (a9e87343f008e0edd)); not yet named in the map
|
||||
- INT-09 Eight- and twelve-GiB epoch transitions recover deliberately without relying on repeated OOM/watchdog cycles.: INT-09 (R1 integration gate): the gate's harness is the owner lane's (app lane); not yet named in the map
|
||||
- INT-10 Metal/CUDA/OpenCL exact dataset geometry agrees; unsupported packs reject before launch.: INT-10 (R1 integration gate): the gate's harness is the owner lane's (CI steward with the hash lane (a690540514aa453d7) and the worker lane (a9e87343f008e0edd)); not yet named in the map
|
||||
- INT-11 Only a memory-reserved proving job launches; mining buffers really release when required.: INT-11 (R1 integration gate): the gate's harness is the owner lane's (app lane); not yet named in the map
|
||||
- INT-12 Transient shard errors can retry safely; expiration, loss and paid work remain distinct durable outcomes.: INT-12 (R1 integration gate): the gate's harness is the owner lane's (proving lane (a6e8f84588b809d62) and fleet lane (ac055d60427caab99)); not yet named in the map
|
||||
- INT-13 Ember cannot retain a rate-ineligible prior; material workload changes invalidate incompatible profiles.: INT-13 (R1 integration gate): the gate's harness is the owner lane's (Ember lane (a04fe3451877e2ff0) with the app lane); not yet named in the map
|
||||
- INT-14 Protected helper and per-device leases restore owned settings on normal/abnormal exit; real ACL/security tests.: INT-14 (R1 integration gate): the gate's harness is the owner lane's (Ember lane (a04fe3451877e2ff0) with the app lane); not yet named in the map
|
||||
- INT-15 Public PoP replay is not session authorization; payout/server/network binding enforced.: INT-15 (R1 integration gate): the gate's harness is the owner lane's (pool lane (a1c484c48a62948c2)); not yet named in the map
|
||||
- INT-16 Pool parsing/queues/connection and crypto budgets remain bounded under controlled adversarial traffic.: INT-16 (R1 integration gate): the gate's harness is the owner lane's (pool lane (a1c484c48a62948c2)); not yet named in the map
|
||||
- INT-17 Missing oracle/keys/mandatory real-proof fixture blocks the applicable production acceptance gate.: INT-17 (R1 integration gate): the gate's harness is the owner lane's (proving lane (a6e8f84588b809d62)); not yet named in the map
|
||||
- INT-18 Whole-system economics pass the strongest feasible adversary, including sunk development and multi-epoch survival.: INT-18 (R1 integration gate): the gate's harness is the owner lane's (research lane (ad6a2bd47d4a46105)); not yet named in the map
|
||||
- R2-F01-R01 Valid proof A, warm cache, carried statement B: refuse exactly as a cold node does.: R2-F01 (P0, the external review): the regression's harness is the owner lane's (proving lane, node lane); not yet named in the map
|
||||
- R2-F01-R02 Run valid/invalid contexts in both orders, concurrently and across cache eviction/restart.: R2-F01 (P0, the external review): the regression's harness is the owner lane's (proving lane, node lane); not yet named in the map
|
||||
- R2-F01-R03 Change payout, network, kind, program ID and activation context; no accepted misbinding.: R2-F01 (P0, the external review): the regression's harness is the owner lane's (proving lane, node lane); not yet named in the map
|
||||
- R2-F01-R04 A native two-node test must agree on block validity and payouts despite different cache histories.: R2-F01 (P0, the external review): the regression's harness is the owner lane's (proving lane, node lane); not yet named in the map
|
||||
- R2-F02-R01 Release build cannot activate test bypass.: R2-F02 (P0, the external review): the regression's harness is the owner lane's (proving lane, CI steward); not yet named in the map
|
||||
- R2-F02-R02 Missing oracle or pinned keys prevents service readiness after enforcement activation.: R2-F02 (P0, the external review): the regression's harness is the owner lane's (proving lane, CI steward); not yet named in the map
|
||||
- R2-F02-R03 Missing proof bytes retry without incorrectly marking a valid block permanently invalid.: R2-F02 (P0, the external review): the regression's harness is the owner lane's (proving lane, CI steward); not yet named in the map
|
||||
- R2-F03-R01 Clean build from one manifest, including the pool and workers, with no unpublished vendor tree.: R2-F03 (P0, the external review): the regression's harness is the owner lane's (CI steward, hash lane (ProgramClass::V6 on freeze), pool lane); not yet named in the map
|
||||
- R2-F03-R02 Same job context produces identical accepted work in node, CPU reference, CUDA, Metal, OpenCL and pool.: R2-F03 (P0, the external review): the regression's harness is the owner lane's (CI steward, hash lane (ProgramClass::V6 on freeze), pool lane); not yet named in the map
|
||||
- R2-F03-R03 Cross every scheduled transition with old/new client behavior documented and identical rule identities.: R2-F03 (P0, the external review): the regression's harness is the owner lane's (CI steward, hash lane (ProgramClass::V6 on freeze), pool lane); not yet named in the map
|
||||
- R2-F04-R01 Native multi-node 40/40/20 partition, equivocation and dust-valid mining on both sides past the window.: R2-F04 (P0, the external review): the regression's harness is the owner lane's (node lane, reference apps, site (explorer)); not yet named in the map
|
||||
- R2-F04-R02 Proof that the chosen recovery guarantee matches the public finality claim; two valid contradictory certificates are a hard failure for strong finality.: R2-F04 (P0, the external review): the regression's harness is the owner lane's (node lane, reference apps, site (explorer)); not yet named in the map
|
||||
- R2-F04-R03 Pause-only resume with historical backfill, missing historical data and all old keys returning.: R2-F04 (P0, the external review): the regression's harness is the owner lane's (node lane, reference apps, site (explorer)); not yet named in the map
|
||||
- R2-F04-R04 Wallet, receipt and oracle consumers distinguish any weaker recovery state.: R2-F04 (P0, the external review): the regression's harness is the owner lane's (node lane, reference apps, site (explorer)); not yet named in the map
|
||||
- R2-F05-R01 Native reference-vs-incremental expression equivalence across all source registers and real instruction updates.: R2-F05 (P1, the external review): the regression's harness is the owner lane's (hash lane, adversary lane, floor lane 3); not yet named in the map
|
||||
- R2-F05-R02 Full-kernel output equivalence, registers, spills, wall power and accepted throughput across target GPUs.: R2-F05 (P1, the external review): the regression's harness is the owner lane's (hash lane, adversary lane, floor lane 3); not yet named in the map
|
||||
- R2-F05-R03 Adversary physical design includes prefix caching/recomputation cost; no assumed full 63-read cost on every load.: R2-F05 (P1, the external review): the regression's harness is the owner lane's (hash lane, adversary lane, floor lane 3); not yet named in the map
|
||||
- R2-F06-R01 Acceptance/reference/emitter evaluate the same activated schedule.: R2-F06 (P1, the external review): the regression's harness is the owner lane's (hash lane, research lane D); not yet named in the map
|
||||
- R2-F06-R02 Full live-dataset census on unseen seeds and the complete v6 pack.: R2-F06 (P1, the external review): the regression's harness is the owner lane's (hash lane, research lane D); not yet named in the map
|
||||
- R2-F06-R03 A failed experimental rule does not silently exhaust generation or bypass the intended resource requirement.: R2-F06 (P1, the external review): the regression's harness is the owner lane's (hash lane, research lane D); not yet named in the map
|
||||
- R2-F07-R01 Same final v6 configuration: mine -> evict -> prove -> aggregate -> submit -> rebuild -> resume; no leaked reservations.: R2-F07 (P1, the external review): the regression's harness is the owner lane's (app lane, fleet lane); not yet named in the map
|
||||
- R2-F07-R02 OOM, process crash and stale work recover without losing wallet state or silently consuming power.: R2-F07 (P1, the external review): the regression's harness is the owner lane's (app lane, fleet lane); not yet named in the map
|
||||
- R2-F07-R03 16 GB+ simultaneous mode only after measured peak plus next-epoch headroom; smaller-card modes labelled separately.: R2-F07 (P1, the external review): the regression's harness is the owner lane's (app lane, fleet lane); not yet named in the map
|
||||
- R2-F08-R01 Report every eligible job outcome, including expired work; a bounded list cannot hide losses.: R2-F08 (P1, the external review): the regression's harness is the owner lane's (proving lane, fleet lane, site (ops page)); not yet named in the map
|
||||
- R2-F08-R02 Consumer tiers complete and receive payment for declared jobs before claims about income.: R2-F08 (P1, the external review): the regression's harness is the owner lane's (proving lane, fleet lane, site (ops page)); not yet named in the map
|
||||
- R2-F08-R03 Sustained real workload across class transitions, with restart/retry and no publisher intervention.: R2-F08 (P1, the external review): the regression's harness is the owner lane's (proving lane, fleet lane, site (ops page)); not yet named in the map
|
||||
- R2-F09-R01 Generate all pass/fail cells directly from the declared inequalities and inputs.: R2-F09 (P1, the external review): the regression's harness is the owner lane's (research lane, floor lane 3, coordinator); not yet named in the map
|
||||
- R2-F09-R02 Independent feasibility and cost evaluation of the strongest modeled SRAM/hybrid opponent.: R2-F09 (P1, the external review): the regression's harness is the owner lane's (research lane, floor lane 3, coordinator); not yet named in the map
|
||||
- R2-F09-R03 GPU owners and entrants remain viable under the approved scenario envelope without assuming chip absence or death.: R2-F09 (P1, the external review): the regression's harness is the owner lane's (research lane, floor lane 3, coordinator); not yet named in the map
|
||||
- R2-F10-R01 Compare exact found nonce/hash sets with full-read mode, including all-hit overflow and zero-hit cases.: R2-F10 (P2, the external review): the regression's harness is the owner lane's (worker lane (new)); not yet named in the map
|
||||
- R2-F10-R02 Test stale jobs, high-32 rollover, tail batches and asynchronous buffer reuse.: R2-F10 (P2, the external review): the regression's harness is the owner lane's (worker lane (new)); not yet named in the map
|
||||
- R2-F10-R03 Compare production throughput and wall energy, not only the isolated kernel timer.: R2-F10 (P2, the external review): the regression's harness is the owner lane's (worker lane (new)); not yet named in the map
|
||||
- R2-F11-R01 Goal switch from an efficiency prior can explore higher core/power when policy allows.: R2-F11 (P2, the external review): the regression's harness is the owner lane's (Ember lane (new)); not yet named in the map
|
||||
- R2-F11-R02 Driver, workload, dataset, compiler and device changes invalidate certification while retaining optional hints.: R2-F11 (P2, the external review): the regression's harness is the owner lane's (Ember lane (new)); not yet named in the map
|
||||
- R2-F11-R03 Thermal/error/late-share events revert safely, including process or machine crash.: R2-F11 (P2, the external review): the regression's harness is the owner lane's (Ember lane (new)); not yet named in the map
|
||||
- R2-F12-R01 Crash before/after broadcast, response timeout, restart before snapshot: no duplicate payment or silent debt loss.: R2-F12 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- R2-F12-R02 Same signed transaction retried, fee replacement reconciled by intent, not a new payment.: R2-F12 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- R2-F12-R03 Receipt reorg and finality pause leave correct pending obligations.: R2-F12 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- R2-F13-R01 Repeated authorization rejected or atomically replaces and cleans prior state.: R2-F13 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- R2-F13-R02 Oversized unterminated frame rejected within fixed memory/time budget.: R2-F13 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- R2-F13-R03 Slow clients and invalid share floods cannot grow unbounded member, nonce or outgoing state.: R2-F13 (P1, the external review): the regression's harness is the owner lane's (pool lane (new)); not yet named in the map
|
||||
- R2-F14-R01 Public build has no default arbitrary remote execution and a documented least-privilege boundary.: R2-F14 (P1, the external review): the regression's harness is the owner lane's (app lane, relay lane); not yet named in the map
|
||||
- R2-F14-R02 Automatic updates off remains off for urgent manifests until explicit action.: R2-F14 (P1, the external review): the regression's harness is the owner lane's (app lane, relay lane); not yet named in the map
|
||||
- R2-F14-R03 A compromised fleet/update signing key cannot silently acquire wallet access or activate a consensus change.: R2-F14 (P1, the external review): the regression's harness is the owner lane's (app lane, relay lane); not yet named in the map
|
||||
|
||||
## Count
|
||||
|
||||
153 automated cases: 56 mapped to a cell, 102 NOT RUN with a reason.
|
||||
171 automated cases: 57 mapped to a cell, 164 NOT RUN with a reason.
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load diff
Loading…
Reference in a new issue