examples
A page for each kind of write-up
Each of these is a complete page — what an agent would hand its user for that kind of work — with every project, name and number in it invented. The gallery puts all eight on one page, a tab each.
These are copies rather than live pages. A leaf page is served by the session
that wrote it, and there is no session behind a static host — so the copies
come from leaf version export, which drops the comment layer
along with every script rather than leave a comment box that swallows what you
type. What the widgets drew is all here, and a control whose state the browser
owns still works: a diff's files still fold away, because that fold is a
<details>. Dragging a card takes a session, which is
one command from a checkout.
The pages
- Design decision
- Where session state should live, argued down to a recommendation. The user picks an option or writes in the box beside it, and a suggestion proposes replacement wording for a paragraph they can accept as it stands.
- Incident report
- A 94-minute queue backlog: what it cost across the top, a sequence diagram of the retry storm, and a timeline of what happened when.
- PR walkthrough
- Three files of a rate-limiting change, read in the order that explains it: the file tree, the diff, and the new code with a remark anchored at each line worth stopping on.
- Status report
- Week six of a search relaunch — the measurements that matter and the milestones behind them, with the open question stated rather than buried.
- Live progress
- A cutover rehearsal the agent republishes as each check finishes. Served live, the counts and statuses move under the reader without a refresh; this copy is the middle state.
- Triage board
- Everything open against a release, as a board the user re-triages by dragging. Each move reaches the agent as an action and holds its place on later versions.
- Release notes
- Four notes the user owns: double-click one and rewrite it, and the exact wording is what the agent gets. The visual change carries a before/after pair the reader flips between in place.
- Parallel workstreams
- Three projects side by side, a tab each holding its own status, board and decisions. Which tab is open is the reader's own view and reaches nobody.
Run one for real
From a checkout, preview.py builds the page directory the runtime
expects and serves it, which is the same path an agent session takes:
scripts/preview.py triage-boardThe page it opens takes comments. Run from an agent session, they reach it and the example gets revised like any other page; run from a bare shell, they queue in the log until an agent next reads it.