Docs · Reference
Case outcomes
When a case resolves, it is classified. The outcome describes what was discovered — code bug, config issue, environment problem, or something else. Classification is set before RESOLVED.
Proof required for all outcomes. Even IntendedBehavior and Unreproducible require verified evidence before a case can resolve. The proof gate is enforced regardless of whether code changed.
ConfirmedCodeBug
A defect in application code was identified and fixed.
ConfirmedConfigBug
A misconfiguration caused the issue.
ConfirmedDataBug
Bad or unexpected data caused the issue.
ConfirmedEnvironmentIssue
Infra, OS, or dependency environment caused the issue.
ConfirmedOperatorError
Issue was caused by an operator mistake (config, deploy, etc).
ConfirmedHardwareSetupIssue
Hardware or device-specific issue.
IntendedBehavior
The system worked as designed. No fix applied.
Duplicate
Issue was already tracked and resolved in another case.
Unreproducible
Issue could not be reproduced despite investigation.
NeedsProductDecision
Resolution requires a product or design decision outside engineering scope.
NeedsUserInput
Blocked on information from external party (user, customer, vendor).
Outcomes without a code change (
IntendedBehavior, Unreproducible, etc.) still require proof — evidence that the classification is correct.