ADR 0097: Stash auto-assignments are tentative and never anchors
Status: superseded Date: 2026-09-25 Notes: Boundary clarification (2026-10-06, stash no-op loop fix): the insert-only/no-steal clause applies to user-CONFIRMED state only. A face holding a live accepted occurrence on another instance is the SOLE thing a stash press must never touch (whole card resolves suppressed_confirmed_elsewhere, signature-suppressed). Removed rows are unassignments, not assignments (removed != assigned): a stash revives them in place onto its shadow. Live tentative rows are movable per ADR 0102 when the OWNER presses stash: they are released (superseded) and re-homed onto the shadow. A stash press always creates or extends a shadow - the only no-op outcomes are the accepted-elsewhere suppression and the absorb-into-existing-stash resolution. persistWorkerCandidates additionally never mints a people candidate holding a face accepted on a non-target instance (mint-time guard against enqueue-time payload staleness).
Context
Spec 039 made stashed instances silent absorption targets: every future matched candidate - deliberately including weak single-face suggestions (spec 040 band) - is auto-accepted with state=accepted and every accepted occurrence becomes a worker matching anchor via the recognition export. Observed effect: stashes dilute over time (one wrong face becomes an anchor, centroid drifts, more wrong faces), distinct real persons merge into one stash, and the UI labels all stash content as Confirmed although the owner never confirmed it. The owner intent of stash is 'a real person I opt out of curating', not 'confirm everything nearby forever'.
Decision
Introduce a confirmation-axis column class_instance_occurrences.assignment_basis in (user_confirmed, auto_assigned) - deliberately NOT a new value in the state lifecycle enum, so all lifecycle paths that supersede/remove over state=accepted (disband negative signature, dissolve, merge, split) keep covering auto-assigned faces. Auto-assignments into stashed instances are recorded with assignment_basis=auto_assigned, are never labeled Confirmed, and are excluded from the worker anchor export and centroids; the stash anchor set is its user-confirmed core. They are exported in a separate tentativeAssignments payload so the worker treats them as assigned (no re-proposal churn) without anchor math. Stash decisions become insert-only (no face stealing from other instances). Unstash or naming adopts the blob, keeps basis labels visible, and marks recognition dirty. Bounded, stable recall for stashes is an accepted product trade-off. Ruling for UI provenance work: a human decision to re-home a face onto an instance of their choosing deliberately flips assignment_basis to user_confirmed - the basis describes the current assignment's provenance, not the face's history; do not treat this flip as a bug.
Consequences
Existing polluted stashes are backfilled deterministically from review-decision provenance (action=auto_accepted_stashed_target); original stash-time faces stay user_confirmed. Recall for future faces of stashed persons drops to the confirmed core's reach - accepted deliberately. Weak matches still absorb quietly into stashes (spec 039 promise preserved) but recoverable and visible as auto-assigned. New required worker payload field means API/worker deploy-order skew must be handled (worker ignores unknown fields; API guards against duplicate occurrence inserts during skew). Pre-stash DBSCAN chaining that merges distinct persons before any stash exists is NOT addressed by this decision and requires separate worker clustering work.
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