Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/workflows/docs-quality.yml
Original file line number Diff line number Diff line change
Expand Up @@ -13,12 +13,12 @@ jobs:

steps:
- name: Checkout repository
uses: actions/checkout@v4
uses: actions/checkout@v5

- name: Set up Node.js
uses: actions/setup-node@v4
uses: actions/setup-node@v5
with:
node-version: "20"
node-version: "24"
cache: npm

- name: Install dependencies
Expand Down
4 changes: 2 additions & 2 deletions articles/ixo-graph.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
- what has been verified
- what should happen next

Use the IXO Graph when your system needs more than private data storage. Use it when multiple participants, applications, services, or agents need to coordinate around the same inspectable reality, and when you need to trace changes over time.

Check warning on line 20 in articles/ixo-graph.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/ixo-graph.mdx#L20

Did you really mean 'inspectable'?

<Tip>
Think of the IXO Graph as the shared operating map for intelligent cooperation. IXO Protocol records verifiable state. Qi uses that state to coordinate humans, agents, applications, and services.
Expand All @@ -25,7 +25,7 @@

## Why it matters

Most real-world work is fragmented across spreadsheets, documents, chats, CRMs, dashboards, blockchains, APIs, and institutional records.

Check warning on line 28 in articles/ixo-graph.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/ixo-graph.mdx#L28

Did you really mean 'CRMs'?

Check warning on line 28 in articles/ixo-graph.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/ixo-graph.mdx#L28

Did you really mean 'blockchains'?

That fragmentation creates coordination failures:

Expand Down Expand Up @@ -58,7 +58,7 @@
Transactions, attestations, Flow events, state transitions, and decisions.
</Accordion>
<Accordion title="What was determined?" icon="scale-balanced">
Evaluation Claims, approvals, rejections, disputes, UDIDs, and outcomes.

Check warning on line 61 in articles/ixo-graph.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/ixo-graph.mdx#L61

Did you really mean 'UDIDs'?
</Accordion>
<Accordion title="What happens next?" icon="route">
Flow state, allowed actions, assigned roles, agent tools, and settlement rules.
Expand Down Expand Up @@ -113,11 +113,11 @@
</Step>

<Step title="Record change over time">
Transactions, attestations, Flow events, Evaluation Claims, and UDIDs create an inspectable history of what changed and why.

Check warning on line 116 in articles/ixo-graph.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/ixo-graph.mdx#L116

Did you really mean 'UDIDs'?

Check warning on line 116 in articles/ixo-graph.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/ixo-graph.mdx#L116

Did you really mean 'inspectable'?
</Step>

<Step title="Enable the next action">
Humans, services, and Agentic Oracles use the graph to decide what is allowed, what needs review, what can be settled, and what should happen next.

Check warning on line 120 in articles/ixo-graph.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/ixo-graph.mdx#L120

Did you really mean 'Agentic'?
</Step>
</Steps>

Expand All @@ -143,7 +143,7 @@
</Step>

<Step title="An agent evaluates the Claim">
An Agentic Oracle inspects only the context it is authorized to access, applies the active rubric, and creates an Evaluation Claim.

Check warning on line 146 in articles/ixo-graph.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/ixo-graph.mdx#L146

Did you really mean 'Agentic'?
</Step>

<Step title="A verifier makes a determination">
Expand Down Expand Up @@ -206,7 +206,7 @@
- resolve which entities are involved in a Flow
- retrieve Claims, evidence, credentials, and workflow history
- check whether a participant, service, or agent has authority
- give Agentic Oracles structured context instead of disconnected prompts

Check warning on line 209 in articles/ixo-graph.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/ixo-graph.mdx#L209

Did you really mean 'Agentic'?
- separate submitted information from verified state
- record Evaluation Claims and UDID-backed determinations
- trigger allowed state transitions, messages, payments, credentials, or next actions
Expand Down Expand Up @@ -298,7 +298,7 @@
</Accordion>

<Accordion title="Record decisions separately">
Keep recommendations, reviews, approvals, disputes, UDIDs, and state transitions distinct so decisions can be audited and challenged.

Check warning on line 301 in articles/ixo-graph.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/ixo-graph.mdx#L301

Did you really mean 'UDIDs'?
</Accordion>

<Accordion title="Design for replay">
Expand All @@ -317,8 +317,8 @@
- [ ] agent permissions are scoped
- [ ] workflow states are defined
- [ ] Evaluation Claims have a structured schema
- [ ] UDIDs record decision and impact determinations

