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

Fence and reconcile workflow runtime effects

Browse Source
This commit is contained in:
zemion
2026-08-03 06:37:45 +02:00
parent a1cea1d162
commit fed8fbe6c3
10 changed files with 1669 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CONCEPT.md
+8 -2
View File
@@ -121,13 +121,19 @@ The first executable slice now provides:
- durable duration/deadline/event wait subscriptions and scale-out-safe claims
- a separate transactional platform-event consumer with bounded JSON filters
and variable mappings, idempotent delivery, and current-authority rechecks
- Core recovery-ledger operations for module actions, including canonical
request evidence, provider-dispatch checkpoints, and atomic local projection
commits
- explicit effect-confirmed/effect-absent reconciliation for unknown provider
outcomes, with blind retries disabled
- distributed execution fences for instance reconciliation, trigger delivery,
and timer resumption
- fail-closed propagation of unresolved Dataflow publication outcomes
The next execution depth should provide:
- static workflow definition registration from configuration packages
- guard hooks implemented through capability calls
- registry-driven generic module-action execution records
- action/effect previews for transitions that call other modules
- explicit blocked, retryable, quarantined, manual-required, and
compensation-required states
- dashboard summary provider