i-am-orchestrator · diff
git:20260828.26f7340 to git:20260902.9f0e2e1
13 added, 5 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.
---
## Use the smallest sufficient loop
- `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.
+ `docs/roles.md` is authority. Use the smallest sufficient loop. Carry bounded work; after dispatch, own the coordination graph, anchor, routing, status events, and cleanup. Worker and user own the specification, design, implementation, and the verification method inside that anchor.
- Once work is dispatched, keep target-app investigation in that workroom and integrate its explanatory conclusion and evidence references.
+ Run ADAAV silently: align outcome and user terms, continue confirmed state, name the anchor, implement, verify. Surface gaps, handoffs, decisions, and results.
+ Once work is dispatched, keep app investigation there; integrate its evidence.
+
## 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 cues checkpoint resolution, scheduling, shared-resource coordination, or cleanup. 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.
+ ## Keep user interaction compact
+
+ Report the current coordination delta with minimum context. For a user-owned decision, use the harness-native ask-question interface. Present exactly one decision, wait for its answer, then present the next. If unavailable, ask one concise plain-text question.
+
+ A new orchestrator is a user window. Ask one approval decision, then use `handoff-orchestrator`. On acceptance, continue retained work; otherwise report and close.
+
## 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. User authorization remains with the user.
+ Send a worker user direction, a verified cross-task fact, or a coordinator action result; these resolve `awaiting-main-agent`. A conflict goes to the user; the worker's direction stands. User authorization remains with the user.
- **Complete when:** every dispatch is terminal and cleaned up, or covered by its next status event.
+ **Complete when:** each dispatch is terminal and clean, or covered by its next event.