Define action/effect automation runner contract #1

Closed
opened 2026-07-09 15:04:48 +02:00 by zemion · 3 comments
Owner

Define workflow-owned action/effect execution so automation remains previewable, idempotent, policy-checked, auditable, retryable, and manually recoverable.

Source concept/wiki doc: govoplan-core/docs/ACTION_EFFECT_AUTOMATION_LAYER.md; govoplan-workflow/docs/CONCEPT.md.

Acceptance criteria:

  • ActionDefinition and EffectDefinition contracts are specified with preview, risk, reversibility, idempotency, and audit metadata.
  • Runner states cover blocked, retryable, quarantined, manual-required, and compensation-required outcomes.
  • The split condition for a future dedicated automation module is documented.

Context recovered from previous GovOPlaN planning chats and consolidated into the roadmap/docs on 2026-07-09.

Define workflow-owned action/effect execution so automation remains previewable, idempotent, policy-checked, auditable, retryable, and manually recoverable. Source concept/wiki doc: `govoplan-core/docs/ACTION_EFFECT_AUTOMATION_LAYER.md; govoplan-workflow/docs/CONCEPT.md`. Acceptance criteria: - [ ] ActionDefinition and EffectDefinition contracts are specified with preview, risk, reversibility, idempotency, and audit metadata. - [ ] Runner states cover blocked, retryable, quarantined, manual-required, and compensation-required outcomes. - [ ] The split condition for a future dedicated automation module is documented. Context recovered from previous GovOPlaN planning chats and consolidated into the roadmap/docs on 2026-07-09. <!-- govoplan-recovered-concept:5a40be5904c186e6 -->
Author
Owner

Roadmap update, 2026-07-20: general Workflow implementation is deliberately postponed while the whole-system interface pattern language and Campaign lifecycle are established. Keep this issue as canonical future scope; do not treat it as part of the current implementation wave.

Roadmap update, 2026-07-20: general Workflow implementation is deliberately postponed while the whole-system interface pattern language and Campaign lifecycle are established. Keep this issue as canonical future scope; do not treat it as part of the current implementation wave.
Author
Owner

The new Workflow graph library now distinguishes user/API/schedule/event/parent start contracts and retains governance provenance in govoplan-workflow@1ec8336. No effect execution is claimed: preview/risk/reversibility contracts, durable command outcomes, retry/quarantine/manual recovery, and compensation remain to be implemented here. Tagged P1/ready as the next runtime-security design slice.

The new Workflow graph library now distinguishes user/API/schedule/event/parent start contracts and retains governance provenance in govoplan-workflow@1ec8336. No effect execution is claimed: preview/risk/reversibility contracts, durable command outcomes, retry/quarantine/manual recovery, and compensation remain to be implemented here. Tagged P1/ready as the next runtime-security design slice.
Author
Owner

Codex State: done

The versioned action/effect automation contract is now complete in the current working tree.

  • Core exposes typed ActionDefinition, EffectDefinition, preview, observed-effect, execution-request/result, recovery-state, and runtime-checkable provider contracts.
  • The contract carries risk, reversibility, scopes/capabilities, policy checks, idempotency, audit metadata, and explicit blocked, retryable, quarantined, manual_required, and compensation_required outcomes.
  • The architecture document fixes the ownership boundary: Core owns stable DTOs; Workflow owns the first durable runner; domain modules own providers; a separate automation module is justified only when scheduling/rule/catalogue concerns outgrow Workflow.

Verification: tests.test_automation_contract (5 tests) and Ruff pass.

Implementation is complete locally and will be included in the next repository push.

## Codex State: done The versioned action/effect automation contract is now complete in the current working tree. - Core exposes typed `ActionDefinition`, `EffectDefinition`, preview, observed-effect, execution-request/result, recovery-state, and runtime-checkable provider contracts. - The contract carries risk, reversibility, scopes/capabilities, policy checks, idempotency, audit metadata, and explicit `blocked`, `retryable`, `quarantined`, `manual_required`, and `compensation_required` outcomes. - The architecture document fixes the ownership boundary: Core owns stable DTOs; Workflow owns the first durable runner; domain modules own providers; a separate automation module is justified only when scheduling/rule/catalogue concerns outgrow Workflow. Verification: `tests.test_automation_contract` (5 tests) and Ruff pass. Implementation is complete locally and will be included in the next repository push.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-workflow#1