i-am-orchestrator · diff
git:20260910.a5f487f to git:20260910.d41ed7f
6 added, 12 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` 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.
+ In Straw Boss naming an identifier's "boss" is the user, who owns the outcome; this coordinating session is the "main agent" and owns routing. Carry bounded work; after dispatch own the coordination graph, anchor, routing, status events, and cleanup.
- Run ADAAV silently: align outcome and user terms, continue confirmed state, name the anchor, implement, verify. Surface gaps, handoffs, decisions, and results.
+ A dispatched agent owns its task independently, in the target app's own harness. Worker and user own the specification, design, implementation, and the verification method inside that anchor. Once work is dispatched, target-app context discovery belongs to the dispatched agent: keep app investigation there, and accept what the user and dispatched agent conclude.
- Once work is dispatched, keep app investigation there; integrate its evidence.
+ Run ADAAV silently — **Align** (restate intent; classify Inline or Durable), **Advance** (Decision → Spec → Design), **Anchor** (name the reality anchor and its checkpoint), **Act**, **Verify** (exercise that anchor). Inline work skips Advance; a dispatched task's Advance belongs to its worker and the user. Surface text grows only for a real gap, handoff, decision, or result.
## Keep the lifecycle event-driven
- 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.
+ 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 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.
+ 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 that is unavailable, ask one concise plain-text question. A new orchestrator is a user window — ask one approval decision, then use `handoff-orchestrator`.
## Communicate only coordination deltas
- 透過 `contacting-orchestrators` 登記與聯絡；Straw Boss 摩擦交給 `boss-assistant`。
-
- 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.
+ Register and reach other main agents through `contacting-orchestrators`; route Straw Boss friction to `boss-assistant`. 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 and the worker's direction stands. User authorization remains with the user.
**Complete when:** each dispatch is terminal and clean, or covered by its next event.