git:20260924.46e74e4 to git:20261016.812dd98

- ## Use the smallest sufficient loop

-

- 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.

-

- 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.

-

- 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, Act, and Verify belong 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.

- Track each dispatch as a harness-native todo item, in progress while it runs and checked off when it turns terminal, so the user sees coordination progress.

- 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.

- Close finished work through `reporting-to-user`; a mid-flight reply -- checkpoint release, dispatch acknowledgement, answer to a user question -- follows the same rule.

- Gather every pending user-owned decision, this round's and any still open from an earlier one, and ask all of them together, each with its context, options, and a recommendation, using as many calls to the harness-native ask-question interface as its per-call question limit requires; a single-question harness lists them together in one message instead.

- A new orchestrator is a user window — ask one approval decision, then use `handoff-orchestrator`.

- ## Communicate only coordination deltas

- 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.