Each vertical line is a context window at one moment; its height is the tokens it held. Left to right is one loop — a call, its reply, the next call. The ribbons carry each span forward; a span's colour says which rung of the lodestone it answers to. The stable rungs run unbroken across every line; the volatile rungs change step to step. Blocks are the sibling view: filmstrip-3d shows what stands on the beach; this shows what entered a mind, from where, and what came back.
upload takes JSON, one file or several: a call log — an object or an array of them, each carrying system_prompt / user_prompt / response and its usage, which is the shape an Anthropic API log already has — or a flow document (flow: 1), which is what session-flow.py writes from a Claude Code transcript. Genus wakes and C-loop frames are recognised by their own shape. Files are read in your browser and go nowhere; and a flow document carries labels and sizes only — no tool result bodies, and secrets dropped unread — so it is safe to hand to someone in a way a raw transcript is not. ?source= also takes a path or URL, so a document served anywhere can be drawn here without uploading it at all — including beach:<block>, which reads a flow document published on a beach (beach@<origin>:<block> for another one). Add &poll=3 to any source to re-read it every few seconds and watch a session compile as it runs.
live — re-reading every few seconds, redrawing only when the document changes