Check warning on line 320 in articles/ixo-graph.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/ixo-graph.mdx#L320

Did you really mean 'UDIDs'?
- [ ] state transitions are inspectable

Check warning on line 321 in articles/ixo-graph.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/ixo-graph.mdx#L321

Did you really mean 'inspectable'?
- [ ] disputes and corrections have a path
- [ ] applications and agents can query only what they are allowed to access
- [ ] verified outcomes can feed reporting, settlement, research, or learning loops
Expand Down Expand Up @@ -346,16 +346,16 @@
## Next steps

<CardGroup cols={2}>
<Card title="Start Building" icon="rocket" href="/start-building">
<Card title="Start Building" icon="rocket" href="/guides/what-you-can-build">
Build a POD, Flow, Blueprint, or Marketplace using IXO and Qi.
</Card>

<Card title="Core Concepts" icon="lightbulb" href="/core-concepts">
Learn the vocabulary for entities, Claims, evidence, credentials, Flows, Blueprints, and outcomes.
</Card>

<Card title="Agent Evaluations" icon="clipboard-check" href="/guides/agent-evaluations">
<Card title="Agent Evaluations" icon="clipboard-check" href="/guides/dev/agent-evaluations">
Evaluate agent work using UCAN authority, Claims, rubrics, evidence, Flow state, and UDIDs.

Check warning on line 358 in articles/ixo-graph.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/ixo-graph.mdx#L358

Did you really mean 'UDIDs'?
</Card>

<Card title="What You Can Build" icon="shapes" href="/guides/what-you-can-build">
Expand Down
8 changes: 4 additions & 4 deletions articles/pods.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@
- which decisions, payments, credentials, or state changes are allowed

<Tip>
A POD is not just a workspace, DAO, database, or chatbot. It is the governed domain where shared state, human roles, agent authority, workflows, and verifiable outcomes come together.

Check warning on line 22 in articles/pods.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/pods.mdx#L22

Did you really mean 'chatbot'?
</Tip>

## When to build a POD
Expand All @@ -28,7 +28,7 @@

<CardGroup cols={2}>
<Card title="Program operations" icon="diagram-project">
Coordinate funders, implementers, verifiers, researchers, agents, and services inside one program domain.

Check warning on line 31 in articles/pods.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/pods.mdx#L31

Did you really mean 'funders'?
</Card>

<Card title="Verified service delivery" icon="handshake">
Expand Down Expand Up @@ -77,7 +77,7 @@

<Accordion title="Blueprints">Protocols that define schemas, evidence rules, rubrics, authority, and outcomes</Accordion>

<Accordion title="Agents">Agentic Oracles or AI services that support review, routing, analysis, monitoring, and decision support</Accordion>

Check warning on line 80 in articles/pods.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/pods.mdx#L80

Did you really mean 'Agentic'?

<Accordion title="Rooms">Secure cooperation spaces for humans, agents, and services</Accordion>

Expand Down Expand Up @@ -110,7 +110,7 @@
</Step>

<Step title="Agents support the process">
Agentic Oracles can inspect permitted context, apply rubrics, summarize evidence, flag risks, and create Evaluation Claims.

Check warning on line 113 in articles/pods.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/pods.mdx#L113

Did you really mean 'Agentic'?
</Step>

<Step title="Humans remain accountable">
Expand Down Expand Up @@ -168,7 +168,7 @@

<Accordion title="`evidence_required`">Required evidence is requested or validated</Accordion>

<Accordion title="`evaluating`">A human, service, or Agentic Oracle applies the rubric</Accordion>

Check warning on line 171 in articles/pods.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/pods.mdx#L171

Did you really mean 'Agentic'?

<Accordion title="`review_required`">A verifier, operator, or governance role reviews the result</Accordion>

Expand All @@ -176,7 +176,7 @@

<Accordion title="`actioned`">Payment, credential, state update, message, or next Flow is triggered</Accordion>

<Accordion title="`closed`">The process is complete and inspectable</Accordion>

Check warning on line 179 in articles/pods.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/pods.mdx#L179

Did you really mean 'inspectable'?
</AccordionGroup>

## PODs and agent authority
Expand Down Expand Up @@ -220,7 +220,7 @@
<AccordionGroup>
<Accordion title="Purpose">Help digital MRV programs find and pay verified field data providers</Accordion>

