Decision Classes
Decision Classes, Decision Events, Delegation Chains for per-action authority tracking.
What it is
Paper Section 13.6. The use-case level (CALIBRE core assessment) authorises a class of AI application. The decision level authorises each specific consequential action within that class.
When to use
- For AI systems that make many decisions of similar type (e.g. customer-service credit-limit adjustments).
- For delegation: which human ultimately backs each class of AI decision?
- For audit: every AI decision that mattered can be traced to a Decision Class, a delegation chain, and a named human.
Walk-through
- 1Sidebar: Runtime governance > Decision classes.
- 2Create a Decision Class: initiative, class ID, description, decision owner, delegated_from, review trigger.
- 3Record a Delegation Chain entry: who delegated to whom, under what scope, for how long.
- 4Decision Events are auto-created when a Runtime Authority check references a class ID.
Common pitfalls
- Making Decision Classes too broad (e.g. 'AI credit decisions'). Narrow classes ($50-500 credit limit changes for existing customers) are more defensible.