WorkflowsCrew patternPlan, draft, approve
Shape a project
Turn the notes, links and half-formed plans you already have into one brief a crew can act on.
- BLUEPRINT: Roles, gates and limits are specified. No runtime runs this workflow yet. A design for agent-drafted briefs; it does not run yet.
- PREVIEW: Available to explore with limited capabilities; check the surface description Today the mission studio prepares a brief and a four-role plan in your browser, without calling a model.
The run, step by step
Steps
Who does what, in order.
Starts when: You have notes, links or a half-formed plan, and a decision it should serve.
Plan
Astra, Mission Strategy Lead
Reads what you supplied and names the decision the brief has to serve.
Make
Orion, Mission Planning Specialist
Shapes your context into one brief with goals, constraints and checks.
Your yes
Brief gate
You read the brief and approve it, edit it or send it back.
Publish
Saved to your workspace
The approved brief becomes the starting point for the next mission.
What it hands you, and what stops it
Exit proof
One approved brief tied to the context you supplied.
Kept with the run
Receipts, sources and the approval decision stay with the run.
Acceptance checks
- A gated request cannot call a model before admission.
- An interrupted request retains its run reference and cannot silently retry.
If it fails
As designed, a failed step stops the run, keeps its receipts and tells you which step to retry.