Three steps: provide a Blue document, configure who's on each channel, then run it. Real packages, real BlueIds, real diff per epoch, real gas — straight from the published Blue document processor.
How it works
Provide a doc. Paste YAML or JSON, drop a file, or pick a sample. The page computes its BlueId live.
Configure channels. For every channel the doc declares, pick whether the participant is a Human or an Agent. In this playground every channel is bound to an in-browser demo timeline.
Run it. Each operation call becomes a Conversation/Timeline Entry with the right actor and source. You can scrub through epochs, see the document state at each one, and inspect every entry.
1Provide doc
2Configure
3Run
Step 1 of 3
Provide a document
Paste a Blue document below or drag a YAML/JSON file onto the editor. We compute its BlueId live, exactly the way web.blue/blue-id-calculator does.
Predefined samples:
BlueId—
Short—
What this is not
Not a hosted runtime — your browser session is the only state.
Not a real timeline provider — no identity assurance, no completeness signal, no ordering across users.
Not a substitute for MyOS or self-hosted timelines — it is a learning surface.