diff --git a/site/litepaper.html b/site/litepaper.html index 2e0720097..15c8bbc8e 100644 --- a/site/litepaper.html +++ b/site/litepaper.html @@ -765,6 +765,16 @@ body.all .pager{display:none}
Dates slip. Gates do not. Phase two decides everything. If consumer GPUs cannot prove shards fast enough, Igneum says so and does not launch on promises.
+| Deliverable | Owner | Pass condition | Today | Evidence |
|---|---|---|---|---|
| D1. A frozen, reproducible baseline | the coordinator with the hash and node lanes | an independent operator reproduces the baseline within declared tolerances from the served kit alone | PENDING: the kit is pinned by digest (the release manifest); the reference GPU population, the two tests per class and the cost per accepted unit of work are owed | igneum-2.0.md |
| D2. Two architectural experiments | the class v6 invention lane (a), the multi-family adversary lane (b) | the candidate improves against re-optimised adversaries within the preset cost and verification limits, or v6 stands and the experiment is published as a failure | (a) TEAM-REPORTED, killed as a class: only the window width reaches the chip; (b) open | connected-state.md |
| D3. A programmable adversary allowed to survive | the multi-family adversary lane with the k lane | the best supported cost and energy advantage sits inside the chosen competitiveness envelope, with uncertainty published | MODELLED: the placed and routed core energies served above; the dataset schedule and the state coupling are under evaluation | class-v6-rotating-family.md |
| D4. A five-year coexistence model | the research lane with the k lane’s rows | the model names credible conditions for sustained commodity participation and names where it fails | MODELLED, first run served: the DRAM board passes six of seven conditions; the die fails on its machine cost; the thresholds live in the sensitivity workbook | coexistence-model.md |
| D5. A no-rescue network exercise | the node lane with the build-server lane | specified behaviour with no emergency algorithm change and no privileged intervention | PENDING: the prerequisite (proof verification enforced in consensus) is on from block zero on the Igneum 2.0 devnet; the exercise itself is owed | finality-guarantees.md |
The pins and their pass conditions are docs/plans/igneum-2.0.md; the Today column carries the served labels (TEAM-REPORTED, MODELLED, PROPOSED, PENDING, EXCLUDED) and moves only with a landed document. The acceptance scorecard is the checklist across the twelve gates.