Governance
Budget governance
Per-agent limits on tool calls, tokens, time, or spend before a workflow can continue.
Budget governance constrains what an agent can consume during a run. It includes token budgets, tool-call limits, duration limits, model-cost controls, and escalation when usage exceeds agreed bands.
Why it matters
Autonomous workflows can create invisible costs unless spend and tool usage are controlled at runtime.
How HARNEXA uses it
HARNEXA includes budget checks inside the harness and reports cost, latency, and usage in CLEAR and AgentOps views.
FAQ
Questions this definition answers.
Is budget governance only a finance concern?
No. It is also a reliability and risk concern because runaway usage can indicate loops, poor retrieval, or weak task boundaries.
Where is budget governance visible?
It appears in run telemetry, CLEAR cost and efficiency dimensions, and AgentOps usage guardrails.
Need these definitions mapped to a live commerce workflow, agent estate, or protocol-readiness path?
Book diagnostic sprint