Products
A product is a step above a recipe. Where a recipe selects capabilities, a product assembles a state machine or composite profile, a domain contract, a read API, a client, and often a CLI into one installable thing with an opinion about a use case.
| Product | What it does | Maturity |
|---|---|---|
| Evidence | Publish an immutable document through a threshold-approved workflow, preserve it in object storage and IPFS, notify Kafka, and prove the whole chain. | preview |
| Cardano History | Query and prove historical Cardano protocol parameters, epoch stake, DRep distribution, and proposal history. | preview |
| eUTxO and ZK | A deterministic Cardano-shaped UTxO ledger, an optional Cardano bridge, and an optional ZK validity/rollup path. | experimental |
What products have in common
Section titled “What products have in common”Each one:
- ships as one or more runtime plugin bundles in the Yano X distribution or
under
optional-plugins/; - selects a state machine or composite profile whose identity is part of chain identity;
- publishes a no-SPI contracts library so off-chain code can build and decode the same canonical bytes the chain uses;
- contributes bounded, read-only domain routes under
/api/v1/plugins/<bundle-id>/; and - defines proof subjects so its facts are provable in application language rather than trie keys.
That last point matters most. A product’s value is not that it stores data — it is that it makes a specific claim provable to someone who does not trust the node that served it.
Choosing one
Section titled “Choosing one”Products are not mutually exclusive with recipes; a product is the recipe for its domain. Start from choosing a recipe and let the outcome table point you here.
Reach for a product when your problem is recognizably the one it models. Reach for the plugin framework when it is not, and check first whether a composite of existing components gets you there.
What products deliberately do not claim
Section titled “What products deliberately do not claim”The reusable platform proves what identified participants finalized and what publication instruction they authorized. It does not decide what counts as a valid product event, an acceptable inspection, or a correct settlement — that stays with the domain.
Evidence, in particular, proves that specific members approved specific bytes at a specific point in a verifiable order, and that a connector reported storing those bytes. It does not prove the document’s content is true.