Architectural decision
Workflow is generic
Several domains need accepted transitions and review history.
Before · Conflated concepts
WorkflowWorkflow DefinitionWorkflow Stage
After · Explicit boundaries
Relationships
- Workflow Definition configures a submitted Workflow
- Workflow orders Workflow Stage
Problem and decision
Independent approval reducers drift in retry, audit and revision behavior.
Use a shared workflow engine with subject-owned adapters and frozen definitions.
Alternatives considered
- Implement approval independently in every feature
- Move all domain records into one workflow object
Tradeoffs and consequences
Adapters retain subject policy and integration coverage must be tracked.
Reuse transition mechanics without erasing domain ownership.
Related architecture
Related workflows
Current architectural direction; this record does not establish production release.