Swarm Loop · Stage 1 of 8
Define Stage
Clarify the goal, constraints, and definition of done.
What the Define Stage Does
Define is where a mission becomes concrete. The swarm states the outcome it is trying to reach, the constraints it must respect, and the signals that will prove the work succeeded. Nothing is routed or executed until the mission is clear enough to act on.
Why It Matters
Most failed automation does the wrong thing efficiently. A sharp definition prevents that. When the goal, the guardrails, and the success criteria are explicit, every later stage has a fixed target to coordinate around.
Flow
Inputs and Outputs
Inputs
- A human request or trigger event
- Business context and constraints
- Relevant history retrieved from memory
- Known risks and policy limits
Outputs
- A clear mission statement
- Explicit success criteria
- Constraints and priorities
- An initial read on scope and risk
Example
What It Looks Like in Practice
A team asks the swarm to launch a new feature. Define turns that into a mission: ship the announcement, landing page, and email by Friday, stay on brand, and require human sign-off before anything goes public.
Common Failure Modes
When this stage breaks
- Vague goals that cannot be measured
- Hidden constraints that surface late
- Skipping context from past missions
- Confusing activity with the actual outcome
See It in Action
Explore an illustrative mission in the simulator, or use the readiness assessment for a directional, self-reported profile.