Best use
From idea to launch-ready planUse it when a rough ask needs structure before execution.
Start Here
Launch your first Mission
Launch Mission is the guided starting surface for real work. It helps you define the objective, output type, context posture, operators, and execution plan before anything runs.
Guide summary
Use this page to understand the surface before you act inside it.
Use Launch Mission and Mission Builder to turn a rough objective into a reviewed execution plan.
Guide type
Start HereThis guide reflects the current product workflow and surface ownership.
Sections
8Summary first, then steps, mistakes, and recovery notes.
Related guides
5Written against the current product structure and core execution workflow.
Main risk
Vague setupA weak objective or wrong output type usually causes weak downstream work.
Related action
Open Launch MissionUse it after Provider Vault and Operators are reasonably prepared.
Guide section
What it is
Launch Mission and Mission Builder turn a rough request into a reviewed mission or run plan.
When to use it
Use them whenever you need to start a new mission, especially if the objective, output type, or source material still need shaping.
Where to find it
Find Launch Mission from Mission Control, navigation, Mission Orb recommendations, and Blueprint entry points.
What happens next
You use this surface as part of the broader mission -> task -> run -> artifact workflow.
Common mistake
Launching with a vague objective
Related action
Review the workflow guide first if you are not yet sure how Missions, Tasks, Runs, and Artifacts connect.
Guide section
Why it matters
They reduce blank-page setup, surface missing inputs early, and make the execution path explicit before cost is incurred.
Guide section
How it fits into the workflow
This is the bridge between product setup and actual execution.
Guide section
Step-by-step usage
- Write the objective in business terms.
- Choose the output type or artifact shape.
- Attach or verify the right context.
- Confirm the operator team and plan.
- Review the launch summary before you create the mission or run.
Guide section
Inputs and outputs
Inputs needed
A clear objective
Output type
Relevant context
A suitable operator team
Provider posture if using BYOK
Outputs produced
A mission plan
Optional tasks
A launchable execution path
A clearer understanding of what is still missing
Guide section
Common mistakes
- Launching with a vague objective
- Skipping context review
- Using the wrong output type
- Treating the builder as a form to rush through
Guide section
Troubleshooting
If Launch Mission feels blocked, check provider posture, required context, and any Blueprint requirements.
Guide section
Saving and resuming
Mission Builder can preserve draft posture so you can gather context, rethink scope, or revisit the plan before launch.
What happens next
Saved drafts can be reopened and refined later.
Common mistake
Treating a draft as launched work. Nothing is running until you confirm execution.