Feedback orient dispatch mode

---

name: Orient/triage automate items: headless vs interactive dispatch description: Orient planner distinguishes headless workers from interactive /spawn sessions; forge tooling work must use interactive mode type: feedback

---

When orient or triage generates automate items, they must be tagged with a dispatch mode:

• headless (claude -p worker): pure research, written proposals, design docs, single self-contained scripts, narrow bug fixes. One pass, no decisions, Justin reads output later.
• interactive (/spawn remote session): building or extending forge tooling, touching live code, anything likely to need mid-flight redirection. Verb hints: 'build', 'wire up', 'integrate', 'refactor', 'set up', 'extend'. Default to interactive when uncertain.

Why: Justin doesn't want back-and-forth forge tooling work squeezed into headless coordinator messages. New forge tooling requires real conversation, redirects, and decision-making. The cost of an unused interactive session is low; the cost of a half-baked forge change delivered as a headless doc is high.

How to apply: Any time orient or triage proposes an automate item that involves building, extending, or modifying forge tooling/code, tag it interactive and dispatch via /spawn (not claude -p). Only clearly bounded one-shot work (research, proposals, quick scripts) goes headless. Show the mode tag (🪟 vs 📄) before Justin confirms execution.

[auto-memory session e285f4ef-43b0-4d4e-a83e-67abfc85848e, confidence 0.88, mode direct]