ZAYAZ turns evidence into claims, and claims into consequences — between parties who don't fully trust each other.
Three layers, one graph. The clearinghouse story explains why. The object kernel defines what. The claim life cycle — your seven questions — describes how. Sales, architecture, and onboarding each enter at their own layer; all three are views of the same structure.
Obligations create demand for verified claims. Evidence creates supply. ZAYAZ is the exchange in the middle — and a clearinghouse's value is its participants, which is why the network is the asset and cascade invitations are free.
Regulators, clients, and stakeholders demand verified claims. CSRD, CSDDD, VSME, contracts, procurement requirements — each one is a standing order for trusted information.
Matches supply to demand. Resolves identity, attaches trust, settles delivery — every claim cleared against evidence, every party known.
Suppliers, sensors, systems, and attestors supply the raw material of proof — documents, meter readings, ERP records, third-party verifications flowing in through the Input Hub.
The irreducible things ZAYAZ governs. Every module has exactly one home object — the discipline test for any future engine is "which object does this govern?" Select a node to see its definition, invariant, and module mapping.
Your seven questions, recast as operations traversing the object graph. The pipeline is a view over the kernel — the user's journey through it — so the two models can never contradict each other.
| Nº | Capability · Question | Operation on the graph | Objects touched |
|---|---|---|---|
| 1 | Define What is required? | Instantiate obligations. Regulations, contracts, and stakeholder demands are registered as Obligation objects binding specific Entities — each one names an obligor, an obligee, and a due form. | OBLIGATIONENTITY |
| 2 | Collect What can we obtain? | Ingest raw evidence. Automated, semi-automated, and manual sources deposit immutable Evidence records via the Input Hub. | EVIDENCE |
| 3 | Observe What do we know? | Resolve identity. Evidence is bound to canonical Entities (CMID, E-C-O) and canonical signals (CSI, USO) — raw data becomes governed observation. | EVIDENCEENTITY |
| 4 | Assure Can it be trusted? | Attach trust to claims. Validation, attestation, and replay establish the evidence lineage of every Claim. Trust attaches to the claim — never vaguely to "data." | CLAIMEVIDENCE |
| 5 | Understand What does it mean? | Contextualize claims. Analytics, forecasting, and intelligence read the claim graph to produce insight and decision support. | CLAIM |
| 6 | Act What should we do? | Trigger decisions. Claims and insight fire workflows, recommendations, and corrective actions — every Decision traceable to the claim that triggered it. | DECISIONCLAIM |
| 7 | Exchange Who needs to know? | Deliver across relationships. Trusted claims travel to people, systems, regulators, and federated ecosystems — always over consented edges, never around them. | RELATIONSHIPCLAIM |
| ↺ | THE LOOP CLOSES: Decisions alter Relationships and create new Obligations — Exchange and Act feed back into Define. The pipeline is a cycle, not a line. | ||
Cross-cutting services that serve every object and every life-cycle stage. In Figma, this is the horizontal band beneath the graph — never forced into a column.
Tokens, component anatomy, edge taxonomy, and page plan — everything needed to rebuild this as the canonical Figma master.
surface/node fill, 1px hairline stroke, 3px top tick in object color. Variants: default / hover / selected.surface/raised plate, midpoint of edge.