Split export into a complete backup and a shareable extract #16
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What to build
Two distinct exports, because backing up and sharing are different intents that a single artifact cannot serve honestly.
Complete backup stays exhaustive and round-trips with the existing archive importer. Every dimension, every
DailyMetric, everyCycleStart. A backup that silently omits data is not a backup, and the omission only surfaces at restore time — the one moment it cannot be recovered from.Shareable extract carries mood, content, and activities only. Handing a mood journal to a therapist or a friend should not also disclose a location history, cycle records, and body metrics.
A single export with checkboxes was rejected: it produces files that look like backups and are not.
Naming and UI copy carry real weight here — the two must be impossible to confuse at the point of download, because the failure mode is someone sharing the wrong one and not finding out.
This lands last deliberately, once every dimension exists, so the backup is complete on arrival rather than needing an amendment per dimension.
Acceptance criteria
DailyMetric, andCycleStartBlocked by