Patterns
Patterns are not repositories.
A pattern is a way of arranging trust. The component, if there is one, comes after, and only with a licence tier.
- Conventional system of recordA database, an API, identity, and a signed audit log operated by one organisation.
- Anchored registryThe register lives off chain. A hash of a defined snapshot is committed where others can see it.
- Controlled transferAn asset representation that can move only when identity, pause, or an allow-list says so.
- Wallet policyKeys that can move value only inside a limit, a quorum, and a recorded approval.
- Verifiable credentialA signed claim a subject can present later, without putting the evidence file on a public chain.
- Off-chain evidence vaultDocuments encrypted at rest, access logged, and at most a commitment published.
- Payment orchestrationApproval, quote, movement, and reconciliation as separate steps. The chain, if any, is one rail.
- Conditional paymentFunds move only if a condition is met. The condition is escrow, a hash lock, or a credential, not a slogan.
- Oracle and attestationA signed statement about the world, brought to a system that cannot see the world.
- Indexer read modelChain events copied into a database your product can query. The chain remains the source for those events.
- Agent spend limitSoftware may propose a payment. A policy, a limit, and a person decide whether it goes.
- Device provenanceA device or a batch signs events. The register records those events. Demand is a separate fact.
- Permissioned shared workflowKnown organisations share a defined state. Membership is the security assumption.
- Staking operations read modelA view of validators, duties, and penalties. Not a yield product.