Layer 04 · Workflows

Workflows

The four journeys that matter, told in plain language: one path that puts data in, two paths that get value out, and one that ties traces to the code they produced. Each page shows the sequence of what happens, in order, without requiring you to read the implementation first.

The covered read/write surface

Writing: traces enter almost exclusively through the command-line tool — either by an explicit share command or automatically via hooks — and every upload schedules a background summarization. Account management (organizations, invites, keys) uses ordinary, smaller write paths that follow the same authentication and policy rules and is intentionally not diagrammed.

Reading: the web app is the primary reader — browsing the public catalog, profiles, and the trace viewer — and the conversational assistant is a second, question-answering reader built on top of the same permissions. GitHub pull requests become a third reading surface through the notes integration.

1. Share a trace — from local agent files to a durable link, and the background summary that follows.
2. Browse & view traces — from a URL to a rendered conversation, with permissions and caching.
3. Link traces to pull requests — git notes in, review-ready links out.
4. Chat with the agent — ask questions across the trace library and get a streamed, permission-checked answer.