Missions — Overclock's 3 modes of work

A mission is the scoped space for one job: its own panes, its own status, and, optionally, its own git worktree. Two jobs on the same project never contaminate each other — each mission lives isolated, with a stable name and status visible on the side.

What changes between missions is the mode: who orchestrates and with how much autonomy. There are 3 modes — and that choice is the first decision in any job on Overclock.

Agentic mode has two internal styles: Chain — a sequential pipeline with scout, builder, and reviewer chiefs (research → build → review) — and Control Tower — an exclusive controller chief, with centralized logging and dispatch, for missions that need rigorous state tracking.

The gate is mechanical, not a promise: chief invocation only exists for the pilot's pane — no worker can call it. The chief is born on first invocation, is reused while it's alive, and its type shows up in the pane header.

Agents log the work's milestones and they become a scoreboard on the side: to do → in progress → done, with a count badge. It's your trust instrument — you see exactly what step the team is on, without asking.

Honest about scope: the scoreboard is read-only for you — the agents are the ones who create and move the milestones, during the mission. It's not your task manager; it's the telemetry of their work.