Glossary

Cost governance / hard cap

Spend limits on agents and tenants, with a hard cap that blocks a run before it overspends.

category ▸ Operations

audit/verify
#101hash ✓#102hash ✓#103hash ✓#104hash ✓#105hash ✓
head 0x9f3a…c1ok: true
verifyChain ▸ chained SHA-256 · signed receipts
What it means

Cost governance / hard cap, in plain language.

Cost governance puts financial limits around AI usage so that token and tool spend cannot run away unobserved. Budgets are scoped — per agent or per tenant — over a rolling window, with an alert threshold that warns as spend approaches the limit and a hard cap that enforces it.

The difference between a soft and a hard cap is enforcement. A soft cap notifies; a hard cap blocks. For autonomous agents that can take thousands of actions a minute, a hard cap is the control that turns "we should keep an eye on cost" into "this cannot exceed its budget."

In Cortex

How Cortex implements it.

This term isn't abstract here — it maps to a real capability in the runtime. Here is exactly how Cortex enforces or relates to it.

Operations

Cortex computes spend live from actual run cost over a rolling 30-day window — no drift-prone counter — and evaluates the applicable tenant and agent policies before each run. An alert threshold flips status to alert; a hard cap blocks the run (402) when projected spend would exceed the cap.

Threshold and exceeded events are emitted so the Control Tower and the ledger can surface them — cost becomes a governed control, not a surprise on the monthly bill.

See Cost governance / hard cap enforced, not just defined.

Book a walkthrough and watch the controls in this glossary return real verdicts, seal real evidence, and trace every fact back to its source.