automation-shape-routing

# Automation Shape Routing Choose the smallest execution shape that preserves the required evidence and control. This skill routes; it does not build or start a substrate. Ordered routing works because each rung is strictly cheaper to operate than the next: if the smallest shape truly preserves the evidence and control the task needs, every larger shape can only add coordination cost, never correctness. Named failure mode — **substrate romance**: routing to persistent workers because the topology is interesting, not because any deciding axis demands it. Anti-pattern: starting the chosen substrate as part of routing "to save a step". Corrective: return the one-line verdict and let the owner start under its own authority. ## Critical Constraints - **Route only; do not start a substrate. Why:** choosing an execution shape is a judgment step, while launching NTM, Agent Mail, or Gas City changes runtime state and requires separate operator authority. - **Prefer the smallest shape that preserves evidence. Why:** persistence and coordination add recovery and ownership costs that one-shot work cannot repay. - **Partition write scopes before choosing concurrency. Why:** a larger worker topology cannot make overlapping production writes safe. ## Route in order 1. **One deliverable?** Do it inline. Use a small in-session fresh-context fanout only when independent perspectives are the product. Do not create a reusable artifact for a one-off task. 2. **Reusable seque...