<Accordion title="Members">Marketplace operator, service providers, buyers, verifiers, funders, agents</Accordion>

Check warning on line 223 in articles/pods.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/pods.mdx#L223

Did you really mean 'funders'?

<Accordion title="Entities">Providers, listings, projects, service orders, Claims, evidence, outcomes</Accordion>

Expand All @@ -235,7 +235,7 @@
<Accordion title="UDID">Records whether the service was accepted and whether payment should be released</Accordion>
</AccordionGroup>

The POD gives the marketplace an operating boundary. The Flow runs the work. The Blueprint defines the rules. Claims and evidence make delivery inspectable. The UDID records the decision and impact.

Check warning on line 238 in articles/pods.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/pods.mdx#L238

Did you really mean 'inspectable'?

## Example: digital MRV program POD

Expand All @@ -244,7 +244,7 @@
<AccordionGroup>
<Accordion title="Purpose">Verify outcomes for a clean cooking, water, energy, land restoration, or biodiversity program</Accordion>

<Accordion title="Members">Program operator, field teams, device providers, communities, verifiers, funders, researchers</Accordion>

Check warning on line 247 in articles/pods.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/pods.mdx#L247

Did you really mean 'funders'?

<Accordion title="Entities">Households, devices, projects, reporting periods, measurements, Claims, outcomes</Accordion>

Expand All @@ -252,7 +252,7 @@

<Accordion title="Flow">Submit measurement Claim, validate evidence, review, determine outcome, trigger settlement</Accordion>

<Accordion title="Agent">Agentic Oracle summarizes evidence and flags anomalies</Accordion>

Check warning on line 255 in articles/pods.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/pods.mdx#L255

Did you really mean 'Agentic'?

<Accordion title="Human role">Verifier reviews edge cases and approves determinations</Accordion>

Expand Down Expand Up @@ -309,11 +309,11 @@
</Accordion>

<Accordion title="Separate recommendation from decision">
Agent outputs should be recorded as Evaluation Claims. Decisions and impacts should be recorded as UDIDs when the Flow reaches a determination point.

Check warning on line 312 in articles/pods.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/pods.mdx#L312

Did you really mean 'UDIDs'?
</Accordion>

<Accordion title="Use Blueprints for repeatability">
Put schemas, evidence requirements, rubrics, thresholds, disqualifiers, escalation rules, and outcome logic into a Blueprint.

Check warning on line 316 in articles/pods.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/pods.mdx#L316

Did you really mean 'disqualifiers'?
</Accordion>

<Accordion title="Design for audit and dispute">
Expand All @@ -340,7 +340,7 @@
- agent permissions are scoped
- human review is required for high-risk decisions
- Evaluation Claims have a structured schema
- UDIDs are used for decision and impact determinations

Check warning on line 343 in articles/pods.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/pods.mdx#L343

Did you really mean 'UDIDs'?
- payments, credentials, and state updates require valid authority
- disputes and corrections have a path
- participants know where to act and what happens next
Expand All @@ -349,19 +349,19 @@
## What to build next

<CardGroup cols={2}>
<Card title="Build a Flow" icon="route" href="/start-building#build-a-flow">
<Card title="Build a Flow" icon="route" href="/guides/users/build-a-flow">
Define the workflow that runs inside your POD.
</Card>

<Card title="Build a Blueprint" icon="file-signature" href="/start-building#build-a-blueprint-protocol">
<Card title="Build a Blueprint" icon="file-signature" href="/guides/users/build-a-blueprint">
Define the schemas, rules, evidence requirements, rubrics, and outcome logic.
</Card>

<Card title="Build a Marketplace" icon="store" href="/start-building#build-a-marketplace">
<Card title="Build a Marketplace" icon="store" href="/guides/users/build-a-market">
Create trusted exchange for services, protocols, data, agent capabilities, or verified outcomes.
</Card>

<Card title="Agent Evaluations" icon="clipboard-check" href="/guides/agent-evaluations">
<Card title="Agent Evaluations" icon="clipboard-check" href="/guides/dev/agent-evaluations">
Evaluate agent work using Claims, evidence, UCAN authority, rubrics, Flow state, and UDIDs.

Check warning on line 365 in articles/pods.mdx

View check run for this annotation

Mintlify / Mintlify Validation (ixoworld) - vale-spellcheck

articles/pods.mdx#L365

Did you really mean 'UDIDs'?
</Card>
</CardGroup>
Loading
Loading