MVP lifecycle
Release target: every success and rejection must replay through model → UPLC → emulatorEvidence-gated delivery, not document-driven completion.
The source-stable model evidence records 57 passing tests, 1,078,499 assertions, direct register/delegate/delegated-deposit/queue coverage, a 15-vector pinned EigenLayer v1.12.0 arithmetic differential, and a finite depth-five one-owner/two-operator explorer with 11,550 attempted edges across 2,894 unique state/slot nodes. Its 8,174 expected rejections include 3,375 action-specific single-fault transaction-fact mutations paired with every planned-success non-create edge; each rejects exactly without state interference and the report explicitly declares that these rejected fact edges never create nodes. The accepted graph still covers 764 registrations, 288 delegations, delegation to either operator, delegated deposit, partial/full queue, and attributed completion paths. The option boundary also rejects explicit null instead of silently defaulting. The operator-aware 10,000-attempt campaign adds 8,506 accepted transitions, 1,494 expected rejections, and 920 transaction-fact mutations. A strict offline audit confirms the canonical manifests, current source hashes, run options, logs, fact/scenario partitions, and counters. A fresh same-host checkout of exact source milestone 5cfa81b reproduced all five deterministic model/formal projections in 227,136 ms. The source-bound release report passes only the bounded abstract formal-build gate and records 12 failures with NOT_RELEASED; independent reproduction, validator implementation, UPLC evaluation, Blaze emulation, implementation refinement, and public-testnet execution remain open.
| Phase | State | Exit evidence | Primary source |
|---|
Progress discipline
- Resolve value-bearing choices in
docs/DECISION_LOG.mdbefore implementing their paths. - Keep every incomplete validator and policy fail-closed.
- Advance status only with source-bound, reproducible evidence using the repository vocabulary.
- Update this explorer in the same change as architecture, transition, phase, or evidence changes.
Claims stop exactly where the evidence stops.
The project uses a deliberately strict vocabulary so pure models, transaction construction, evaluator execution, emulator acceptance, public-ledger inclusion, formal proofs, and release decisions cannot be conflated.
Release tiers
- Pre-production alpha: generated UPLC and Blaze emulator evidence, explicitly not public-chain execution.
- Testnet-executed alpha: named public-testnet transactions, reconstructed state, and exercised operational recovery.
- Production: additional soak, independent review, deployed governance controls, monitoring, and budget headroom.