Project, repos, instructions, prior work, constraints, capabilities, conflicts.
Agent OS · Mission Control · Issue #14
From incomplete idea to autonomous execution
One guided operator flow for defining the work, gathering evidence and references, creating and critiquing the plan, approving authority, and running safely.
Define the work
Preserve Brian's raw intent, compile live context, then lock outcomes instead of jumping from prompt to tasks.
Problem, audience, requested solution, attachments, assumptions, why now.
Goals, expected outcomes, non-goals, appetite, success signals, closeout proof.
Discover and ground
The operator approves what to learn, where to look, how much to spend, and what counts as enough.
Questions, source classes, freshness, scouts, budgets, stopping rules.
Cited findings, repo SHAs, experiments, conflicts, confidence, open gaps.
Functional, technical, product, design, asset, and anti-references.
Create the ideal plan
Turn evidence into a selected direction, testable requirements, solution design, task graph, and independent critique.
Credible alternatives, tradeoffs, cost, reversibility, recommendation.
Behavior, quality, edge cases, negative requirements, acceptance, traceability.
User flow, architecture, trust boundaries, recovery, migration, proof.
Task DAG, dependencies, owned surfaces, routing, estimates, checkpoints.
Completeness, feasibility, simplicity, UX, security, cost, proof, autonomy.
Approve autonomous authority
A versioned execution contract—not a prompt—defines exactly what Run authorizes.
Resolve evidence, coverage, authority, budget, verification, rollback, and stop-gate failures.
Simulate, run selected branches, run to checkpoint, or run all approved work.
Run, verify, and learn
Healthy work stays quiet; the operator can steer, pause, interrupt, constrain, switch, or take over throughout.
Native sessions, action trust, capability leases, receipts, checkpoints, bounded repair.
Material changes show impact and require reapproval; safe local choices remain autonomous.
Outcome proof, independent review, artifacts, cost, residual risk, routing feedback.
Runtime and model are separate choices. Every consequential effect is governed independently of the model that proposed it.