Table of contents
ADR 0112: Stashing a named person discards the name
Status: accepted Date: 2026-10-14
Context
Spec 039 allowed stashing only UNNAMED instances: the stash endpoint refused named ones with 400 and naming cleared stashed_at, so ADR 0107 could rely on 'a stash can only ever be an UNNAMED instance'. Owner request (2026-10-14): a NAMED person should be convertible into a stashed person from the people list. Options considered: (a) remember the display name in a side field and restore it on unstash — rejected, extra schema and lifecycle for a value the owner explicitly declared expendable; (b) keep display_name set while stashed — rejected, it breaks the stash=unnamed invariant that the ADR 0107 card-hiding rule and the shadow semantics rest on; (c) discard the name at stash time — chosen.
Decision
The stash ENDPOINT accepts named, active, people-domain instances: the same UPDATE that sets stashed_at also sets display_name = NULL, so the instance becomes an ordinary unnamed shadow and the discarded name is irreversibly gone. This keeps the invariant enforced at WRITE time instead of by rejection. The decideCandidate stash path is UNCHANGED: the default (no explicit target) arm keeps its onlyUnnamed guard byte-identical, and decisions with an explicit existingInstanceId target keep their legacy semantics — including the pre-existing quirk that a named target can gain stashed_at without its display_name being cleared (not UI-reachable; accepted residual, tracked in KNOWN_ISSUES). Unstash returns the instance to default views as an UNNAMED person; the name is not recovered (the owner renames if they want it back). Aliases are untouched by stash/unstash. Assignments do not change, so recognition is intentionally not marked dirty. The web UI must confirm the name loss before stashing.
Consequences
Users can hide a named person directly from the people grid; the person re-enters the default list after unstashing as an unnamed candidate for re-curation, which is the accepted cost of not storing the name. A stashed formerly-named person is indistinguishable from any other stashed person — no provenance marker of the discarded name exists anywhere (API, DB, or audit). The ADR 0107 hidden-cards rule is unaffected: stash targets remain unnamed, so no candidate cards surface against them. Recognition export, candidate state machine, worker, and schema are untouched: no migration, no new column, no new API field. Tests pin the named-stash success path (name NULL afterwards, listed as stashed), the unstash-as-unnamed round trip, and the unchanged decideCandidate guards.
Memories Wiki
Using Memories
- Accounts, the Library Hub, and Data Export
- Albums and Automatic Suggestions
- Explore and Discovery Domains
- The Media Viewer
- People and Faces
- Places and Map
- Plants (In Development)
- Datenschutzerklärung (Privacy Policy)
- Fast, Progressive Image Loading
- Search
- Sharing and Households
- Timeline and Photos
- Uploading and Import
Self-Hosting
- Backup and Restore
- CLI Password Reset
- Deployment Architecture
- Known Issues and Operator Diagnostics
- Map Tiles and Place Data Privacy
- Storage Layout
- Upgrades and Versioning
- Workers
Reference