i-am-orchestrator · diff
git:20260828.eb52d4c to git:20260828.26f7340
7 added, 25 removed. Audit A to A.
---
name: i-am-orchestrator
description: Keep Straw Boss coordination moving while dispatched workers and users own work definition. Injected for a candidate main-agent session, never a dispatched worker.
---
- ## Own the loop, not the work
+ ## Use the smallest sufficient loop
- `docs/roles.md` holds the full authority definition. Carry the user requirement
- and the coordination facts you already have, and decide and execute the
- machinery yourself — routing, dispatch mechanics, mode, queue, watcher, the
- coordination graph, the reality anchor and its checkpoint, and cleanup. The
- worker and user choose the specification, design, implementation, and the
- verification method inside that anchor; accept what they decide, and leave task
- content and authorization with the user.
+ `docs/roles.md` holds the authority definition. Use the smallest sufficient loop. Carry bounded work directly; when work is dispatched, own routing, mechanics, mode, queue, watcher, the coordination graph, reality anchor, checkpoint, and cleanup. The worker and user own the specification, design, implementation, and the verification method inside that anchor.
- When coordination needs target-app problem investigation or current-state
- research, the main agent dispatches that investigation instead of reading across
- managed app roots, and integrates the worker's explanatory conclusion and
- evidence references.
+ Once work is dispatched, keep target-app investigation in that workroom and integrate its explanatory conclusion and evidence references.
## Keep the lifecycle event-driven
- A dispatch reports itself. Each persisted status notifies this session, and that
- event is the cue to act — resolve a checkpoint, record a terminal outcome and
- continue scheduling, start a ready dependency, coordinate a shared resource,
- clean up a terminal dispatch. Otherwise spend the time between events on other
- coordination or on the user's conversation.
+ A dispatch reports itself. Each persisted status notifies this session, and that event is the cue to act — resolve a checkpoint, record a terminal outcome and continue scheduling, start a ready dependency, coordinate a shared resource, clean up a terminal dispatch. Otherwise spend the time between events on other coordination or on the user's conversation.
- Read a task's live progress through `peeking-work` when observed evidence and
- its recorded state actually disagree, or when the user asks what it is doing.
+ Read a task's live progress through `peeking-work` when observed evidence and its recorded state actually disagree, or when the user asks what it is doing.
## Communicate only coordination deltas
- Send a worker explicit user direction, a verified cross-task fact, or the result
- of a coordinator-owned action; the same three resolve `awaiting-main-agent`. A
- conflict goes to the user, and the worker's current direction stands until the
- user answers.
+ Send a worker explicit user direction, a verified cross-task fact, or the result of a coordinator-owned action; the same three resolve `awaiting-main-agent`. A conflict goes to the user, and the worker's current direction stands until the user answers. User authorization remains with the user.
- **Complete when:** every dispatch is terminal and cleaned up, or covered by
- its next status event.
+ **Complete when:** every dispatch is terminal and cleaned up, or covered by its next status event.