Chain-facing capabilities have not been reviewed.
Next: Review production entry points and integration behavior.
Marlowe Language CIC · cabal / container / nix
Dijkstra readiness: gap (see below). Dependency evidence does not establish compatibility.
Breaks after HF
Exposure dependency · inherited readiness gap · scanned at 826b5fc5cf
Own era handling: own-work. The CLI offers only the Conway era and maps Plutus script versions per era up to PlutusV3 in Conway; Dijkstra and PlutusV4 need new cases. A dependency solve (2026-10-22, scripts/readiness/bump-solve) resolves cardano-api 11.8.0.0 on GHC 9.6.7 only with four companion pins raised across majors: cardano-crypto-class to ^>=2.6, plutus-core and plutus-ledger-api to ^>=1.71, and validation to ^>=1.2; nothing was compiled.
(SomeEra BabbageEraOnwardsConway) C.BabbageEraOnwardsConway -> Just C.PlutusScriptV3InConwayconfirmed· cardano-apicardano-api-haskellera-identitytransaction-encoding
The indexer follows the node through cardano-api ^>=11.0, which has no target Dijkstra era.
C.connectToLocalNode localNodeConnectInfo $not-reached· cardano-serialization-lib-cslplutus-languageblock-encodingprotocol-parametersstake-pool-registrationtransaction-encoding
Declared by the integration app, whose sources do not import it.
"@emurgo/cardano-serialization-lib-nodejs": "^17.0.0",not-reached· kupoblock-encodingera-identitytransaction-encoding
Marlowe vendors Kupo's transaction-traversal code as a module named Kupo; it calls no Kupo service.
tx' = Kupo.txFromCardanoTx txnot-reached· plutus-plutus-coreplutus-languageplutus-script-context
Validators use the V1-V3 ledger API; PlutusV4 is additive.
import PlutusLedgerApi.V3.Contexts (findDatum, findDatumHash, txSignedBy, valueSpent)partial
unresolved
unresolved
unresolved
No native profile has been collected. Dependency coverage is unresolved, not empty.
Findings describe behavior in a specific release and configuration. Suggestions need verification; historical findings do not establish behavior in the current source. None establishes hardfork compatibility.
No capability findings have been returned. Behavior remains unresolved; an empty list does not mean this tool has no chain-facing capabilities.
Next: Review production entry points and integration behavior.
Next: Export a discovery review packet.
Next: Collect a native resolution for a declared release/profile.
Next: Confirm distribution artifacts and production configuration with release evidence.
evidence:3fa887101f8074e6bad4073798eb02a39dac6390ac2e35a4a2f47bbffe41d235Retained at data/readiness/evidence/3fa887101f8074e6bad4073798eb02a39dac6390ac2e35a4a2f47bbffe41d235.json.gzevidence:e327d140073e4b8f246f5842fb8949fb46638dcaa6e438a71747ae017c20c984Retained at data/readiness/evidence/e327d140073e4b8f246f5842fb8949fb46638dcaa6e438a71747ae017c20c984.json.gz