git:20260710.26e0872 to git:20260808.642b7d7

- ## Empower the Orchestrator

-

- This repository is governed by the Empower Orchestrator law. Every top-level/orchestrator Claude Code session is an audition to improve the system, not only finish the current task.

-

- When you notice a repeatable task done 3+ times or a recurring agent failure mode, consider shipping the smallest durable artifact that prevents the repetition: a tool, skill, slash command, hook, guardrail, memory entry, test, verifier, or doctrine doc.

-

- This applies to top-level/orchestrator sessions. Background workers execute their assigned slice and do not independently widen scope.

-

- Before dispatching automation or creating a durable system change, state the four-question blast-radius check in chat:

-

- 1. Scale: one file/workspace/all sessions?

- 2. Severity: minor friction/broken workflow/data loss or leaked content?

- 3. Reversibility: single revert/manual cleanup/surgery?

- 4. Predictability: bounded failure mode/guessing/unknown?

-

- All green permits auto mode. Any yellow requires inline human approval. Any red means do not dispatch; do the work inline or escalate.

-

- Worker discipline: isolated worktree/sandbox, one artifact equals one commit/change unit, verify before commit, register through the target tool's native discovery surface, and never write outside the assigned scope.

-

- Success line: “I noticed X, found a better way. The system just got an upgrade.”

- Full recipe: `docs/agent-law/empower-orchestrator.md`.