How Rutter got built
Rutter is open source for AI builds: not the code an agent wrote, but the editor's cut of how a human steered it. This recap is the first night that idea became a live product, on its own site.
The route, plotted
Hover any marker to read the direction that set it. One long night: premise, name, design, product, skills, and ship.
From premise to harbor in one night
It started as a values question, not a product brief. Open source shares the code. With agents, the durable artifact is the direction: what the human asked next, what they rejected, what they named. The first move was to prove the extract existed inside past Claude Code sessions.
I'm coming from the open source world where the code that is written is freely shared and can help others. Well with AI agents the code output isn't actually that valuable. What is valuable is how the user directed the AI agent to get to the completed project.
A design-lead pass turned the extract into something readable. Then the product question landed: cliffnotes, not a forensic dump, and a place to browse those recaps like a gallery of builds.
This is a good extraction but how can we turn this into something useful for folks that want to learn how others are building stuff? Maybe we need the "cliffnotes" version? I'm picturing an open source for AI builds website.
The first real tack was editorial, not technical. Full raw session data is too much, and it is a security problem. Ship an editor's cut. Keep images and logs on disk. Publish the flow.
I actually think shipping an editor's only summary might unlock the biggest win and solve the security issue. The value is in the flow. How did the user direct the agent. What did the user do next.
Naming came next. Passage led to rutter (a pilot's book of courses and bearings). Domain secured. Nautical language locked: Harbor, wake, headings, tacks, landmarks, manifest. Then a Cove site, a theme and plugin driven from Rutter.dc.html, and a hard data call: custom tables, not CPTs.
Let's build out the single rutter using dismissed.fyi from the command-center flow. One data pick, I think we should use custom tables instead of CPTs.
The first published recap (Dismissed.) tried polished em-dashes. That reversed the same hour. House style is short sentences and no em-dashes. The write path became two skills: /dev-rutter for the product, /rutter-sync for the editor pass. command-center flow --editor was shaped to feed that pass, not write the prose.
In the report, can we remove emdashes? Let's create two new skills: /dev-rutter and /rutter-sync <project>.
Minn Admin proved the pipeline. Then a sketched interactive chart became a first-class recap block: a plotted passage of ~7–9 waypoints the editor curates. Mature projects needed a before/after AI story, so prelude and chart.origin: joined landed. Last product beat of the night: a section of paste-ready prompts titled like "if I built this again." Then production: freighter tenant, deploy notes, live site.
I think a section that shows something like "if I were to build this or something like again I would prompt this".
What came next
Most of the product landed in one session. The follow-through was deploy, skills, and catalog.
Premise and extract Direction-over-code thesis. Forensic extract from past sessions. Design pass on the summary.
Editor-only product Cliffnotes, not raw logs. Naming hunt ends at rutter.run. Nautical theme briefed for Design.
Harbor on Cove rutter.localhost, theme + rutter-core from Rutter.dc.html, custom tables, first dismissed recap.
Pipeline and chart No em-dashes. /dev-rutter + /rutter-sync. flow --editor. Minn Admin trial. Route chart. prelude/joined. Sailing-directions prompts.
Ship rutter.run Freighter tenant, core update-db, theme deploy, skill docs for local and production.
What to borrow
The opening prompt did not ask for a website. It stated what is worth sharing (direction) and what is not (agent code). Product shape followed the value judgment.
The security and readability tack (editor-only summary) simplified everything downstream: no public raw transcripts, a recap document schema, skills for the write path.
Em-dashes shipped in the first recap and were banned the same hour. House style is cheaper when you reverse it before the catalog grows.
command-center flow --editor is deterministic fuel. The agent writes the recap. That split is why /rutter-sync stays an editor pass, not a dump-to-page button.
If you built this again
Front-loads the value judgment, editor-only security model, data shape, and extract/prose split the first night discovered in sequence.
Bundles the pipeline, chart, before/after-AI, and sailing-directions beats that arrived after the first page worked.
The ops and data lessons that only show up at first production push.
This recap is the output of an editor pass over the genesis agent transcript for Rutter itself. A deterministic extract (command-center flow --editor on session bbf4aeaf) pulled the direction spine; the narrative, landmarks captions, chart, and sailing-directions prompts were written here.
Session logs and screenshots stay on the author's machine. Only the curated recap is published. Yes: this page is a rutter about building Rutter.