Story: Add the identity workflow and the commands that drive it
Table of Contents
This page documents a story in Sprint 27. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
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, and ores.shell drives it end to
end. The fixture and the cross-tenant engine shipped with the source
story; this story is the identity workflow and its commands.
This story was split from Exercise the workflow engine end to end when that story was reworded to the fixture it delivered and closed DONE at the sprint 26 close on 2026-10-05; the task Add the identity workflow and the commands that drive it moved here.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 27 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-05 |
3. Acceptance
- The identity workflow is a registered definition whose steps are declared by the request.
- 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 |
|---|---|---|---|---|
| Add the identity workflow and the commands that drive it | DONE | 2026-10-09 | Give the workflow component a fixture it can run against itself: an identity workflow whose steps the request declares, plus the shell commands that start it and read the engine back. |
5. Decisions
6. Out of scope
7. Result
Closed on the tasks' state, in the sprint's bookkeeping pass: every task is DONE with its work merged, and the tasks carry the outcomes.