An open language for the agentic era
Documents agents can understand, extend, and act on.
Blue is an open language for executable documents. State, behavior, history, and authority live in the document itself — exact enough for people, organizations, and AI agents to act on, and for anyone to independently verify the result.
The graph is the application. Connected Blue documents form a shared, verifiable application — not one private backend.
Concepts
Eight ideas explain the whole model.
Read them in order — each one makes the next obvious.
Documents and Types
A Blue document is a typed graph of fields and values whose meaning stays explicit wherever it moves.
Read the concept → 02BlueId
A BlueId identifies exact meaning, so equivalent content resolves to the same semantic address.
Read the concept → 03Contracts
Behavior lives in the document: the same eligible input produces the same transition and declared events.
Read the concept → 04Timelines
Provider-backed histories carry attributed entries without pretending the world shares one database or clock.
Read the concept → 05Embedded Documents
Living documents compose inside other documents while retaining their own identity, state, and history.
Read the concept → 06Mandates
Authority is a document: bounded to a principal, target, operation, conditions, and an end.
Read the concept → 07Document Participants
People, agents, organizations, and providers are modeled by the role they play and the claims they can make.
Read the concept → 08The Graph Is the Application
Connected, bounded documents form the application without one private backend owning its meaning.
Read the concept →Executable examples
Seven lessons. One coherent path through Blue.
Each lesson is a real document processed by the real engine — and each introduces exactly one new boundary while keeping everything you've already learned. Every lesson opens its live Playground scene.
01 · Counter Basics
Alice increments, Bob decrements — one document records both authenticated operations as immutable revisions.
Learn Timelines and Operations → Lesson 0606 · Alice's Agent: Authority by Mandate
Powerless, then mandated, then revoked — and every attempt, allowed or refused, stays attributed.
Learn Mandates and revocation → Lesson 0707 · Safe Retry: One Entry, One Effect
Reject invalid input atomically, process a valid entry once, retry without duplicating state, events, or gas.
Learn admission and idempotency →Playground
Read the model. Then operate it.
The Playground is a browser lab where Blue documents actually run. Take the seat of any participant — a person or an agent — call a real Operation, or try one you're not allowed to call, and watch the actual engine produce actual revisions. Nothing is animated; everything is inspectable.
The cube is the interface
Each glass cube is one executable document.
How a session works
Every lesson is an immutable starting point. Your fork gets its own actors, Timelines, and complete history — break it, reset it, replay it, share it.
MyOS — the SaaS for Blue
Everything Blue needs to run.
MyOS is managed infrastructure for Blue: hosted Timeline infrastructure, continuous document processing, observable events, outbound webhooks, and secure API access — everything between a Blue document and a running application.
Blue defines portable meaning and deterministic behavior. MyOS supplies the managed infrastructure that keeps it running.
