Missions & Mission Control

The strategy leaves the deck.

A mission is a promise with machinery: an outcome, an owner, a budget, acceptance criteria, and a verification plan — compiled from your strategy, delivered by your team and governed agents.

Problem

Between “we decided” and “it shipped” lives the graveyard.

Handoffs, forgotten context, tools that don’t know why the work exists. Project management tracks the dying. Missions prevent the death.

Mechanism

Approve → compile → run.

Approve a strategy → the compiler proposes the mission graph: deliverables, dependencies, actors, budgets, gates. You review the preview — compilation is never a side effect — then Mission Control runs the graph: dispatching, watching leases and budgets, escalating blockers, routing rework, coordinating release.

Anatomy

The Mission contract.

Expandable, real from the Aster run:

Mission contract

outcome: Launch design-partner experience
metric: 10 qualified partners / 30 days
scope + non-scope: defined explicitly
deliverables: 6, each with acceptance criteria
dependencies: a graph
actors: 2 yours, 3 agent, 1 tool
budget: $80 AI capacity + $0 external
authority: L4 contract
verification plan: included
outcome measurement plan: included

Worked example

The critical path, lit.

Research → positioning → landing page; product build runs in parallel; pricing gate amber. Click a node to open its work contract.

Landing page — work contract

Outcome: Live page, claims verified
Owner: Agent (coding)
Budget: $14 AI capacity
Authority: L4

Control

Typed blockers, owned and timed.

Typed blockers (missing info · dependency · authority · budget · quality · human judgment), each with an owner and an SLA · budget envelopes warn before they stop · cancellation and supersession are states, not deletions.

UnderstandDecideDeliverVerifyLearn

Missions compile from strategy; Verify gates what they produce.

Hard question

What happens when a mission goes wrong?

Loudly, and on the record. Blockers surface with owners and next actions; failed verification creates remediation with exact findings; budget breaches pause gracefully and ask; a mission can be cancelled or superseded — and the ledger keeps what happened, because “we don’t talk about Q3” is how companies stay stupid.