User Guide for Mission Control
This guide is designed for first-time operators. Follow the flow from login to onboarding, then learn how to use Missions, Outcomes, Telemetry, and the Command Bar. If you prefer exploring without setup, use Demo Mode.
Use this as your mental model. Every action should produce an outcome you can pin, export, and audit.
From first login to your first pinned outcome
Each step maps to a screen you will see in the product. Follow in order, or jump to a section that matches what you are doing now.
Choose Google or GitHub. The callback page completes the session and routes you into the console.
Create your org and first workstream, then your first mission. This establishes your active context.
- • Organization (tenant boundary)
- • Workstream (vertical / team)
- • Mission (objective + timeline)
Keep your first mission objective short and measurable. You can refine it later—what matters is creating a stable anchor for outcomes and telemetry.
Direct is for fast answers, Run is for multi-step execution, and Optimize is for solver-backed tradeoffs.
Quick response, optional outcome capture.
Step plan, tool calls, telemetry timeline.
Decision math, constraints, and scored results.
Press the shortcut to jump across missions, outcomes, and actions. Pin the commands you use most.
Outcomes are your durable artifacts: reports, plans, exports, and decisions. Pin the ones you want to reuse.
- • Title is specific and scoped
- • Summary states decision + why
- • Includes next actions
- • Exportable for stakeholders
Outcomes can be audited and traced back to runs and tool calls. This is how you make AI work reviewable.
If the backend is not connected yet, demo datasets let you explore vertical flows and outcomes instantly.
