Cardano Modular Restaking

Evidence-gated delivery, not document-driven completion.

The source-stable model evidence records 105 passing tests across 20 files, 1,085,690 assertions, seven accepted vault/operator actions, and a finite depth-five explorer with 11,550 attempted edges across 2,894 unique state/slot nodes. A canonical one-million profile and a separately invoked, separately seeded two-million profile now pass 3,000,000 reconciled attempts through the same TypeScript planner, candidate-fact validator, and full invariant machinery; they remain modeled only. Selected-source inventories and negative readiness boundaries still keep 60 unresolved or prohibited later seams absent and fail closed. The pinned Catalyst stack and project guards/codecs provide 106 non-protocol UPLC evaluations; F-001 remains open and Forestry scope is maintenance-only until an immediate consumer exists. The source-bound vault and operator/delegation reports provide 78 evaluator-only protocol-transition relations, while validator-context evaluation remains zero. Six exact abstract vault/operator skeletons stop before build under D-017/D-019. Pinned Blaze builds/tests pass and one generic non-protocol transfer is constructed, signed, and emulated. No protocol transition has been constructed, Blaze-emulated, or testnet-executed. The strict release report remains NOT_RELEASED: PPA-08 and PPA-10 pass, while eleven gates fail.

The middleware corpus closes the reachable Solidity graph from 78 source files, 97 test files, and two scripts at 310 files and 1,402 import edges with zero unresolved, while recording 121 normalized source declarations, 618 named source functions, 116 test families, and 800 named tests. Its 921 exact review records still accept zero Cardano behavior. Hash-pinned Foundry v1.3.6 and Solidity 0.8.27 compile all 310 files; a fixed-seed non-fork EVM run records 839 passing and six skipped. A deterministic overlay reproduces the upstream assertion mismatch and confirms the transparent proxy's expected admin rejection before the call reaches Allowlist. The 43-path semantic triage resolves 20 paths as source-compatible, including the bounded 31-importer IStrategy consumer surface, classifies three paths as source-incompatible, and queues 20 for manual semantic review. The queue-slash review binds a differing result (1 versus 0) under exact WAD arithmetic. The slasher review binds both manager/interface revisions, the 58-import/50-importer fanout, legacy slasher=avs conversion, separate slasher call, and three appointee-selector bindings. The exact source-bound strategy, hook, queue-slash, and allocation/slasher sources are hash-bound but unexecuted by these reviews. These findings are not storage-layout proofs, bytecode equivalence, Cardano translation, or approved divergence. This is partial upstream EVM evidence, not Cardano compatibility or execution.

The release-scale audit binds the one-million digest model-fnv1a64:315fda939f59125c and independent two-million digest model-fnv1a64:a08f28ac462fdcd0, exact profile options, eight rejection codes, all seven accepted actions, current source hashes, and zero stronger-evidence counts. A fresh checkout of source checkpoint 7fa6db8 passes all eight same-host reproduction commands and matches all eleven semantic report projections in 375,965 ms. A manually dispatched GitHub-hosted Ubuntu workflow shares those exact projections and pins every setup/upload action by commit, but no remote report is accepted until the run, download, and strict import checks complete; even then, the bounded subset cannot close PPA-13 alone. The direct-core triage remains 20 reviewed-source-compatible, three reviewed-source-incompatible, and 20 manually queued paths. D-017/D-019 still block public validators and policies, protocol construction, validator-context UPLC, Blaze lifecycle execution, and testnet evidence. Release status remains NOT_RELEASED. Independent rebuild contract ↗

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.