Permissions & Approvals
Problems where ownership, approval, authority, permission state, responsible control, or action rights are missing, stale, bypassed, conflicting, or unclear.
Primary Issues
- No Owner for Agent Action
An agent action can affect the system without a declared responsible owner, authority, or accountable decision path.
- Fallback Authority Is Missing
The system does not declare who or what has authority when the primary owner, rule, tool, source, or decision path is unavailable or inconclusive.
- Declared Owner Cannot Control Outcome
A person, role, system, or policy is declared responsible for an outcome but does not have the actual authority or control needed to govern it.
- Permissions Conflict After Being Combined
Permissions, approvals, roles, policies, or authority rules that seem valid separately conflict when combined in the same workflow or AI action.
- Revoked Approval Still Treated as Active
An approval, permission, exception, or authorization that was revoked continues to affect AI behavior or workflow decisions as if it were still active.
- Behavior Does Not Match Declared Role
The AI or agent behaves outside, below, or differently from the role, authority, responsibility, or permission posture declared for it.
- Model Output Triggers Unapproved Action
AI output causes, recommends, or triggers an action that has not passed the required approval, permission, or authority check.
- Action Triggered by Confidence Score
A confidence score, certainty label, risk level, or probability-like value triggers an action without enough approval, calibration, or authority control.
- Tool Can Act Without Responsible Authority
A tool, connector, function, or integration can perform an action without a declared responsible authority for that action.
- Automation Skips Required Approval
An automated AI or workflow step proceeds past an approval gate that should have been required before action.
- Agent Gets Conflicting Tool Authority
An agent receives conflicting authority signals about whether, when, or how it may use a tool, connector, function, or integration.
Also Related Issues
Showing 8 of 13 cross-listed issues.
- Workflow Step Has No Decision Owner
A workflow step requires a decision, approval, judgment, or routing choice, but no owner is declared for making it.
- Conflicting Instructions From Different Authorities
Instructions from different sources, roles, policies, prompts, tools, or workflow authorities conflict without a clear rule for which one governs.
- Human Review and Automation Disagree
A human review result and an automated AI or workflow result disagree without a declared rule for resolving the difference.
- Same Case Has Conflicting Policies
The same case appears to be governed by multiple policies, rules, or standards that point to incompatible outcomes.
- Hidden Rule Overrides Visible Instruction
A hidden, upstream, system, policy, tool, or product rule changes or overrides the visible instruction the user expects the AI to follow.
- Risk Score Triggers Wrong Escalation
A risk score, severity label, confidence value, or threshold result triggers the wrong escalation path.
- Missing Fallback for Unavailable Information
The task does not declare what the AI should do when required information, sources, tools, fields, or evidence are unavailable.
- Cannot Identify Authoritative State
The user or workflow cannot tell which state, version, review result, decision, source, or output is currently authoritative.
Ontology Metadata
- Code
CAT-0050- Version
CAT-0050@0.1.0- Ontology release
- 0.1.0
- Updated
- 2026-05-10T00:00:00Z
History
No public history entries recorded.