Sidecat Public-only source
The committed snapshot is generated from a temporary data directory, not from the operator live plane.
Live surfaces
Public artifacts from the Sidecat work plane.
Sidecat now publishes a small public-only snapshot of the surfaces operators and agents use locally, keeping two operator jobs distinct. A review operator uses Sidebird to review what happened — replay, evidence, receipts; an approval operator uses Sidebar to plan and approve what should happen next, with a clarified review promoted between them as a handoff, not a milestone. The first full path follows Nosh, a research librarian, through a real Zotero/Catmandu/PURL complication.
This is a static GitLab Pages snapshot, generated from a clean temporary sidecatd data directory. It does not export private local work records.
Sidebird
The generated replay surface is published as HTML.
The snapshot is created by sidebird export, using the same
server-rendered routes as local Sidebird preview, including the
operation catalog and detail pages. Recent Sidebird work also lets an
operator raise an anchored review from a live page — a question,
concern, explain, or redo carried into a durable message, without
inventing planned work.
Sidebird brief
A static export generated by the real Sidebird renderer from a temporary public-only sidecatd plane.
Sidebird board
The generated work board for the public snapshot, including the work thread story links.
Sidebird operations
The exported sidecatd operation catalog, including native git operation details.
Sidebar packet
The public Sidebar packet and operator decision artifacts generated from the same clean plane.
Sidebar
Planning and approval artifacts are published next to the replay.
The same public snapshot seeds a runtime review record, emits a Sidebar packet, submits a decision, and exports the resulting review state. A clarified Sidebird review can now be promoted into Sidebar planning context through an explicit handoff that carries its anchors and reason — a handoff, not an approval or a milestone.
Publish boundary
Public means intentionally exported.
A live local Sidecat plane can contain private operator work. Publishing Sidebird therefore needs an explicit public source, not a blind dump of whatever the daemon can see.
Sidebird body
The artifact includes the generated brief, board, operation catalog, operation detail pages, receipts, obligations, and thread story pages.
Sidebar body
The matching review packet, submitted decision, decision list, and obligations list are published as JSON.