Cases Issues Events

Summary

Workflow state is organized around cases, issues, and events. A case gives operators a durable object to inspect, issues make ambiguity visible, and events provide the audit trail that explains how the state changed.

Problem

Automation often discovers partial truth. If the system only records success or throws an exception, operators lose the middle state where review and repair are possible.

Principle

Stateful operational workflows should turn uncertainty into structured records, not hidden control flow.

Platform Shape

The shared workflow services provide case, issue, and event packages. POA uses those primitives for AP document cases, while precon keeps similar concepts in its domain-native opportunity tables. Both patterns preserve the same posture: operator state is OLTP-backed, replayable, and auditable.

Source Evidence

• docs/domains/poa.md
• services/workflow/cases
• services/workflow/issues
• services/workflow/events

Related Reading

• docs/engineering/concepts/failures-are-data.md
• docs/engineering/concepts/services-expose-capabilities.md