> ## 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. # Act on Reality > Turn your intent into verifiable outcomes, through intelligent cooperation. AI agents can plan, reason, and call tools. But real-world work doesn't just need more capable agents, it needs **shared reality** and a source of truth across these dimensions: **Why we are doing it**—**verifiable intent** so people, programs, and agents align on purpose and success criteria, not only on tasks or outputs. **Who is involved**—identities and **roles**: who can represent an organization, a device, a service, or an agent in the system, and how that is established and delegated. **What is being asserted**—**claims** and the **protocols** that supply rubrics, rules, standards, and outcome definitions so assertions can be reviewed against something explicit. **What backs the claim**—documents, measurements, observations, attestations, media, reports, sensor data, or external records, linked so reviewers and automation can inspect the same material. **Who has authority to act**—**credentials**, **capabilities**, and **permissions** that determine who may submit, attest, dispute, pay, publish, or change state on behalf of whom. **Whether a result holds**—decisions, impacts, and approvals: what was reviewed, by whom, under which rules, and what was accepted, rejected, or sent back for more evidence. **What changed**—**transactions**, **state transitions**, and **immutable logs** so “what happened” is inspectable over time, not only the latest screen in an app. **What was achieved**—**verifiable outcomes** tied to evidence and decisions: the record of what the system treats as true after review, suitable for reporting, funding, or compliance. **How value moves**—**financing**, **generation and circulation of assets**, and **value flows** (payments, rewards, fees, reserves, settlement) that can be anchored to verified outcomes and governed rules, not only offline agreements. **What should happen next**—**cooperative workflows** that route the right actor, human or agent, to the next step using shared context and governed handoffs—not ad hoc chat threads. **IXO with Qi** provides the operating systems for acting on reality, for you and your organization to make positive impacts on the world, and for you to benefit from the intelligence economy. ## What makes this different Most AI platforms help agents complete tasks inside existing tools. IXO and Qi help you build workflows that people, organizations, and agents can trust across many systems and participants. Use this stack when your workflow needs to know who is involved, what is being claimed, what evidence supports it, who has authority to decide, what value should move, and what outcome was actually achieved. **IXO is the trust layer** that creates a verifiable graph of the state of real-world entities, with identities, claims, credentials, evidence, transactions, and verifiable outcomes. **Qi is the intelligent cooperating system** that empowers humans, AI agents, applications, and services to cooperate over that graph through secure context, declared tools, governed workflows, and inspectable state changes. Model people, organizations, assets, claims, evidence, credentials, transactions, and outcomes as connected graph state. Link claims to evidence, credentials, attestations, authority, and protocol-defined state changes. Coordinate humans, agents, applications, and services through shared context and governed workflows. Connect measurements, verification, funding, governance, and learning to real-world results. ## How it works Let's look at a verified claims workflow to see how IXO and Qi are different from ordinary agent tooling. An implementer, organization, device, service, or agent submits a claim about work completed, evidence collected, eligibility, delivery, compliance, performance, or impact. Documents, measurements, observations, attestations, reasoning traces, media, reports, sensor data, or external records are attached to the claim. The workflow verifies who submitted the claim, which domain or entity they represent, the credentials or permissions that allowed them to act, and which capabilities were invoked. Agentic Oracles, overseen by human operators, inspect evidence, check program rules, flag risks, summarize context, generate decision and impact determinations, then recommend next actions. Reviewers, verifiers, funders, operators, services, and agents work through secure rooms and messages, to coordinate actions, use tools, and implement cooperative workflows. Accepted claims, attestations, transactions, outcomes, payments, governance actions, or next workflow states emit decision and impact determinations as immutable, auditable records with provenance. Verified outcomes feed analytics, agent evaluation, decision support, program design, and future workflow improvement, through automated learning loops. The core pattern is that agents do not invent facts or act on disconnected prompts. **Humans and agents cooperate over shared state** to produce changes that others can inspect, rely on, and build on. **Qi** is the intelligent cooperation layer that makes this possible. ## What you can build The workflow above is one **verified-claims-shaped** slice of the stack. Everything else—**PODs, Flows, Blueprints, Agentic Oracles, assets, markets**, recurring **program shapes** (MRV, outcome-linked financing, secure cooperation rooms, learning loops) are covered in the guides. Pick a first build, see how the pieces fit together, and open program-shape accordions with stack detail and **Start here** links into hands-on guides for each shape. Shared vocabulary for domains, claims, evidence, state, cooperation, and how IXO and Qi split responsibility for verifiable outcomes. ## Canonical references Use these when wiring integrations so auth headers and base URLs match the interface you call. Chain IDs, RPC, REST, Matrix, and service base URLs referenced in docs Auth patterns by API surface (protocol gateways vs service APIs) Short definitions of IXO terms with links to deep dives ## This is just the beginning. Turn your intent into a programmable organizational domain (POD) with a shared workspace, configured flows for your team and AI agents, and economic mechanisms. Automate work, elevate productivity, earn financial rewards, and drive positive impact with verifiable records of outcomes. The data, memories, and intelligence you generate remain yours to own and control. You can sell, rent, or trade it as you choose.