Start here
The easiest way to understand Blue is to build one small world. This page walks through a shop, an order, a payment mandate, a PayNote, and a delivery confirmation. Different interactions — same shape.
Five separate Blue documents, each with its own participants and rules, taken together forming Alice's world. Bob participates in some of them. The bank participates in another. The courier in another.
Shop ─ Alice's storefront block.Order ─ Alice + Bob, references the PayNote.Mandate ─ Bob + Bob's OpenClaw agent, governs what the agent can do.PayNote ─ Bob + Alice + Bank, governs the money on the order's transaction.Delivery confirmation ─ Alice + Courier + Bob, unlocks payment completion.
Start with a shop block.
Participants: Alice
State: business name, description, contact preferences, payment status
Operations: Alice can update her shop. Services may be invited later. Orders may be linked into it.
Timeline entry that triggers a change: Alice posts an Update Profile request to her owner channel.
Result: the shop document's state moves to the new profile, and the change is permanently recorded on Alice's timeline.
Now add an order.
Participants: Alice, Bob, optionally Bob's agent
State: item, quantity, status, notes, expected amount
Operations: Bob can place or update the order. Alice can confirm or reject it. The order may trigger or link to a payment.
Timeline entry: Bob places the order via his buyer channel; Alice accepts via her seller channel.
Result: two timelines, one document, status moves placed → accepted.
Bob wants his agent to buy safely. He creates a mandate block.
Participants: Bob, Bob's agent (e.g. OpenClaw), maybe a bank or payment operator
State: allowed payment source, boundaries, conditions, approval thresholds
Operations: the agent may only propose payments through the mandate. The proposal must satisfy the constraints. Actions outside the mandate are invalid.
Timeline entry: the agent posts a Propose Payment request through its agent channel; the mandate document validates it.
Result: a constrained, attributable agent flow that does not require giving the agent a card.
Attach a PayNote to the transaction.
Participants: Bob, Alice, the bank / guarantor, maybe delivery or verification participants
State: expected amount, secured, completed, reversed, conditions, delivery and review state
Operations: secure funds now. Complete payment later — only after conditions are satisfied. Reverse or cancel if rules allow.
Timeline entry: the bank posts a Secure Funds entry on its guarantor channel.
Result: money is part of the same explicit world as the order, the delivery, and the mandate.
Now a courier or verifier participates.
Participants: Alice, Bob, bank, courier
State: delivery status, confirmation status, timestamps
Operations: the courier can confirm delivery. That confirmation may unlock payment completion.
Timeline entry: the courier posts a Confirm Delivery entry on its courier channel; the PayNote sees it via composition and processes a Complete Payment step.
Result: the world reaches its terminal state with full attribution and a permanent record.
| Block | Participants | State | What can happen |
|---|---|---|---|
| Shop | Alice | business profile | Alice updates the shop |
| Order | Alice, Bob | item, status, amount | Bob requests, Alice accepts |
| Mandate | Bob, OpenClaw | limits, conditions | OpenClaw proposes a purchase |
| PayNote | Bob, Alice, Bank | secured, completed, cancelled | Bank completes only under rules |
| Delivery | Alice, Courier, Bob | delivery status | Courier confirms |
You now have a small but complete Blue world. Each block has participants, rules, state, and can reference or trigger others. That is Blue.
You can approach the same world in three ways: