[Feature] Add scoped Workflow templates, reuse, and governed start triggers #6

Open
opened 2026-07-28 14:03:00 +02:00 by zemion · 1 comment
Owner

Parent: #5

Apply the same governed definition and trigger model to Workflow while preserving Workflow-owned runtime and effect semantics.

Acceptance criteria:

  • definitions support system/tenant/group/user scope, flow/template kind, inheritance, reuse, and start grants
  • templates are reusable graph definitions but cannot be activated or started
  • derivation pins source revision/hash and exposes complete Policy provenance; ancestor changes require explicit review
  • start origins distinguish user, API, schedule, event, parent workflow, dependency, retry/replay, and backfill
  • scheduled/event triggers cannot start until an active runtime revision and current automation principal are available
  • inherited definitions are read-only unless derived into an editable local definition
  • runtime permission guards, action effects, correlation/causation, audit, and manual recovery remain owned by Workflow
  • module actions and nested workflows use versioned capabilities, never optional implementation imports
Parent: https://git.add-ideas.de/GovOPlaN/govoplan-workflow/issues/5 Apply the same governed definition and trigger model to Workflow while preserving Workflow-owned runtime and effect semantics. Acceptance criteria: - definitions support system/tenant/group/user scope, flow/template kind, inheritance, reuse, and start grants - templates are reusable graph definitions but cannot be activated or started - derivation pins source revision/hash and exposes complete Policy provenance; ancestor changes require explicit review - start origins distinguish user, API, schedule, event, parent workflow, dependency, retry/replay, and backfill - scheduled/event triggers cannot start until an active runtime revision and current automation principal are available - inherited definitions are read-only unless derived into an editable local definition - runtime permission guards, action effects, correlation/causation, audit, and manual recovery remain owned by Workflow - module actions and nested workflows use versioned capabilities, never optional implementation imports
Author
Owner

Governed definition slice implemented in govoplan-core@26ae034, govoplan-policy@d6e09fb, and govoplan-workflow@1ec8336.

Completed:

  • system/tenant/group/user scope and flow/template kind
  • reusable templates that cannot activate/start
  • pinned derivation with source revision/hash, node-library version, actor, Policy decision, and transitive ancestor limits
  • inherited read-only editor behavior and explainable provenance
  • user, API, schedule, event, and parent/dependency start-node contracts
  • UI explicitly reports that automatic instance dispatch is unavailable rather than implying execution

Remaining before closure:

  • Workflow instance runtime and durable start dispatch under govoplan-workflow#5
  • effect runner, retries/manual recovery/compensation under govoplan-workflow#1
  • current automation-principal and durable event integration before enabling scheduled/event starts

Verification: 13 Workflow tests, WebUI typecheck, migrations, and consolidated focused suite pass.

Governed definition slice implemented in govoplan-core@26ae034, govoplan-policy@d6e09fb, and govoplan-workflow@1ec8336. Completed: - system/tenant/group/user scope and flow/template kind - reusable templates that cannot activate/start - pinned derivation with source revision/hash, node-library version, actor, Policy decision, and transitive ancestor limits - inherited read-only editor behavior and explainable provenance - user, API, schedule, event, and parent/dependency start-node contracts - UI explicitly reports that automatic instance dispatch is unavailable rather than implying execution Remaining before closure: - Workflow instance runtime and durable start dispatch under govoplan-workflow#5 - effect runner, retries/manual recovery/compensation under govoplan-workflow#1 - current automation-principal and durable event integration before enabling scheduled/event starts Verification: 13 Workflow tests, WebUI typecheck, migrations, and consolidated focused suite pass.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-workflow#6
No description provided.