Design a Blueprint

Plan a Blueprint, a reusable set of rules for one type of claim: its scope, claim form, evidence standard, roles, rubric and what follows each decision.

A Blueprint is Qi's word for a protocol: a reusable set of rules for one type of claim. It says what a submitter fills in, what evidence the claim needs, and the rubric the claim is judged by. Plan one when the same rules have to apply across many PODs, Flows or markets, so that every claim of that type is checked the same way. This page helps you write those rules down before anyone builds them.

You end withA Blueprint design: its scope, the claim and its form, the evidence standard, the roles, the rubric, what follows each decision, and a version with test examples.
Who decidesWhoever governs the Blueprint owns its rules and decides when they change. A decision oracle produces the facts the rubric asks for, and the IXO decision engine applies the rules.

What you are designing

PartWhat you decide
ScopeWhat the Blueprint governs, and what its claims are about
ClaimWhat a participant can claim, and what they fill in to claim it
Evidence standardWhich evidence is accepted, and what gets a claim rejected
RolesWho may submit, review, approve, dispute, audit, publish and change the rules
RubricThe rules the claim is judged by
OutcomesWhat follows each decision
ExceptionsHow disputes and exceptions are handled
VersionHow the rules change, and how a reader can tell which version applied

Design steps

Write the scope

State exactly what the Blueprint governs. Keep it narrow at first: one claim type, one service category, one verification method or one class of outcome.

A first Blueprint could standardise one of these: service delivery, claim processing, outcome approval, project eligibility, supplier onboarding, credential issuance or marketplace fulfilment.

Define the claim

Write what a participant can claim. For each claim, name its subject, who makes it, the evidence it needs, the rule it is reviewed under, and the decisions it can end in.

Set the evidence standard

List the types of evidence you accept and the metadata each must carry. Say where the evidence must come from, how recent it must be, and what makes you reject it.

Name the roles

Decide who can submit, review, approve, dispute, audit and publish, and who governs changes to the Blueprint.

Write the rubric

Turn the rules into criteria that a person and an agentic oracle would apply the same way. Design an evaluator shows how to split criteria into gates, scores, named facts and review tasks.

Decide what follows each decision

For each decision, write what happens next. For example: approve the claim, request more evidence, reject the claim, issue a credential, update the state of an outcome, release a payment, or start another Flow.

Plan for disputes and exceptions

Say what happens when a claim does not fit the rules, and how someone challenges a result. On chain a dispute is a record of its own, separate from the claim. See How claim disputes work on chain.

Version and test it

Test the Blueprint against representative examples before you publish it. Keep a version history, so that a later reader can inspect how the rules changed.

What a Blueprint does not do

  • It does not decide. It holds the rules. A decision oracle produces the facts and the IXO decision engine applies the rules to them.
  • It does not run the work. A Flow does that. See Design a Flow.
  • It does not make a result true. A claim that passes shows the evidence met the rules as written. What each record proves explains the difference.

Where a Blueprint is built

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.