Bootstrap project and safe work-item workflow
This commit is contained in:
23
delivery_backlog/stories/US06-02-archive-transfer.md
Normal file
23
delivery_backlog/stories/US06-02-archive-transfer.md
Normal file
@@ -0,0 +1,23 @@
|
||||
# US06-02 — Transfer, Verify, and Remove Active Sources
|
||||
|
||||
Epic: [E06](../E06-archive-lifecycle.md)
|
||||
|
||||
As a user, I want source files removed only after durable archive verification so
|
||||
reclaiming space cannot cause data loss.
|
||||
|
||||
## Acceptance criteria
|
||||
|
||||
- A journal records planned, transferring, verified, removing, and terminal item state.
|
||||
- Cross-filesystem flow copies to a temporary destination, closes, hashes, atomically
|
||||
publishes, records manifest, then removes the matching source.
|
||||
- Same-filesystem optimization is used only when proven safe and still verified.
|
||||
- Unexpected source/destination changes stop the item without overwrite or deletion.
|
||||
|
||||
## Automated tests
|
||||
|
||||
- Filesystem/process tests interrupt every transition before and after source removal.
|
||||
- Tests assert manifest/hash correctness, idempotent recovery, and zero verified loss.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- US06-01, US02-03
|
||||
Reference in New Issue
Block a user