Merge igneum-2.0-plan-docs-2 4990e9f9 into master (gate: green on 4990e9f9, recorded by tools/ci/pre-push.sh; landed on the box mirror under the exception declared by main: main's ruling, 7 Oct 2026 19:5x UK: the GitHub account is suspended, lanes land on the box mirror's master, the box gate stamp is the verdict; GitHub gets the fast-forward when it answers)

docs/plans/igneum-2.0.md

@@ -245,3 +245,25 @@ The PDF is the complete reference and supersedes the .rtf where they differ; bot
 - [ ] Mainnet needs: complete proof enforcement, a resolved finality and recovery model, operator-control tests, the compatible-application test suite, a funded maintenance plan (engineering, audits, infrastructure, incident response), committed funding distinguished from adoption-dependent income; fair launch is a principle, not a funding strategy.
 - [ ] Acceptance scorecard served as a checklist with its "do not substitute" column (plan p. 25), never as a completion dashboard.
 - [ ] Brand kit stands: Unbounded, IBM Plex Sans, IBM Plex Mono; obsidian, ember, graphite, bone, molten.
+
+## The finish line (8 October 2026, 18:0x BST)
+
+Finished means: D1 to D5 pass their conditions, the launch requirements are live, and the claim ladder is earned rung by rung.
+
+- Tonight (by 23:30): D1 object frozen with the five digests and the spec re-cut; v2.0.0 on every platform, both PCs mining with no click, the card posted; the site reset complete (labels, ladder, scorecard, fresh ledger); D4 landed with the die verdict, the workbook, the proving-payment design and the dataset-schedule sentence; D2 and D3 placed rows; the D5 partition row; the pool vote-key design; the guest re-pin.
+- Tomorrow: class v6 live on the devnet; node 2.0.1 and miner v2.0.1 as one paired cut (manifest, four words, explicit update acceptance, time-share and claim rules, finality v4 behind its switch, the new shard program id); the "layer 8 off" D2 experiment under the one acceptance rule; the dataset floor decision (5.5 GiB is +14 percent at the lock on the 5090, over budget); the pool implementation (vote keys committed in the work, non-custodial payouts, the home-connection penalty measured); the 32-lane placed core and the rest of the adversary matrix.
+- Days two and three: the D5 no-rescue exercise on the three idle seeds plus a fleet subset with founder infrastructure removed and an in-house second client; operator experience (three income streams net of tariff, failure visibility, proving isolated from keys); the signed Mac build when the Apple enrolment is active; paid-pilot outreach from docs/plans/paid-pilot.md.
+- Not ours to force: "independently reproduced" needs an unaffiliated operator (we serve the kit and the prize); "repeat paid jobs" needs a customer who pays twice; "miners stay through hard conditions" is measured over months. These separate shipping 2.0 (this week) from earning the top-tier claim (the evidence).
+- Founder decisions: the finality switch (recovery, default at 20:00, or pause only); the dataset floor after the 21:00 sentence; the first pilot customer class; the Apple enrolment route.
+
+### Pins the finish line missed (checked against the 37 pages, 18:1x BST)
+- [ ] Served reference GPU population and the cost-per-accepted-unit table, existing owner and new entrant per class (p. 8). Owner: research lane with the site lane.
+- [ ] The formal memory model: the evaluation mapped into capacity, bandwidth, energy and amortisation terms, what is bounded and what rests on physical design (p. 10). Owner: adversary lane.
+- [ ] Cryptographic review of the template, nonce, work and result binding: no expensive intermediate reused across cheap winning attempts (p. 10). Owner: the attack seat, with the hash lane.
+- [ ] The disclosure prize live with terms rewarding a better adversary or a reproduced shortcut (p. 12). Owner: site lane, terms from the coordinator.
+- [ ] Home-connection against datacentre accepted-work penalty, measured on the 2.0 devnet (p. 14). Owner: fleet lane with a home box (PC 1 or PC 2).
+- [ ] Published optimisation work, compiler settings and safe tuning logic (p. 14). Owner: hash lane, served by the site lane.
+- [ ] Negative test six, proof side: derivation inside the aggregator guest (P22 stage 3) (p. 16). Owner: enforced-proving lane.
+- [ ] The proving benchmark served with typical and tail latency per stage (p. 17). Owner: fleet lane's record, served by the site lane.
+- [ ] Reproducible builds with a served recipe, and a signing-key incident procedure (p. 21). Owner: shipper with the build-server lane.
+- [ ] The funded maintenance plan and the committed-funding line (p. 24). Owner: the founder.