Issue Index
All Issues
Complete comprehensive list of all issues.
Retry Makes the Problem Worse
A retry, repair attempt, regeneration, or follow-up instruction increases the error, expands the failure, or creates additional breakage instead of narrowing the problem.
Review Escalates Without Stop Condition
A review process keeps escalating, re-reviewing, or adding scrutiny without a declared condition for stopping.
Review Outcome Changes Unrelated Environment
A review result, approval, rejection, or classification changes state outside the environment, case, file, or workflow it was meant to govern.
Review Queue Becomes Bottleneck
A review queue, approval path, or validation stage accumulates too much work and begins blocking the workflow.
Review Rubric Missing Required Criteria
A review rubric, grading rule, evaluation checklist, or classification standard lacks criteria required to make the review reliable.
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.
Risk Score Triggers Wrong Escalation
A risk score, severity label, confidence value, or threshold result triggers the wrong escalation path.
Risk Signal Escalates Beyond Evidence
A risk signal, warning, score, or concern escalates farther than the available evidence supports.
Routing Overrides Task Intent
Routing, mode selection, agent behavior, or workflow classification sends the task down a path that overrides what the user was trying to accomplish.
Routing Path Cycles Back to Start
A routing path sends the case back to the starting point or an earlier step without resolving the condition that caused the route.
Rubric Changed but Results Did Not
A review rubric, scoring rule, evaluation standard, or classification criterion changes, but AI results continue to reflect the old rubric.
Same Case Has Conflicting Policies
The same case appears to be governed by multiple policies, rules, or standards that point to incompatible outcomes.
Same Contract Name Has Different Meanings
The same prompt, schema, field, policy, tool, or workflow contract name is used in different places with different meanings.
Same Instructions Allow Different Outputs
The same instructions are broad or underspecified enough to allow materially different outputs that all appear compliant.
Same Rule Declared in Multiple Places
The same rule, constraint, instruction, or policy appears in multiple places, creating redundancy and possible drift.
Same Workflow Check Happens Twice
The same review, validation, approval, routing, or safety check occurs more than once in the workflow without a clear reason.
Saved Memory Not Used
A saved memory, preference, instruction, or durable context item exists but does not affect the AI output when it should.
Saved Reference No Longer Works
A saved source, citation, file reference, prompt reference, or workflow pointer previously worked but no longer resolves to the expected object or meaning.
Schema Reference Loops Without Base Case
A schema, field, type, object, or structured reference points through a loop without a base case that allows validation or interpretation to resolve.
Severity Increases Without New Evidence
The severity, risk, confidence, or escalation level increases even though no new evidence has been added.
Similar Cases Route to Different Outcomes
Similar inputs, cases, prompts, or workflow states are routed to different outcomes without a declared difference that explains the split.
Single Field Carries Too Many Obligations
One field, label, score, status, or structured value is expected to carry too many meanings, decisions, or workflow obligations.
Single Step Carries Too Many Decisions
One prompt, workflow step, review stage, or agent action carries too many decisions for the system or user to evaluate cleanly.
Small Change Produces Large Downstream Effects
A small prompt, schema, policy, output, or workflow change creates unexpectedly large effects in downstream steps.