Guardrails
Layered safeguards — policies, technical controls and monitoring — applied at the data, model, application and infrastructure levels to keep a system operating within organizational or regulatory boundaries.
Why it matters
Guardrails shape behavior continuously. They are not a stopping mechanism, and presenting them as one is how institutions end up with no stopping mechanism.
What it is not
These are routinely confused with Guardrails. The distinctions are not pedantic — each one has consequences for how a system is governed.
Guardrails constrain how a system operates. Kill criteria determine whether it continues to operate at all.
Guardrails are applied by the operator to the system. A grant is issued by a principal and defines what the system may commit.
Relationships
Typed edges into the rest of the ontology. These are what make the canon traversable rather than merely readable.
| Verb | Target | Meaning |
|---|---|---|
constrains | Agent Identity | The subject bounds what the object may do. |
addresses | Oversight | The subject speaks to the object as a question or concern. |
Record
| Canonical identifier | QIS-TERM-00015 |
| Status | Canonical industry term |
| Adoption | Widely used |
| Domain · Layer | Oversight · Governance |
| Origin | Defined in the AIEOG Shared AI Lexicon (February 2026). |
| Semantic aliases | None recorded. |
| First published | 2026-08-02 |
| Last reviewed | 2026-08-02 · 180-day cycle |
Cite the identifier, not the URL. Identifiers are stable; URLs may change. This entry is free to read, quote and index under the dual license. Corrections to [email protected] are published.