subagent

Coordinating delegated subagents within an orchestrated workflow requires scoping execution to designated files and enforcing strict ownership boundaries. This approach returns compact, actionable results while logging detailed traces to history, ensuring deterministic outcomes without unauthorized state modifications.

Enforcing file ownership boundaries for delegated subagents involves restricting their execution scope to explicitly designated files. This prevents unauthorized modifications to shared state and ensures that all changes remain isolated until reviewed and committed by the orchestrator.

Escalation rules for a blocked subagent require routing the issue directly to the orchestrator for review. The orchestrator then evaluates the blocker and manages the commit process, preventing the subagent from altering shared git state without explicit approval.

Keeping git state under orchestrator control while running multiple subagents is achieved by preventing subagents from directly modifying shared state. The orchestrator manages session context, reviews detailed history logs, and handles all commits to maintain deterministic workflow results.

Subagents returning verbose output instead of compact telemetry lack a protocol for routing detailed traces to history. Implementing a terse telemetry approach ensures returns are compact and actionable, while comprehensive execution details are securely logged to history.