> ## 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. # Your Role > Choose how you want to start your journey into the future of voluntary intelligent cooperation, based on your intent to build, fund, evaluate, research, develop, or make markets for the verified outcomes you want to achieve. We are now all builders of the future we want to live in, where the form of how we organize is fundamentally changing with AI. This is redefining the roles we play in the system, and the way we cooperate to achieve our goals. 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. Start by choosing the role you are playing now. You may hold more than one role. Choose the role that best matches what you want to do first. ## Choose your entry point Offer services, capabilities, data, verification, implementation, agent support, or outcomes through trusted PODs, Flows, and Marketplaces. Build applications, Agentic Oracles, MCP tools, Qi Flows, integrations, schemas, and automation over IXO-backed state. Allocate capital to programs, outcomes, services, protocols, markets, or organizations with verifiable evidence and settlement rules. Review Claims, inspect evidence, apply rubrics, issue determinations, and support trusted decisions. Generate knowledge from verified data, evidence graphs, experiments, Claims, outcomes, and learning loops. Create trusted exchange, liquidity, discovery, pricing, fulfillment, and settlement for services, protocols, agents, data, and outcomes. ## The shared building blocks Every role works with the same core building blocks. **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. *** ## 🤝 Service Provider You are a Service Provider if you want to offer useful work into the IXO and Qi ecosystem. You may provide implementation services, evidence collection, verification, AI agent operations, data services, research support, digital MRV, local field operations, protocol design, marketplace fulfillment, or outcome delivery. ### Your role Service Providers help turn intent into verified action. You may: * deliver services for a POD * fulfill a Marketplace listing * submit Claims about completed work * attach evidence to Claims * operate an Agentic Oracle * provide field verification or expert review * implement a protocol in the real world * receive payment, rewards, credentials, or reputation when outcomes are verified ### Start your journey Describe the service, capability, data, verification function, agent service, or outcome you can reliably deliver. Join an existing POD, create your own POD, or publish your offer into a Marketplace. Define the intake, delivery, evidence, review, approval, and settlement steps for your work. Record what you delivered and attach documents, measurements, observations, reports, attestations, media, sensor data, or external records. Let evaluations, UDIDs, credentials, payments, and completed outcomes become part of your operating history. ### First useful build Start with one verified service offer. **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. ### Build path Operate inside a secure domain with roles, tools, rooms, agents, and governed permissions. Make your service discoverable to buyers, funders, programs, and other participants. Coordinate service delivery, evidence submission, review, approval, and settlement. Make your Claims reviewable under clear evidence rules and outcome criteria. *** ## 💻 Developer You are a Developer if you want to build the technical systems that make intelligent cooperation work. You may build applications, Agentic Oracles, MCP tools, Qi Flows, schemas, data integrations, evidence pipelines, marketplace components, claim processors, dashboards, or developer tools. ### Your role Developers make verifiable coordination programmable. You may: * build apps that read and write IXO-backed graph state * create Qi Flows for governed workflows * define Claim schemas and validation logic * build Agentic Oracles for review, routing, summarization, or decision support * expose tools through MCP interfaces * use UCANs to scope agent and service authority * generate Evaluation Claims and UDID records * connect marketplaces, payments, credentials, and external systems ### Start your journey Pick one coordination problem, such as claim review, evidence intake, service fulfillment, funding approval, marketplace ordering, or credential issuance. Identify the entities, Claims, evidence, credentials, roles, Flow states, and decisions that need to exist. Use UCAN-style capability scoping so agents, services, and users can only perform allowed actions on allowed resources. Create the trigger, states, actions, failure paths, human checkpoints, and outputs. Add Agentic Oracles, MCP tools, validation services, external APIs, data pipelines, and dashboards. Ensure the system emits Claims, Evaluation Claims, evidence references, state transitions, and UDIDs where decisions and impacts are determined. ### First useful build Start with an agent-assisted Claim review Flow. **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. ### Build path Create the governed state machine for the workflow you want to automate. Add agent services for evidence review, decision support, summarization, or monitoring. Expose structured context and actions to agents without giving them uncontrolled system access. Create, validate, evaluate, dispute, and automate verifiable Claims. *** ## 💰 Funder You are a Funder if you want to allocate capital toward verified work, services, outcomes, programs, or markets. You may fund impact programs, service delivery, outcome incentives, liquidity pools, research, protocol development, verification capacity, agent services, or marketplace growth. ### Your role Funders help turn resources into verified outcomes. You may: * create or fund a POD * define funding eligibility rules * sponsor outcomes-based programs * fund Marketplace demand or liquidity * release value when Claims are verified * require evidence, evaluation, and UDID-backed determinations * support service providers, researchers, and developers * govern how funds are allocated, reserved, released, or recovered ### Start your journey State what outcome, service, protocol, market, or organization you want to support. Decide whether you are funding grants, services, verified outcomes, marketplace liquidity, research, protocol development, or ongoing operations. Specify the Claims, evidence, credentials, evaluations, and determinations required before value moves. Use a Flow to govern intake, eligibility, approval, evidence review, milestone completion, dispute handling, and settlement. Release funds only after the required decision and impact determination exists. ### First useful build Start with one outcome-funded program. **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. ### Build path Set up the operating domain for funders, operators, implementers, verifiers, and agents. Specify eligibility, evidence, rubrics, outcome rules, and settlement conditions. Govern applications, reviews, milestones, determinations, payments, and disputes. Create demand, incentives, liquidity, or rewards for verified services and outcomes. *** ## ✅ Evaluator You are an Evaluator if you review Claims, inspect evidence, apply rubrics, issue recommendations, or make determinations. You may be a human verifier, expert reviewer, auditor, governance participant, standards body, community representative, or operator of an Agentic Oracle. ### Your role Evaluators create trust in the system. You may: * inspect Claims and linked evidence * check whether evidence satisfies a Blueprint * apply a rubric * identify missing, stale, invalid, or conflicting evidence * create Evaluation Claims * recommend approval, rejection, escalation, or dispute * issue or support UDID-backed determinations * improve rubrics and protocols based on review outcomes ### Start your journey Start with one type of Claim that you can evaluate consistently. Apply a versioned Blueprint that defines evidence requirements, scoring, disqualifiers, thresholds, and escalation rules. Confirm that you, your service, or your Agentic Oracle has the UCAN authority required to inspect the Claim and perform the evaluation. Write the review result as structured data with evidence references, applied checks, recommendation, limitations, and proof. When the Flow reaches a decision point, record the final decision and impact determination with authority, evidence, and state transition. ### First useful build Start with agent-assisted evidence review. **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. ### Build path Evaluate agent work and evidence review using UCAN authority, Claims, rubrics, and UDID records. Work with verifiable assertions, evidence, review status, disputes, and automation. Govern review, escalation, approval, rejection, dispute, and determination steps. Define the rules that make evaluation consistent and repeatable. *** ## 🔬 Researcher You are a Researcher if you want to generate, analyze, validate, or publish knowledge from verifiable data and outcomes. You may study interventions, markets, protocols, agent behavior, evidence quality, environmental impact, social outcomes, digital MRV systems, funding mechanisms, or cooperative intelligence. ### Your role Researchers help the system learn. You may: * define research questions and hypotheses * design evidence protocols * analyze Claims, evidence, outcomes, and determinations * compare programs or interventions * evaluate agent performance * study coordination patterns * publish findings with verifiable references * improve Blueprints, rubrics, and Flows * contribute to verified learning loops ### Start your journey State what you want to learn and which real-world system, program, protocol, or market the question applies to. Determine which entities, Claims, evidence records, credentials, Flow states, UDIDs, and outcomes are relevant. Use POD roles, permissions, and UCAN-scoped access so research uses only authorized data and tools. Define data requirements, inclusion criteria, evaluation methods, reporting rules, and publication standards. Record research outputs as Claims linked to data, methods, evidence, limitations, and review history. ### First useful build Start with one verified learning loop. **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. ### Build path Set up a secure workspace for researchers, data stewards, agents, reviewers, and collaborators. Standardize methods, evidence access, analysis rules, review requirements, and publication outputs. Work with measurements, reporting, verification, Claims, determinations, and learning loops. Study agent outputs, authorization, evidence use, rubric adherence, and human override patterns. *** ## 🛍️ Market-maker You are a Market-maker if you want to create trusted exchange between participants. You may operate a Marketplace, design liquidity mechanisms, curate suppliers, create demand, define pricing, coordinate settlement, govern listings, or build markets for services, outcomes, protocols, agent capabilities, data, or credentials. ### Your role Market-makers help cooperation scale. You may: * create a Marketplace * define listing categories * onboard suppliers and buyers * set eligibility and credential requirements * create pricing, fees, rewards, or liquidity incentives * attach fulfillment Flows * attach verification Blueprints * route disputes * coordinate settlement * track market health and reputation ### Start your journey Choose the first category of services, outcomes, protocols, data, credentials, or agent capabilities that participants can offer and request. Identify suppliers, buyers, funders, verifiers, operators, agents, and governance roles. Specify listing fields, eligibility rules, pricing, availability, evidence requirements, and fulfillment terms. Every listing category should have a Flow for fulfillment and a Blueprint for verification. Decide when payments, rewards, credentials, fees, or reputation updates happen, and require UDID-backed determinations for high-value actions. ### First useful build Start with one verified service marketplace. **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. ### Build path Create the exchange layer for listings, requests, fulfillment, verification, and settlement. Operate the market with roles, governance, agents, tools, moderation, and analytics. Coordinate orders, delivery, evidence, review, disputes, and settlement. Make every listing category reviewable under clear rules and evidence standards. *** ## If you are not sure which role to choose Use this guide. **Start as:** Service Provider **Start as:** Developer **Start as:** Funder **Start as:** Evaluator **Start as:** Researcher **Start as:** Market-maker ## Recommended first operating loop The fastest path is to build one complete loop before scaling. Give the work a secure operating domain with roles, rooms, tools, agents, and authority. Specify the rules, evidence requirements, rubrics, and outcome logic. Coordinate submission, review, determination, action, and closure. Make the work inspectable with structured assertions and linked proof. Use humans, Agentic Oracles, and rubrics to create Evaluation Claims and UDID-backed decisions. Release value, issue credentials, update state, publish findings, improve the protocol, or route the next action. ## Production readiness Before inviting more participants, check that each role has a clear responsibility. 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. ## Start building Build a POD, Flow, Blueprint, or Marketplace. Explore practical use cases for IXO and Qi. Understand the verifiable graph of identities, Claims, evidence, credentials, entities, and outcomes. Learn how humans, agents, services, and organizations cooperate over shared state.