The page shows each of the 128 cases in 16 suites as it is run, in the standard's words (NOT RUN, RUNNING, PASS, FAIL,
BLOCKED, DEFERRED): a header with the approval line and a thin segmented count bar (never a percentage), G0 and the five
gates G1 to G5 plus the three named gates as cards whose state follows the standard's rule, one section per suite with an
expandable row per case (setup, steps, accept, required evidence, the run's evidence record when present), the profiles
(approved as proposed, P13 deferred, the P04 line read as a FAIL to work against), the fixtures, and the closing notes.
site/lib/acceptance-render.mjs is the one renderer: build.mjs imports it for the build-time page and prints the same functions
into the page's inline script, which polls /api/acceptance (site/api/acceptance.mjs: the registry from git.igneum.network
master, cached 60 s, ok:false with status 200 on failure) and re-renders in place when a case state or source_sha256 moves.
Hooks: the Learn panel, the nav check, the sitemap, capture.sh, the og card row, a lead link on /scorecard, the facts rows 1
to 7 name the case that will prove each. The never-served check strips the plan's own marked never-served list. Node tests
(known-failed first) run in the gate; the registry and the standard text land with the page.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The markdown loop in site/build.mjs takes paths under docs/ (build/build.md, build/grants.md, build/compatibility.md, site/audit-2.0.md); /audit joins the Learn panel (both lists), the nav-check groups, the sitemap, the capture routes and the og cards.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
docs/spec/finality-guarantees.md section 9: one vocabulary, included, executed, proven, finalised; the network's pause
is the network's word, never a transaction's. The wallet's History row read the node's "finality not active" word for a
transaction under a locked checkpoint while finality was paused; it reads "finalised" now, with the pause in the why
("under a locked checkpoint, not yet verified here; finality is paused on the network above it"). Known-failed first on
build-2 (view.test.mjs: the row's word and the vocabulary set); 21 wallet UI tests green.
docs/design/app-audit-2026-10-08.md gains section 7: the founder's reversals and additions for v2.0.1 (the Cards tab
back, the first-block card once per address, the four words, one positioning line, the watchdog's waiting words), each
with where it lands (branch cards-201 on release-2.0.1; this branch for the wallet).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The three files as they stand in the Mac checkout at 18:23 BST, on the coordinator's word, one documents-only commit:
igneum-2.0-test-standard.pdf (392 KB), igneum-2.0-test-standard.txt (its text), igneum-2.0-test-registry.json (205 KB; data, not
code: the registry the suites are read from, parses). No chain path.
The object names a prior pair, a next pair, an activation height and a window; below the height only the prior pair verifies and pays, in the window either, after it only the next; the node embeds both pairs (elf/ and elf/prior/), the body rule, the payment rule and the native segment statement read one floor, the daemon refuses to start without every pair the object accepts at the tip, the manifests carry both pairs and the height; never on every object, in the digest once set. Tests known-failed first (the seven refusals on both sides of the height) and the fast-time case across it; the node branch by 18:00 UK on 9 October 2026.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Documents-only replay of 25098c1a2 (25098c1a276d80987262eda59a7f1beef8cd6ba4) for the box mirror master
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Landed from ca3-coord-record c1aa45bde on the founder's order through the research-landing hand: igneum-2.0-register.md whole. docs/plans/igneum-2.0.md stays master's copy under rule 26: the branch's plan-file change was the finish-line sections already on master from the checkout and the removal of the finality lane's D5 block, which stays.
Rule 26: the same file master holds, merged not replaced: a three-way merge of the checkout's file over master's copy with the
846fab00 landing as the base; the finality lane's D5 partition-row block (e9f32fb9) stays, the two new sections are added, 22 lines,
no deletions. Documents only.
