Get started with Blue
Choose a short route from the first Blue document to the capability or solution you need.
Blue is easiest to learn by adding one responsibility at a time. Begin with exact content. Add deterministic behavior. Then add provider-attributed actions, delegated authority, payments, and document networks only when the previous layer is clear.
Blue in 10 minutes
Understand the complete model without starting from protocol vocabulary.
Choose a routeStart from your goal
Find the best path for learning, building agents, designing a solution, or evaluating MyOS.
QuickstartProcess a document
Run one operation and inspect the entry, patch, event, gas, and resulting state.
SolutionsStart with a business problem
Explore complete patterns before choosing packages or implementation APIs.
Recommended learning sequence#
- Documents and BlueIds. Learn how exact content, types, references, and semantic identity fit together.
- Contracts and BEX. Make one state transition deterministic and inspectable.
- Requests, Responses, and Operations. Turn actions and conversations into typed messages.
- Timelines and providers. Attribute who acted and close a safe order across independent histories.
- Mandates and agents. Delegate one bounded operation, verify it at the action time, and revoke it.
- PayNotes and domain packages. Apply the lower layers to payment, Agreements, Orders, and other reusable types.
- Document networks. Connect bounded roots through requests, subscriptions, events, and exact references.
Important: You do not need to learn every layer before using Blue. A simple application can begin with Language and Contracts. Add Coordination, Mandates, and PayNotes only when the workflow crosses trust, authority, provider, or payment boundaries.
Prefer a quick result?#
Use a quickstart when you want to see the model work before reading the architecture.