Story: Exercise the workflow engine end to end
Table of Contents
This page documents a story in Story. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
The workflow component can be driven end to end from ores.shell, against the live fleet and with no other component's data, so the engine's start, dispatch, success, warning, failure, compensation and recovery paths are each reachable and each asserted.
2. Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent sprint | Story |
| Now | Not yet started. |
| Waiting on | Nothing. |
| Next | Break the story into tasks. |
| Last touched | 2026-09-26 |
3. Acceptance
- Every engine path is reachable from ores.shell and asserted against an expected terminal state.
- The operation surface no shell command reaches today has one: the registered definitions, starting a workflow, the instance summaries, a step result, and entity history.
- The identity workflow is a registered definition whose steps are declared by the request, so one fixture covers many workflow configurations that emulate real ones.
- Each configuration is a runnable script whose expected terminal state makes it a regression test for the engine rather than a demonstration.
- No assertion is vacuous: each one fails when the path it covers does nothing.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|