Problem statement
A deck's contents currently aren't portable: there's no way to archive one, move it to another machine, or hand it to a client as a self-contained artifact.
What success looks like
A deck can be exported to a portable artifact and re-imported elsewhere, making "this is yours to keep" demonstrable rather than asserted.
Impacted repositories
Acceptance criteria
- A deck can be exported and re-imported on a different machine, preserving its contents.
Related
- Extends the existing backup capability rather than building parallel infrastructure. Open question raised alongside this: could the same mechanism be used for syncing a deck between a user's own devices? Worth a design pass, not scoped into this epic yet.
Problem statement
A deck's contents currently aren't portable: there's no way to archive one, move it to another machine, or hand it to a client as a self-contained artifact.
What success looks like
A deck can be exported to a portable artifact and re-imported elsewhere, making "this is yours to keep" demonstrable rather than asserted.
Impacted repositories
Acceptance criteria
Related