Ultracode

Choose the lightest workflow that completes the requested outcome. Explicit invocation permits this coordination workflow, but does not expand permission for external effects or override host delegation limits.

Choose a mode

• Direct: tightly coupled or small work; normal implementation and verification.
• Thin: visible phases and optional independent workers; no durable ledger needed.
• Durable: resumability, an audit trail, or multi-agent integration needs saved state.
• Runner: a detected, trusted runner materially helps repeatable work and its actions fit existing authorization.

An Ultracode request, task category, or elapsed timer alone does not require durable artifacts. No real worker capability means Direct or Thin; never simulate multiple agents with personas.

Establish scope and capability

State the outcome, ownership, acceptance checks, useful phases, and any user-specified resource limits. Use the actual host's available spawn, message, wait, background execution, and progress tools; do not assume a tool namespace. Batch independent read operations with the available parallel call mechanism.

Check existing authorization before asking. Routine credentialed reads, required dependencies, local dev servers, or 15 minutes of authorized work do not by themselves require another permission question. Ask only about unresolved consequential choices, missing authority, or exceeding an explicit user/host limit. Prepare the concrete action first and pause only dependent work. See references/risk-and-cost-gates.md.