Most organisations are not blocked because they lack AI tools. They are blocked because people and agents operate on conflicting information, decisions are disconnected from evidence, workflows break across organisational boundaries, automation cannot be trusted with real-world consequences, and nobody can clearly prove what happened, who acted, or whether outcomes were achieved. The IXO Stack — IXO Protocol as the verifiable state layer and the Qi Intelligent Cooperating System as the human–AI cooperation layer — addresses that class of problem. It is not chat-based AI automation; it is outcome-driven coordination infrastructure for humans, AI agents, organisations, data systems, governance processes, and financial systems operating against shared, verifiable state.Documentation Index
Fetch the complete documentation index at: https://docs.ixo.world/llms.txt
Use this file to discover all available pages before exploring further.
The two layers
IXO defines what is true and verifiable. Qi defines how intelligent actors cooperate over that state inside real workflows.IXO: the verifiable state layer
Identity, claims, evidence, credentials, governance, programmable coordination, payments, and outcomes — modelled as cryptographically verifiable state on the IXO Graph.
Qi: the intelligent cooperating system
Humans and AI agents working together over IXO-backed state through shared context, declared interfaces, governed workflows, and inspectable actions.
What IXO records
IXO maps real-world systems into cryptographically verifiable digital state. Typical state transitions include:- a carbon reduction event
- a youth skills credential
- a pathogen detection signal
- a delivery confirmation
- a governance decision
- a machine telemetry reading
- an evaluation outcome
- an AI-generated recommendation
What Qi coordinates
Qi creates persistent cooperative environments where context is shared, memory persists, authority is explicit, actions are governed, and outcomes are verifiable. It is designed around intent, shared state, flows, capabilities, and outcomes — moving teams from generating AI outputs to producing accountable outcomes. See Qi Intelligent Cooperating System.Core building blocks
These are the four building blocks every reader should recognise before going deeper.Shared state
Shared state
PODs
PODs
A POD (Programmable Organisational Domain) is a governed cooperation environment — a team, company, project, field operation, supply chain, public health response, financing facility, or research collaboration. Every POD has identity, governance, shared memory, verifiable history, programmable permissions, and financial coordination primitives. PODs are the operational trust boundary for AI-enabled organisations.Read more: IXO PODs. Hands-on: Build a POD.
Qi Flows
Qi Flows
Qi Flows coordinate work between humans and AI agents. Flows are state-driven, governance checkpoints are programmable, humans remain in the loop, and evidence and outcomes are first-class objects. A Flow can orchestrate AI services, request evaluations, trigger payments, issue credentials, update governance state, coordinate field operations, manage disputes, and route work dynamically — embedded directly into collaborative workspaces, not separate orchestration dashboards.Hands-on: Build a Flow.
Agentic Oracles
Agentic Oracles
An Agentic Oracle is not just a model endpoint. It is a governed economic actor with identity, permissions, policies, payment mechanisms, reputation, verifiable execution records, and evaluatable outcomes. Examples include document evaluation, carbon verification, epidemiology, accounting, legal review, and sensor anomaly detection agents. Every action can be authorised, audited, evaluated, disputed, and settled.Read more: Agentic Oracles and Oracle architecture. Evaluation model: Claim evaluation protocol.
Trust architecture
The trust architecture is what makes intelligent automation safe for consequential work.Identity
Identity
IXO uses Decentralized Identifiers (DIDs) to establish cryptographically verifiable identity for people, organisations, agents, devices, workflows, and governance domains. This enables portable trust, sovereign identity, verifiable delegation, and cross-platform interoperability.The system aligns with W3C Verifiable Credentials, W3C DID Core, and W3C Data Integrity. See Identity and credentials.
Capabilities and permissions
Capabilities and permissions
Qi uses object-capability security for fine-grained authorisation. Permissions are explicit, delegated, time-bound, revocable, and scoped to intent and resources, so organisations can safely authorise agents to access systems, perform actions, operate tools, and coordinate with other agents — without granting blanket control.Capability delegation patterns are informed by UCAN and ZCAP-LD. See Authentication, Session keys, and Authz.
End-to-end encryption
End-to-end encryption
Collaboration and shared state are protected with end-to-end encryption so platform operators cannot inspect private operational data, organisations retain sovereignty over their information, and AI cooperation occurs within controlled trust boundaries.Secure coordination is built on the Matrix Protocol. See IXO Matrix.
Verifiable outcomes
Verifiable outcomes
Outcomes — evidence, evaluations, approvals, causal reasoning, financial settlement, governance decisions — become part of a durable, verifiable audit graph. Organisations can then automate trust, finance verified outcomes, coordinate across institutional boundaries, evaluate AI performance, and improve decision quality over time.Read more: Claim evaluation protocol and Digital MRV.
Typical deployment layers
A production IXO + Qi deployment composes several layers, each with a canonical home in the docs.| Layer | Purpose | Canonical reference |
|---|---|---|
| IXO verifiable state | Identity, claims, governance, settlement | IXO Protocol |
| Graph substrate | Shared, queryable map of entities and relationships | IXO Graph |
| POD runtime | Organisational cooperation environments | IXO PODs |
| Qi Flow engine | Human–AI workflow coordination | Qi Intelligent Cooperating System |
| Agentic Oracles | AI services and accountable automation | Agentic Oracles |
| Matrix federation | Encrypted collaboration and shared documents | IXO Matrix |
| Indexing and query | Read-side access to protocol state | IXO Blocksync |
| Endpoints and networks | Chain IDs, RPC, REST, Matrix base URLs | Networks and endpoints |
| External integrations | ERP, CRM, sensors, APIs, AI models | Integrations |
Why this matters
AI systems can increasingly reason, plan, operate tools, execute workflows, and coordinate actions. But intelligence without trust creates systemic risk. The next layer of infrastructure must answer:- Who authorised this action?
- What evidence supports this decision?
- Which agent performed the work?
- Can the outcome be independently verified?
- Can governance intervene?
- Can financial settlement be automated safely?
What you can build
Outcome finance
Carbon markets, impact finance, youth livelihoods, development finance, and grant disbursement systems that move value only when outcomes are evidenced and verified.
Digital MRV
Measurement, reporting, and verification systems with cryptographic trust, automated evaluation, and verifiable certification.
AI-native operations
AI-assisted accounting, public health coordination, digital compliance, supply chain verification, and scientific collaboration with governed AI delegation and verifiable execution.
Sovereign collaboration
Federated research, public–private coordination, regulated data exchanges, and decentralised service marketplaces with sovereign data ownership and interoperable identity.
Design principles
Humans remain accountable
Humans remain accountable
Humans stay in the loop for governance, policy, accountability, oversight, escalation, and strategic judgement. AI systems augment coordination capacity. They do not replace institutional responsibility.
Trust must be verifiable
Trust must be verifiable
Assertions are insufficient. The system must support evidence, provenance, cryptographic verification, reproducibility, evaluation, and dispute resolution.
Cooperation requires shared reality
Cooperation requires shared reality
Intelligence must produce outcomes
Intelligence must produce outcomes
The value of AI is not generated by conversations. It is generated by decisions, coordination, execution, and measurable outcomes.
Frequently asked questions
Is this a blockchain platform?
Is this a blockchain platform?
Partially. Blockchain is used where durable public verification and settlement are necessary. Most operational collaboration occurs off-chain using encrypted shared state. The architecture balances sovereignty, scalability, privacy, interoperability, and auditability. See IXO Protocol and IXO Matrix.
Does this replace existing enterprise systems?
Does this replace existing enterprise systems?
No. IXO and Qi integrate with existing CRMs, ERPs, AI platforms, databases, identity providers, messaging systems, and analytics systems. The goal is trusted coordination across systems, not replacement. See Integrations and Model Context Protocol (MCP) servers.
Can organisations control their own data?
Can organisations control their own data?
Yes. The architecture is designed around sovereign identity, end-to-end encryption, federated infrastructure, explicit permissions, and portable trust. See Domain privacy and IXO Matrix.
Can AI agents perform real operational work?
Can AI agents perform real operational work?
Yes — within governed trust boundaries. Agents can evaluate, coordinate, classify, generate, monitor, trigger workflows, and propose actions. Sensitive operations can require approvals, evaluations, multi-party authorisation, policy enforcement, and human oversight. See Agent evaluations and Claim evaluation protocol.
Where to go next
Act on Reality
Outcome-first positioning and a short verified-claims walkthrough.
Core concepts
Vocabulary and mental models for entities, claims, evidence, state, and cooperation.
What you can build
Pick a first POD, Flow, Blueprint, Oracle, asset, or Market.
Developer overview
SDKs, APIs, and implementation entry points.
Glossary
Short definitions of IXO and Qi terms.
Product and SDK map
Which surface owns what across the stack.