Issue Taxonomy

Summary

An issue taxonomy gives failures and ambiguities stable names. Stable names let operators filter work, services route repair, and engineers measure which conditions are recurring.

Problem

Free-form error text is useful for debugging, but it is a weak operational contract. It cannot reliably drive queues, dashboards, or remediation policy.

Principle

Use typed issue kinds for expected business ambiguity and preserve diagnostic detail as supporting context.

Platform Shape

Workflow issue contracts and services provide shared issue state. POA also exposes diagnostics taxonomy routes for current greenfield failure modes. The taxonomy is a product surface for engineers and operators, not just an internal enum.

Source Evidence

  • libs/workflow/issues
  • services/workflow/issues
  • libs/poa/diagnostics
  • docs/domains/poa-greenfield-route-map.md
  • docs/engineering/concepts/failures-are-data.md
  • docs/engineering/reference/ops-diagnostics.md