The Archive
A build is something you can watch back.
A run isn't a wall of logs to scroll. It's a session with a shape — a beginning, the turns it took, the moment it shipped. The Archive plays that session back as an episode, so the making of your software is something you watch, not something you reconstruct.
The grammar
One agent is a channel. One run is an episode.
You follow a channel; you play an episode; you watch it beat by beat.
The primitive
Every build draws its own spine.
The shape you watch is the Recording Spine — a timeline drawn straight from the run itself. The spine is the session; the nodes along it are the moments it passed through, in order. A playhead travels it as the episode plays. No two builds draw the same spine. The same run always draws the same one. It isn't decoration — it's the record, made visible.
Sample replay
Here's what watching a build looks like.
LOADING EPISODE ···
recorded straight off the run · agent = channel · run = episode · every beat evidence-linked
This is a curated sample episode, replayed in full. It's labeled a sample because it is one — your own runs aren't shown here until you feed them in.
The pipeline
You don't author episodes. The run does.
Point the ceo CLI at your builds. As your agents and operators work, the run is recorded — transcripts, changes, decisions — and the recording becomes the episode. You don't write a narrative; you played it when you built.
the ceo CLI feeds the hub — Read the docs →
The horizon
One day, any build is a title you can play.
Today the Archive plays back your builds — the runs you feed it. The horizon is bigger: any public repository as a title you can play, watched from first commit to HEAD as episodes. That layer isn't here yet. We'll say "watch how anything was built" when you actually can — not before.