Bootstrap project and safe work-item workflow
This commit is contained in:
23
delivery_backlog/stories/US04-02-rename-journal.md
Normal file
23
delivery_backlog/stories/US04-02-rename-journal.md
Normal file
@@ -0,0 +1,23 @@
|
||||
# US04-02 — Journal Rename State and Preconditions
|
||||
|
||||
Epic: [E04](../E04-guarded-renaming.md)
|
||||
|
||||
As an operator, I want every rename transition journaled durably so interrupted work
|
||||
can be diagnosed and recovered without guessing.
|
||||
|
||||
## Acceptance criteria
|
||||
|
||||
- Plan and item state machines record preconditions, intent, attempts, outcomes,
|
||||
timestamps, fencing tokens, and verification evidence.
|
||||
- Journal writes occur before filesystem mutations and terminal transitions are
|
||||
idempotent.
|
||||
- Startup classifies incomplete transitions as resumable, rollback-safe, or manual.
|
||||
|
||||
## Automated tests
|
||||
|
||||
- State-machine tests cover all valid/invalid transitions and repeated recovery.
|
||||
- Migration/repository tests prove durable state after process restart.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- US04-01, US02-03
|
||||
Reference in New Issue
Block a user