Build a Flow

Design a governed workflow that coordinates people, agents, tools, evidence, decisions, and state transitions.

Build a Flow

A Flow is a governed workflow for real-world work. It coordinates people, Agentic Oracles, tools, evidence, decisions, transactions, and state transitions.

Build a Flow when you already know the sequence of work that needs to happen, but you need it to become inspectable, repeatable, and verifiable.

Build a workflow where agents, people, organizations, evidence, value, and outcomes operate from shared verifiable state.

Flow patterns to explore

Verified claims workflows

Submit, review, attest, dispute, and resolve claims with linked evidence and explicit authority.

Digital MRV systems

Connect measurements, reports, verification, and outcomes into auditable workflows.

Outcomes-based financing

Release funding, incentives, or other value when agreed outcomes are verified.

Agentic evidence review

Use AI agents to inspect evidence, check rules, flag risks, and support human decisions.

Multi-party data rooms

Coordinate funders, implementers, verifiers, communities, services, and agents in secure spaces.

Verified learning loops

Feed verified outcomes back into analytics, agents, programs, and future workflows.

The common workflow pattern

Most IXO and Qi applications follow the same underlying pattern.

Create Entity

A person, organization, project, asset, place, service, agent, or workflow is represented in the IXO Graph, configured with controllers, services, resources, claims, accounts, and relationships.

Authorize Actions (UCAN)

A person, service or an oracle is authorized to act on the entity, claim, evidence, or state.

Submit Claims

A person, service or an oracle asserts that something is true: work was completed, evidence was collected, eligibility was met, or an outcome occurred.

Process Claims

An evaluation oracle service reviews the claim and evidence, checking rules, rubrics, permissions, and workflow requirements.

Verify (UDID)

A qualified actor or process accepts, rejects, disputes, or verifies the claim, submitting a signed Universal Decision and Impact Determination (UDID).

Update State

The accepted result becomes part of IXO-backed state and can trigger downstream actions or stored as a record to be queried, inspected, and used by other workflows.

Settle

The system can trigger payment, governance, escalation, notification, credential issuance, or another workflow step. The UDID is recorded as a transaction on the IXO Chain, and the outcome is stored as a record to be queried, inspected, and used by other workflows.

Learn

Verified outcomes and results feed analytics, agent evaluation, model improvement, and improved future decisions and actions.

Flow Builder

Use the Flow Builder Agentic Oracle in qi.space to turn your process, actors, triggers, actions, tools, and approvals into an executable workflow design.

Build with AI

What you will create

  • Trigger that starts the Flow
  • Actors and responsibilities
  • Workflow states
  • Actions available at each state
  • Evidence required at each step
  • Agentic Oracle tasks and tool access
  • Human approvals and escalation paths
  • Decision outputs
  • State changes written to the graph
  • Notifications, handoffs, and next actions

Quick start

Choose the trigger

Decide what starts the Flow. Common triggers include a claim submission, onboarding request, marketplace order, scheduled review, data update, governance decision, or external event.

Define the actors

List who participates in the Flow. Separate submitters, reviewers, verifiers, approvers, funders, operators, agents, services, and observers.

Map the states

Write the workflow as states, not just tasks. For example: Draft, Submitted, Evidence Required, In Review, Approved, Disputed, Settled, Closed.

Attach actions and permissions

For each state, define who can act, what tools they can use, what data they can access, and which actions change state.

Add evidence and review logic

Connect the Flow to the Blueprint that defines claim schemas, evidence rules, rubrics, verifier requirements, and approval logic.

Test with edge cases

Run at least one happy path, one missing-evidence case, one rejected case, and one escalation case before putting the Flow into production.

Useful first scope

Start with a Flow that answers one operational question:

  • Can this participant be onboarded?
  • Is this claim complete?
  • Does this evidence satisfy the protocol?
  • Should this outcome be approved?
  • Should this value be released?
  • Should this task be escalated to a human?

Resources

Blueprints

Start from Flow templates for claims processing, digital MRV, approvals, onboarding, fulfillment, governance, or settlement.

Concepts

Learn how Flows coordinate triggers, actors, states, actions, evidence, permissions, Agentic Oracles, and graph updates.

Code with AI

Generate workflow schemas, state machines, test cases, agent instructions, and integration code with an AI coding assistant.

Deep dive

Understand Flow architecture, state transitions, tool invocation, escalation, observability, and production operations.