Workflows
Guided end-to-end tutorials that cross several views — from harvesting your first source to grounding your first agent fleet.
The feature guides explain one view at a time. These tutorials do the opposite: each one walks a complete, concrete scenario end to end, crossing several views on the way — because that is how the platform is actually used. Individually, harvesting, missions, context artifacts, and the terminal fleet are features; together they are operations you direct, watch, and approve.
Every tutorial follows the same shape:
- Prerequisites up front — what must be installed, configured, or understood before step 1, with links.
- Numbered steps across views — with what you should see at each step, so you always know whether you are on track.
- Costs stated where they occur — steps that spend your agent subscription say so; mechanical steps that cost nothing say that too.
- Approval gates are steps, not footnotes. Where the platform holds something for your review — a newsletter send, a mission completion, a pipeline stage — the tutorial names it as an explicit step, because the gate is part of the workflow. Where it does not hold something, the tutorial says that too.
The walks
| Tutorial | Scenario | Views crossed |
|---|---|---|
| From harvest to publish | Point the intelligence desk at a source and take one story from raw feed to published briefing — and a newsletter through the send gate | Observer → Intelligence |
| Run a mission | Turn a written goal with success conditions into a dispatched fleet you watch, steer, and complete through the gate | Missions Board → Terminals |
| Build a knowledge product | Take a thesis and a folder of raw material through the staged pipeline to an exported two-component product | Products |
| Produce a video | Install the HTML-first engine, write a brief, review each pipeline stage, and render locally | Video |
| Ground a session | Author a context artifact, attach it where sessions launch, and verify an agent starts already briefed | Context Artifacts → Terminals → Cortex |
Suggested order for a new operator
- From harvest to publish first. It runs on everyday surfaces, produces a visible result the same day, and teaches the platform's core rhythm: mechanical work is free and automatic, judgment costs tokens, and the newsletter at the end of it is drafted rather than sent — the writer never sends, so the send is yours.
- Ground a session second. Context artifacts are the habit that pays across everything else — including the mission walk that follows.
- Run a mission third, once you have watched single agents work in Terminals. It composes everything: the board, the fleet, grounding, the pause control, and the completion gate.
- Build a knowledge product and Produce a video when you need them — both are Ultra surfaces (see Tiers) with their own prerequisites.
Every walk assumes the install is done, Doctor runs green, and you have taken the quickstart tour of the sidebar.
Not a tutorial, but read before you leave one running
Two of these walks dispatch agents that keep working while you look away. Before you do that in earnest, read Autonomy & controls — how far a dispatched agent may reach, which switch stops each outward action, and what gets recorded. Scheduling that work for a moment you are not at the machine is the Calendar's job, and its page carries the walkthrough for planning a week that way.
Doctrine
The shipped operating rules — what the operating contract, the protocols, the blackboard, and the session digests each govern, and where they live on your disk.
From harvest to publish
Register a source, run a scheduled harvest, curate the pile into reports, dispatch a briefing writer, and take a newsletter through the send gate.