α0
Genesis
INSIGHT
Stochastic successor compiler
—fresh score
Safe precision—
Unsafe accept—
Forge efficiency—
Child uplift—
root pending
CompilerSTOCHASTIC‑V1
Fresh‑task gain—Generation α0 → α2
Successor‑forge efficiency—Against validator oracle
Exact independent replays0 / 3Isolated browser workers
Chronicle decisionPENDINGProof gates not yet executed
I · The lineage
The proof‑gated chain
Each generation inherits only the prior generation’s admitted policy and compiler. Every successor receives the same proposal budget, task count, tool surface, validator rubric, and replay burden.
I
α1
Promoted
NOVA‑SEED
Failure‑guided successor compiler
—fresh score
Safe precision—
Unsafe accept—
Forge efficiency—
Child uplift—
root pending
CompilerFAILURE‑GUIDED‑V2
α2
Sovereign
SOVEREIGN
Transfer‑aware successor compiler
—fresh score
Safe precision—
Unsafe accept—
Forge efficiency—
Shadow child uplift—
root pending
CompilerTRANSFER‑AWARE‑V3
II · The two required proofs
Transfer + successor generation
The fresh suite is committed before evaluation and never shown to the successor forge. Successor‑generation quality is measured on a separate held‑out suite against a validator‑only oracle.
II
Fresh‑task transfer
Sealed after policy commitSuccessor‑forge ability
12 proposals each · equal budgetIII · Independent replay chamber
Three isolated executions. One root.
ORION, ATLAS, and SENTINEL each rebuild the task suites, forge the lineage, recompute every metric, and derive the chain root from scratch inside separate browser workers.
III
IV · Equal‑constraint constitution
No advantage by spending more
The only thing permitted to improve is the inherited policy and successor compiler. Compute, proposal count, task count, tools, validation, safety rules, and replay burden remain fixed.
IV
| Constraint | α0 | α1 | α2 | Gate |
|---|
V · Evidence Docket
Inspect the proof, not the spectacle
Every public claim below is generated from the run artifact: mission contract, task commitments, generation roots, transfer results, forge results, replay attestations, cost ledger, safety ledger, and claim boundary.
V
Run manifest
Canonical identity, deterministic seed, engine version, proof level, and root commitments.
Generation lineage
Policy evolution, fresh transfer, safety precision, and parent‑root continuity.
Fresh‑task manifest
Held‑out adjacent tasks generated only from committed seeds after all three policies are frozen.
Successor forge
Equal proposal budgets, held‑out child evaluation, and validator‑oracle efficiency.
Replay attestations
Each isolated worker recomputes the complete chain and signs its result with a node‑specific attestation digest.
Cost & safety ledgers
All generations receive identical compute accounting and must preserve the hard local‑mode safety boundary.
Canonical JSON preview
The downloadable Evidence Docket contains the complete artifact. This preview is intentionally compact.
Run the chain to generate the canonical artifact.
Claim boundary
What this demonstrator proves locally—and what it explicitly does not prove.
Local deterministic demonstration only.
VI · Export the proof
Replay it somewhere else
Download the canonical Evidence Docket, a compact replay kit, a human‑readable CSV summary, or a print‑ready proof brief. All exports are created locally in your browser.
VI
Evidence Docket
Complete run artifact with roots, metrics, tasks, ledgers, and attestations.
Replay Kit
Seed, engine version, fixed constraints, expected roots, and verification instructions.
Summary Matrix
Generation, transfer, safety, forge ability, and root continuity in CSV format.
Proof Brief
A clean print layout suitable for Save as PDF from your browser.