Mission
Objective layerUse a mission for the outcome, not for every single subtask.
Workflow
Missions
A mission is the objective container for meaningful work. It gives the runtime something coherent to execute toward and gives you a stable place to attach tasks, context, and resulting artifacts.
Guide summary
Use this page to understand the surface before you act inside it.
Define the objective layer that connects tasks, runs, context, and artifacts.
Guide type
WorkflowThis guide reflects the current product workflow and surface ownership.
Sections
7Summary first, then steps, mistakes, and recovery notes.
Related guides
4Written against the current product structure and core execution workflow.
Main relationship
Mission -> Tasks -> Runs -> ArtifactsThat is the cleanest way to think about how work unfolds.
Related action
Start from a Blueprint when usefulBlueprints help when the work pattern repeats or the setup is complex.
Guide section
What it is
A mission defines the high-level outcome you want to achieve.
When to use it
Use it whenever the work needs a durable objective, multiple execution steps, or a result that may be improved over time.
Where to find it
Find missions in the Missions index and create them through Launch Mission or related product entry points.
What happens next
You use this surface as part of the broader mission -> task -> run -> artifact workflow.
Common mistake
Writing a mission title instead of a real objective
Related action
Use a Blueprint when the work matches an existing repeatable pattern.
Guide section
Why it matters
It keeps tasks, runs, artifacts, and context aligned around one objective instead of scattering related work across unrelated records.
Guide section
How it fits into the workflow
The mission sits above tasks and runs and below your overall product strategy.
Guide section
Step-by-step usage
- Write the objective in clear outcome language.
- Review whether context is needed before execution.
- Decide whether one task is enough or whether the work needs multiple lanes.
- Launch a run or create tasks for later execution.
- Review artifacts and replay against the original objective.
Guide section
Inputs and outputs
Inputs needed
Clear objective
Expected output type
Relevant context or blueprint if needed
Outputs produced
A durable objective anchor
Optional tasks
Future runs and artifacts linked to the same outcome
Guide section
Common mistakes
- Writing a mission title instead of a real objective
- Combining too many unrelated outcomes in one mission
- Launching without checking whether a blueprint would provide better structure
Guide section
Troubleshooting
If a mission feels chaotic, narrow the objective and split follow-on work into separate tasks or missions.