GovOPlaN/govoplan-workflow
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add reusable workflow definition graphs

Browse Source
This commit is contained in:
Albrecht Degering
2026-07-28 12:43:26 +02:00
parent 0d099b05b7
commit 85eef00913
13 changed files with 972 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@@ -4,14 +4,22 @@
**Repository type:** module (platform).
<!-- govoplan-repository-type:end -->
`govoplan-workflow` will own process orchestration for GovOPlaN.
`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.
See [docs/CONCEPT.md](docs/CONCEPT.md) for the current module concept.
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