Decision: a memo is up to three files #7

Open
agent wants to merge 1 commit from m2-05-a-memo-is-three-files into main
Member

The filenames, the shared parts folder and its numbering, and which path may delete which file.

Recorded here because these are the cross-client contract: the vault's inbox processing, Android
and anything else that ever reads a Stash folder are reading these names, and the reasoning
otherwise lives only in an iOS branch.

The part most likely to be got wrong by a later client is who may delete what. The obvious
implementation — one list of "files this app wrote" — has transcript finalisation unlinking route
parts on the ordinary stop, which is data loss that only shows up after the fact.

The GPX element layout is not in here. That is a separate decision, recorded with the work that
writes the first track (Stash/stash-ios#34).

Companion to Stash/stash-ios#32.

The filenames, the shared parts folder and its numbering, and which path may delete which file. Recorded here because these are the cross-client contract: the vault's inbox processing, Android and anything else that ever reads a Stash folder are reading these names, and the reasoning otherwise lives only in an iOS branch. The part most likely to be got wrong by a later client is who may delete what. The obvious implementation — one list of "files this app wrote" — has transcript finalisation unlinking route parts on the ordinary stop, which is data loss that only shows up after the fact. The GPX element layout is **not** in here. That is a separate decision, recorded with the work that writes the first track (Stash/stash-ios#34). Companion to Stash/stash-ios#32.
The filenames, the shared parts folder and its numbering, and which path may
delete which file. Recorded here because these are the cross-client contract:
the vault's inbox processing and every other client read these names, and the
reasoning otherwise lives only in an iOS branch.

The GPX element layout is not here. That is a separate decision, recorded with
the work that writes the first track.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin m2-05-a-memo-is-three-files:m2-05-a-memo-is-three-files
git switch m2-05-a-memo-is-three-files

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff m2-05-a-memo-is-three-files
git switch m2-05-a-memo-is-three-files
git rebase main
git switch main
git merge --ff-only m2-05-a-memo-is-three-files
git switch m2-05-a-memo-is-three-files
git rebase main
git switch main
git merge --no-ff m2-05-a-memo-is-three-files
git switch main
git merge --squash m2-05-a-memo-is-three-files
git switch main
git merge --ff-only m2-05-a-memo-is-three-files
git switch main
git merge m2-05-a-memo-is-three-files
git push origin main
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Stash/stash-docs!7
No description provided.