SOSA Orchestrator

The resource-aware brain that decides what runs, what waits, and what stops.

Why This Exists

Every Claude session — Cowork, Claude Code, scheduled tasks — burns through a finite token budget. Without active orchestration, a low-priority health check can eat the tokens you needed for a revenue-critical invoice run. The Orchestrator solves this by maintaining a live priority×cost matrix and making smart allocation decisions throughout the session.

It integrates tightly with the SOSA Governor (which gates individual tool calls) and the Token Efficiency Audit (which optimizes long-term patterns). The Orchestrator operates at the task level — deciding which tasks deserve tokens right now.

Core Concepts

Token Budget Hierarchy

Budgets cascade from broad to narrow. The orchestrator reads these from config/budgets.json (shared with SOSA Governor):