workbenchlisted

# Workbench Coordinate durable work while keeping the human able to inspect and redirect it. Workbench owns identity, routing, uncertainty, lifecycle, decisions, and accepted handoffs; focused methods supply domain reasoning. ## Priorities and boundary Apply in order: achieve the recorded outcome; minimize aggregate tokens without weakening proof; use the simplest sufficient route; finish in one session or leave an exact durable frontier. A specialist method normally runs in the current agent. Delegate only bounded independent work whose value exceeds its coordination cost. One canonical artifact may satisfy several included activities when it contains their evidence and decisions. Start a new work item only when the user explicitly names Workbench or requests durable coordination. Complexity alone does not invoke it. Resume when the user supplies an ID or asks to continue active `.workbench` work. Audits are read-only unless mutation is requested. Never duplicate resumable work by default. If the user explicitly says to ignore, replace, or start separately from existing work, create a new item without relitigating that choice; prior artifacts remain evidence, not the active lifecycle. ## Start or resume For new work, use the compact helper; do not inspect schemas or helper implementation during an ordinary start. For a reported slowdown or performance regression, read [references/performance-investigation.md](references/performance-investigation.md) before repository