Your Role

People, agents, services, markets, protocols, and institutions are beginning to cooperate through shared digital systems rather than only through traditional organizational structures.

Many of the biggest problems we face in daily life and as humanity are coordination failures. We have the intent, knowledge, resources, and technologies to solve many problems, but we struggle to align people, verify facts, allocate capital, govern action, and learn from outcomes.

In an AI future, the optimal path is voluntary intelligent cooperation.

IXO and Qi give you a way to participate in this new operating model. IXO provides the verifiable state layer for identities, Claims, credentials, evidence, assets, outcomes, and transactions. Qi coordinates humans, AI agents, applications, services, and organizations through secure workspaces, governed Flows, capability-based authority, and inspectable state changes.

What it does: Creates a programmable organizational domain.

Why it matters: Gives people, agents, services, and organizations a secure place to cooperate.

What it does: Coordinates work through governed steps.

Why it matters: Turns activity into inspectable state transitions.

What it does: Defines a reusable protocol.

Why it matters: Makes rules, rubrics, evidence requirements, and outcomes repeatable.

What it does: Enables trusted exchange.

Why it matters: Helps participants discover, offer, request, verify, and settle value.

What it does: Records something asserted, submitted, reviewed, delivered, or achieved.

Why it matters: Makes work, evidence, and outcomes inspectable.

What it does: Delegates scoped authority to people, agents, services, or tools.

Why it matters: Ensures actions happen within explicit permissions.

What it does: Records a decision and impact determination.

Why it matters: Creates an auditable record of what was decided, why, by whom, and with what effect.

Example: Field data collection for clean cooking usage.

Example: Digital MRV program operator.

Example: Service request, delivery, evidence submission, review, approval, payment.

Example: Work completed for household visits.

Example: Field reports, timestamps, geo-tagged observations, photos, device references.

Example: Human verifier or Agentic Oracle checks completeness and consistency.

Example: Determines whether the service was accepted and whether payment should be released.

Example: Service completed, evidence submitted, outcome achieved, supplier verified.

Example: Evidence Review Oracle.

Example: Read one Claim, inspect linked evidence, apply one rubric, create one Evaluation Claim.

Example: Submitted, authority check, context resolved, evaluating, human review, determined, actioned.

Example: Evaluation Claim and proposed transition.

Example: UDID after human or protocol-approved decision.

Example: Pay for verified adoption of a clean cooking technology.

Example: Program domain for funders, implementers, verifiers, and agents.

Example: Protocol defining eligible households, evidence, usage thresholds, and outcomes.

Example: Application, service delivery, claim submission, review, determination, payment.

Example: Outcome achieved for a household or project.

Example: Device telemetry, field report, household record, verifier attestation.

Example: Determines whether the outcome was verified and whether value should be released.

Example: Service completed, outcome achieved, supplier eligible, data submitted.

Example: Documents, measurements, observations, attestations, media, reports, sensor data.

Example: Required fields, evidence checks, thresholds, disqualifiers, escalation rules.

Example: Summarizes evidence and flags inconsistencies.

Example: Accepts, rejects, escalates, or requests more evidence.

Example: Records findings and recommendation.

Example: Records the accountable determination.

Example: Which evidence types most reliably predict verified service delivery?

Example: Claims, evidence references, Evaluation Claims, UDIDs, Flow timestamps.

Example: Research workspace with scoped access.

Example: Research protocol defining methods and access rules.

Example: Data access request, analysis, review, publication.

Example: Research Claim with methods, findings, evidence references, and limitations.

Example: Update rubrics, evidence requirements, or Flow design based on findings.

Example: Evidence collection services for digital MRV programs.

Example: Field operators and data service providers.

Example: Program operators, funders, project developers.

Example: Service area, method, capacity, price, credentials, evidence standards.

Example: Request, accept, deliver, submit evidence, evaluate, settle.

Example: Verification rules for service completion and evidence quality.

Example: Payment released after accepted service determination.

Example: Completed services, disputes, evaluations, and credentials update supplier profile.

Start as: Service Provider

Start as: Developer

Start as: Funder

Start as: Evaluator

Start as: Researcher

Start as: Market-maker

The provider knows what they offer, which POD or Marketplace they operate in, which Claims they submit, what evidence is required, and how settlement happens.

The workflow has typed Claims, scoped UCAN authority, explicit Flow states, safe tool access, structured outputs, test cases, and inspectable records.

The funding rules define eligibility, evidence, evaluation, determination, settlement, disputes, and governance.

The evaluator has a versioned rubric, scoped authority, evidence access, clear escalation rules, and a way to record Evaluation Claims and UDIDs.

The research process has authorized data access, defined methods, evidence references, review rules, privacy boundaries, and publication standards.

The marketplace has a clear category, supplier and buyer rules, listing standards, fulfillment Flows, verification Blueprints, settlement logic, and dispute handling.