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 56 passing tests, 1,078,480 assertions, direct register/delegate/delegated-deposit/queue coverage, a 15-vector pinned EigenLayer v1.12.0 arithmetic differential, a finite depth-five vault explorer with 1,299 attempted edges and 672 unique state/slot nodes, and an operator-aware 10,000-attempt campaign with 8,506 accepted transitions and 1,494 expected rejections. The campaign includes 90 accepted registrations, 486 accepted delegations, 109 repeat-delegation rejections, and 920 transaction-fact mutations. A strict offline audit confirms the canonical manifests, current source hashes, run options, logs, and counters. A fresh same-host checkout of source milestone bef9f45 reproduced all five deterministic model/formal projections. 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.