Guardrails and incident maturity
How KAOS is promoted from advisory to autonomous, one incident class at a time.
Stub. The maturity model and the per-incident promotion procedure belong here — this is the chapter referenced from the Agentic pricing tier.
KAOS is never granted blanket autonomy. Its authority is scoped per class of incident, and each class is promoted through three states as the playbook matures:
- Propose — KAOS describes what it would do; a human reviews and takes the action manually.
- Approve — KAOS proposes an action with the exact change prepared; a human signs off and KAOS applies it.
- Act — KAOS handles the incident end-to-end, logging the decision; a human reviews after the fact.
Promotion happens incident-class by incident-class, only after the class has been resolved enough times the same way that “same way” is a fact, not a guess.
This chapter will cover: how a class is defined, what “the same way” means in operational terms, who can promote / demote a class, and how the audit log makes promotions reversible.