Cardano Modular Restaking

Evidence-gated delivery, not document-driven completion.

The source-stable model evidence records 103 passing tests across 19 files, 1,085,673 assertions, seven accepted vault/operator actions, and a finite depth-five explorer with 11,550 attempted edges across 2,894 unique state/slot nodes. Selected-source inventories bind the allocation, reward, governance, and complete 283-file middleware archives. The middleware graph recursively closes at 310 Solidity files and 1,402 edges with zero unresolved. Hash-pinned Forge/Solidity compilation succeeds; a fixed-seed non-fork EVM run records 839 pass and six skip. A deterministic replay classifies the earlier allowlist proxy-admin collision as an upstream fuzz-domain/assertion mismatch with no authorization bypass. Of 43 direct project-core counterparts, 20 are compatible only at the reviewed source level, including the bounded 31-importer IStrategy consumer surface; StrategyManager hooks, DelegationManager queued-slash rounding, and IAllocationManager per-set slasher authority are reviewed source-incompatible; and 20 remain manually queued. The storage relocation, direct-interface-consumer, hook, exact-integer rounding, and slasher-authority findings are not whole-core cross-version executions, EVM storage-layout proofs, bytecode-equivalence results, Cardano translations, or approved divergences; compatibility remains open and zero middleware behavior is accepted for Cardano. A separate exact-bigint allocation oracle remains model-only. Complete pre-validator plans keep 60 unresolved or prohibited seams absent and fail closed. The pinned Catalyst stack and project guards/codecs provide 106 non-protocol UPLC evaluations; F-001 remains open. The decision-consumer map isolates D-002/D-003/D-027, and the source-bound 42-vector evaluator-only Plutarch vault arithmetic/timing report passes all 42 cases and all 15 failure classes. This raises protocol-transition UPLC evaluation to 42, while validator-context evaluation remains zero. The new D-019 boundary has 21 passing direct tests: four exact abstract skeletons prepare deterministically and then stop at build, while 16 malformed families reject with four stable codes. It emits no datum, redeemer, CBOR, budget, signature, transaction ID, emulator result, or submission, so protocol construction remains zero. 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 last reconciled strict release report remains NOT_RELEASED with one pass and twelve failures.

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 current self-contained evidence checkpoint is f5c957b550b7c676844d62bc80a299e437031ce4, bound to source checkpoint 293f0764394fef77bd651d6b766a801d87f47ad4. The direct-core triage is 20 source-compatible, three reviewed source-incompatible, and 20 manually queued paths. The D-019 boundary is source-bound and clean-reproduced: four exact abstract preparations stop before build, 16 malformed families reject, and every stronger protocol count remains zero. D-019 still blocks public validators/policies, protocol construction, validator-context UPLC, Blaze lifecycle execution, and testnet evidence. Release status remains NOT_RELEASED.

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.