The IXO Graph is the connected model of the records IXO's services share: domains, the claims made about them, the evidence behind those claims, the decisions on them, and the credentials, grants and payments that follow. Each record links to the others, and each change is recorded, so you can follow a piece of work from the domain it concerns to the decision and what that decision set in motion.
Read this page when you are deciding how to model your own system on IXO. It explains what the graph links together and which record answers which question.
What the graph links
| Record | What it is | Linked to |
|---|---|---|
| Domain | The full presence of something on IXO: an organisation, a project, an asset, an oracle, a protocol. See Core concepts | Other domains, through linked entities |
| Claim | A signed statement about a domain | The domain, the protocol that defines its type, and its evidence |
| Evidence | Files and answers attached to a claim | The claim, by a hash of their content |
| Decision | What the IXO decision engine concluded from the facts under a rubric | The claim, the rubric, and the engine's signed receipt |
| Credential | A signed statement that its holder can show | The issuer, the holder, and the decision it rests on |
| Grant or delegation | Permission for a named party to do a named thing | The party, the action and the resource |
| Payment | Money that moved because of a decision | The decision and the accounts involved |
Links between domains place each domain in a graph of relationships. A programme links to its projects, a project to its devices, a device to the oracle that checks its readings.
Which record answers which question
| Question | Record |
|---|---|
| What is the work about? | Domain |
| Who is acting? | An identity: a person, an organisation, a service or an agent |
| What is being asserted? | Claim |
| What supports it? | Evidence |
| Who may act? | Grant, delegation (UCAN), credential or role |
| What steps is the work following? | Qi Flow |
| What was decided? | Decision (some pages call the signed record a UDID) |
| What changed? | A transaction or state change on chain |
| What value moved? | Payment |
Keep these records separate. A claim is an assertion. A decision is a separate record. A payment is another. None of them proves the one before it: What each record proves explains why.
Example: paying for a field visit
A service provider collects field data for a digital MRV programme.
The provider and the project are domains
The provider and the project each have a domain, linked to each other.
The provider makes a claim
The provider submits a claim that field visits were completed for the project in a given reporting period. Reports, timestamps, locations and photos are attached as evidence.
The claim is decided
A decision oracle produces the facts the rubric asks for. The IXO decision engine applies the rubric and signs the decision. If the rubric sends the claim to a person, the reviewer's answers become part of the same decision.
The decision sets something in motion
If the claim is approved, payment terms on the collection can pay the provider, and the decision can support a credential.
Each step adds a record linked to the ones before it: provider, project, claim, evidence, facts, decision and payment.
How the graph is used
- IXO Protocol records the on-chain part: domains, claims, decisions, grants and payments. See IXO Protocol.
- IXO Blocksync indexes what the chain has recorded so applications can query it. See IXO Blocksync.
- IXO Matrix holds the off-chain part: encrypted rooms, messages, files and shared documents attached to a domain. See IXO Matrix.
- Qi reads the graph to give people and agents the same context: which domains a Flow involves, what has been claimed and decided, and who may act. See Qi.
Agent memory and chat history are not records in the graph. An agent should cite records by identifier, not rely on what it remembers.
Start small
Model only what several parties need to check or act on. Start with one domain type, one claim type and one Flow:
- Choose the domain: a service provider, a project, a device, a household or a dataset.
- Define the claim about it: its type, who may make it, the required fields and the evidence.
- Decide who may submit, review, decide, dispute and pay, and give agents only scoped delegations.
- Write the rubric the claim is decided by.
- Run real cases, then read back the records to find missing evidence, unclear authority or slow review.