Quickstarts
Quickstarts
Build a small working example, inspect the complete processing trace, and then open the concept or package behind it.
Quickstarts are the fastest way to understand Blue. Each guide starts with a bounded document, performs one or more actions, and makes the evidence visible: the original Timeline Entry, actor, source channel, authority decision, processor trace, patches, emitted events, gas, epoch, and resulting BlueId.
Process your first documentOne direct operation and one deterministic state transition.→
Build a Request and Response flowAddress a provider, correlate work, and preserve exact causality.→
Delegate one operation to an agentConfirm, activate, use, revoke, and inspect a withheld attempt.→
Capture only after fulfilmentConnect commercial conditions to PayNote and provider evidence.→
Coordinate two businesses around one orderCompose two provider-backed perspectives into one reproducible result.→
What the Playground should show#
The right questions are not only “did the button work?” A Blue quickstart should let the reader answer:
- What exact document state did the action target?
- Who or what wrote the Timeline Entry?
- Which provider made that attribution?
- Which source Channel matched?
- Was authority direct or Mandate-backed?
- Why was an action accepted, withheld, or deferred?
- Which workflow ran, which patches committed, and which Root events were emitted?
- What is the resulting state BlueId?
The Playground is therefore the proof layer for the documentation, not a separate collection of demos.