Chain-facing capabilities have not been reviewed.
Next: Review production entry points and integration behavior.
dcSpark · cargo / npm
Dijkstra readiness: gap (see below). Dependency evidence does not establish compatibility.
Breaks after HF
Exposure implements · inherited readiness gap · boundary component, R2 status gap · scanned at 69b8664c84
Step 19 of the fix order: once the earlier steps land, it unlocks 2 more tools: cardano-ibc-incubator, nami.
If only this were fixed
No tool on its own: every tool that needs it also waits on something else.
Also needed by cardano-ibc-incubator (still waits on gouroboros, kupo, ogmios, blockfrost), carp (still waits on carp (own gap), oura), lucid-evolution (still waits on lucid-evolution (own gap), scalus, kupo, ogmios, blockfrost, koios), nami (still waits on cardano-js-sdk, blockfrost, ledgerjs-hw-app-cardano, cardano-hw-interop-lib)
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:c783e4179ad6f6914f55b9e4a683ede3c9d774f517b426f7b18038608388579fRetained at data/readiness/evidence/c783e4179ad6f6914f55b9e4a683ede3c9d774f517b426f7b18038608388579f.json.gzevidence:d5dd9bcf5eefc79c54b66e184ce6952a7cc3bc283e999ec27aa0444fd15dcb3aRetained at data/readiness/evidence/d5dd9bcf5eefc79c54b66e184ce6952a7cc3bc283e999ec27aa0444fd15dcb3a.json.gz