- A project objective
- Knowledge of which stages depend on earlier outputs
workflows guide
Choose Solo, Collaboration, or Dual
Match the orchestration topology to the dependency structure of the work.
- The topology matches real dependencies
- No box creates an unrelated version of the whole project
- Stop authority follows the selected mode
Complete the task
Use Solo when boxes can work independently
Use Collaboration when later boxes must receive one accepted handoff
Use Dual when two distinct workstreams can proceed separately and then be synthesized
Assign review authority only to the active Majesty Obmil supervisor boxes
Keep Board Chat empty until the user needs to add a shared rule or canon change
- Solo has no supervisor; only the user can stop a box
- Elapsed time alone must not stop a supervised worker