generated from coulomb/repo-seed
Implemented durable workflow/job foundation
This commit is contained in:
@@ -47,12 +47,13 @@ audit events.
|
||||
|
||||
## Implementation Status
|
||||
|
||||
The first foundation slice is implemented for transformation operations,
|
||||
transformation run persistence, and derived artifact lineage. See
|
||||
`docs/transformation-implementation.md`.
|
||||
The first foundation slices are implemented for transformation operations,
|
||||
transformation run persistence, derived artifact lineage, workflow templates,
|
||||
and the MVP durable job runner. See `docs/transformation-implementation.md`
|
||||
and `docs/workflow-jobs-implementation.md`.
|
||||
|
||||
Workflow templates, job runner orchestration, review gates, exception queues,
|
||||
and richer workflow audit reconstruction remain open in this workplan.
|
||||
Review gates, exception queues, and richer workflow audit reconstruction remain
|
||||
open in this workplan.
|
||||
|
||||
## O8.1 - Implement transformation operation registry
|
||||
|
||||
@@ -144,7 +145,7 @@ Implemented:
|
||||
|
||||
```task
|
||||
id: KONT-WP-0008-T004
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "2c55c5dd-f07b-466b-85a5-f229e41fd124"
|
||||
```
|
||||
@@ -159,11 +160,22 @@ Acceptance:
|
||||
- Workflow inputs can be assets, collections, queries, source events, or
|
||||
submitted payloads.
|
||||
|
||||
Implemented:
|
||||
|
||||
- `WorkflowTemplate`, `WorkflowInputDefinition`, and
|
||||
`WorkflowStepDefinition` capture reusable templates, dependencies, inputs,
|
||||
outputs, preconditions, policy checks, and failure behavior.
|
||||
- Template registration validates missing dependencies, duplicate step IDs,
|
||||
unsupported failure behavior, and dependency cycles.
|
||||
- Workflow invocations preserve asset, collection, query, source event, and
|
||||
payload input bindings; the MVP runner resolves asset bindings for
|
||||
transformation-backed steps.
|
||||
|
||||
## O8.5 - Implement job runner status retry resume and cancel behavior
|
||||
|
||||
```task
|
||||
id: KONT-WP-0008-T005
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "5f4d6c88-904d-4369-90d5-eaa4d27e3010"
|
||||
```
|
||||
@@ -177,6 +189,15 @@ Acceptance:
|
||||
- Safe retry, resume, and cancellation behavior is defined per operation.
|
||||
- Recovery actions do not require direct storage edits.
|
||||
|
||||
Implemented:
|
||||
|
||||
- `WorkflowService` can queue, invoke, resume, retry, and cancel workflow
|
||||
runs programmatically.
|
||||
- The MVP runner executes transformation-backed steps in dependency order and
|
||||
persists workflow run/step state in memory and SQLite repositories.
|
||||
- Retry creates fresh governed outputs when fixed template output IDs would
|
||||
collide with existing assets.
|
||||
|
||||
## O8.6 - Implement review gates human tasks and exception queues
|
||||
|
||||
```task
|
||||
|
||||
Reference in New Issue
Block a user