Glossary
Plain-language definitions for the terms used throughout this documentation.
| Term | Meaning |
|---|---|
| Action Authority | The overall governed layer that decides what an agent may do, executes it through one gateway, verifies the result, and records everything. |
| Authority Engine | The decision-making component: classifies every proposed action and routes it according to your autonomy policy. |
| Action Gateway | The single execution path. No action reaches a vendor API without going through it; credentials are brokered just-in-time. |
| Proof Engine | Verifies that a "fixed" finding actually changed the underlying condition — closure requires verification, not just execution. |
| Flight Recorder | The append-only, tamper-evident evidence record of every proposal, decision, approval, execution, verification, and rollback — including decisions HALO deliberately did not act on. |
| Action class | An objective, engineering-assigned property of an action's blast radius and reversibility (Safe, Constrained, Dangerous, Forbidden). Never adjustable by a model or a policy slider. |
| Autonomy matrix | Your tenant's per-action, per-environment routing table: which action classes may run automatically, and which always queue for human approval. |
| Human-in-the-loop (HITL) | A required human approval step before an action executes. Some action classes carry a default human-review requirement even where policy would otherwise permit automatic execution. |
| Risk appetite | Your declared, versioned tolerance for accepting a known weakness versus tolerance for disruption from defensive change — compiled into concrete enforcement (patch cadence, approval thresholds, maintenance windows). |
| Tenant | A customer's isolated data and configuration boundary. Every record in the system is scoped to exactly one tenant. |
| Kill switch | An emergency stop, available per action, per tenant, or globally, that halts autonomous execution immediately. |
| Connector | An integration that reads from (and, where governed, writes to) a specific vendor product or estate source — see the connector catalog in the customer documentation tier for what's live in your tenant. |
Related docs
Unverified · owner docs-portal-steward
Was this helpful?
Optional comments unlock after a short time on this docs site.
Ask the docs
Tier-scoped answers from this portal corpus (extractive; no external LLM).
Comments
Loading comments…
Suggest an edit
Propose a correction. Staff review every suggestion and open a draft PR; nothing publishes without CI.