28 lines
1.3 KiB
Markdown
28 lines
1.3 KiB
Markdown
# govoplan-workflow
|
|
|
|
<!-- govoplan-repository-type:start -->
|
|
**Repository type:** module (platform).
|
|
<!-- govoplan-repository-type:end -->
|
|
|
|
`govoplan-workflow` owns process orchestration for GovOPlaN.
|
|
|
|
The module should execute configurable state machines and command handoffs
|
|
between modules without importing their implementations. It coordinates cases,
|
|
tasks, forms, files, templates, mail, appointments, payments, and records
|
|
through capabilities, events, commands, and DTOs.
|
|
|
|
The first executable slice exposes a workflow-specific node library and graph
|
|
validation API through `/workflow/node-types` and
|
|
`/workflow/definitions/validate`. It uses Core's domain-neutral definition graph
|
|
contract, but applies Workflow constraints: exactly one trigger, at least one
|
|
outcome, governed configuration fields, connected nodes, and permitted loops for
|
|
correction and retry paths. Dataflow uses the same graph contract with its own
|
|
acyclic transformation library.
|
|
|
|
See [docs/CONCEPT.md](docs/CONCEPT.md) for the complete module concept.
|
|
|
|
There is a BPMN component playing a major role here. Maybe this needs to
|
|
become a separate module. It is quite viable to think about workflow
|
|
modelling (and consequently import and export) in terms of BPMN, permitting
|
|
a standardized configuration of the system.
|