> ## 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.

# Build a Blueprint

> Define a reusable protocol for deeds, claims, evidence, roles, rubrics, rules, verifications, and settlements for PODs, Flows, Assets, Oracles, and Markets.

## Build a Blueprint

A Blueprint is a reusable protocol. It defines how a type of deed, claim, asset, service, outcome, or marketplace interaction should be structured, evidenced, reviewed, verified, and settled.

Build a Blueprint when you need repeatable rules that can be used across many PODs, Flows, Assets, Oracles, or Markets.

<Card title="Blueprint Builder" icon="wand-magic-sparkles" href="#add-protocol-builder-url" cta="Build with AI" arrow={true}>
  Use the Blueprint Builder Agentic Oracle in qi.space to turn your rules, standards, rubrics, schemas, roles, evidence requirements, and outcome logic into a Blueprint.
</Card>

### What you will create

* Blueprint purpose and scope
* Entity types covered by the blueprint
* Claim schemas
* Evidence requirements
* Roles and authority model
* Rubrics and decision logic
* Verification rules
* State transition rules
* Outcome definitions
* Dispute or exception handling
* Versioning and governance rules

### Quick start

<Steps>
  <Step title="Define the blueprint scope">
    State exactly what the Blueprint governs. Avoid broad protocols at first. Use a narrow scope such as one claim type, one service category, one verification method, or one outcome class.
  </Step>

  <Step title="Define the claims">
    Specify what participants can claim. Each claim should have a clear subject, claimant, evidence requirement, review rule, and possible decision outcome.
  </Step>

  <Step title="Define the evidence standard">
    List acceptable evidence types, required metadata, provenance requirements, freshness rules, and rejection conditions.
  </Step>

  <Step title="Define the roles and authority">
    Decide who can submit, review, verify, approve, dispute, audit, publish, or govern changes to the Blueprint.
  </Step>

  <Step title="Define the rubric">
    Convert rules into review criteria. Make the rubric clear enough for humans and Agentic Oracles to apply consistently.
  </Step>

  <Step title="Define state transitions">
    Specify what happens after each decision. For example: approve claim, request evidence, reject claim, issue credential, update outcome state, release payment, or trigger another Flow.
  </Step>

  <Step title="Version and test the Blueprint">
    Test the Blueprint against representative examples before publishing. Keep version history so changes to rules can be inspected later.
  </Step>
</Steps>

### Useful first scope

Start with a blueprint that standardizes one of these:

* verified service delivery
* claim processing
* outcome approval
* project eligibility
* supplier onboarding
* credential issuance
* marketplace fulfillment

### Resources

<CardGroup cols={2}>
  <Card title="Blueprints" icon="diagram-project" href="/blueprints/blueprints">
    Start from reusable protocol templates for claims, evidence, verification, governance, credentials, fulfillment, or outcome settlement.
  </Card>

  <Card title="Concepts" icon="file-signature" href="/concepts/blueprints">
    Learn how Blueprints define schemas, roles, authority, evidence rules, rubrics, verification logic, and state changes.
  </Card>

  <Card title="Code with AI" icon="terminal" href="/guides/blueprints/code-with-ai">
    Generate schemas, rubrics, fixtures, validation logic, protocol documentation, and test cases with an AI coding assistant.
  </Card>

  <Card title="Deep dive" icon="book-open" href="/guides/blueprints/deep-dive">
    Understand protocol design, versioning, verification patterns, governance, composability, and production rollout.
  </Card>
</CardGroup>