What This Looks Like
The primary authority, rule, source, tool, reviewer, or decision path is unavailable, unclear, or inconclusive, but the system does not declare what should happen next. The AI may stall, guess, escalate inconsistently, proceed without approval, or loop between options because no fallback authority is defined.
Why It Matters
Fallback authority protects workflows when the normal path fails. Without it, edge cases and unavailable inputs become control failures. The user may not know whether to stop, continue, ask someone else, use a default rule, or treat the result as unresolved.
Structural Signal
A primary authority path exists or is implied, but the structure does not define a valid authority when that path cannot decide. The issue is not that the fallback was used incorrectly; it is that the fallback authority is missing.
Common Triggers
- A workflow assumes the primary reviewer, tool, or source will always be available
- Escalation rules say to escalate but do not name the authority
- The AI is told not to decide but is not told who should decide instead
- Approval paths have no default when the approver is absent
- Policy conflicts have no declared tie-breaker
- The system treats inconclusive evidence as permission to continue
When to Use This Issue
Use this Issue when the normal decision path fails or cannot decide and the system has no declared fallback authority, escalation owner, or stop rule.
When Not to Use This Issue
Do not use this Issue when a fallback exists but the AI ignores it. Do not use it when the user simply wants a second opinion. This Issue applies when the backup authority structure itself is missing.