Table of contents
- ADR 0013: Shareable, Forkable Person Identities
- Context
- Decision
- Core Concepts
- Workflows
- User curates and shares a Person
- Shared user contributes to a Person
- Rename or remove faces
- Transfer ownership
- Person owner leaves a group
- Shared user loses access
- Multiple groups and one real person
- Sharing Person vs Sharing Media Collections
- UI Implications
- Migration / Incremental Implementation
- Consequences
- Non-Goals for v1
- Revisit Triggers
ADR 0013: Shareable, Forkable Person Identities
Status: proposed Date: 2026-05-15
Context
ADR 0011 established owner-wide face recognition: Core stores embeddings and creates owner-local person assignments without worker-owned People authority. ADR 0012 then proposed collaborative group person spaces so trusted family groups could curate shared people such as Family William.
Further product clarification changes the boundary. Christian does not want family members to see multiple visible versions of the same real person depending on whether they are in a private owner view or a group view. He also wants a person curated by one user to be shareable directly with users or groups, while still preserving ownership, approval policy, and the ability for each side to keep a usable copy if sharing ends.
The user mental model is:
- “I uploaded my media and curated William.”
- “I want to share William with Rikke, grandparents, or a family group so they can contribute their William photos and help curate incorrect faces.”
- “I still own the person I created unless I transfer ownership.”
- “If collaboration ends, both sides should keep a useful William person over the contributions they are allowed to retain.”
This pushes two priorities against each other:
- Simplicity / family UX: there should appear to be one real William, not separate owner and group Williams everywhere.
- Privacy / ownership / reversibility: sharing a person must not automatically share all photos, erase media ownership, leak contributions across audiences, or make revocation destructive.
Decision
Memories will model collaborative people as shareable, ownable, forkable Person identities.
The long-term collaborative Person boundary is not “a group owns a GroupPerson.” Instead:
- A
Personidentity is created and owned by a media owner/user. - A
Personcan be shared with individual users and/or sharing groups. - Shared users/groups may contribute eligible face/media references to that Person according to the Person owner's policy.
- The Person's representative face-crop thumbnail is Person identity metadata. It is automatically visible to everyone who can see the shared Person, uses the same chosen representative source for all viewers, and updates automatically when the Person owner/admin changes the representative thumbnail.
- Person ownership/admin authority controls the identity graph and curation decisions, not the underlying media bytes.
- If sharing ends, Memories can fork the Person so each side keeps a usable copy over the contributions it is allowed to retain.
Existing owner-local PersonRecord and transitional GroupPerson concepts remain implementation stepping stones, but ADR 0013 supersedes ADR 0012 as the target long-term product model.
Core Concepts
Collaborative Person
A durable identity such as William.
Fields/concepts:
- Stable ID.
- Display name and optional aliases.
- Owner user/media-owner.
- Person admins.
- Lifecycle state:
active,archived,forked,merged,dormant. - Provenance: creation source, recognition source, naming history, ownership transfers, forks, merges.
The Person owns the curation graph: which face assignments/contributions are considered part of that identity. It does not own original media files or immutable stored bytes.
Person Share
An access/collaboration grant from a Person to an audience.
Audience may be:
- individual user;
- sharing group;
- future lightweight audience/circle.
Policy controls what the audience may do:
allow: audience members may contribute and curate within allowed action scope without per-change approval;require_person_admin_approval: contributions/changes require owner/admin approval;deny: audience may view retained shared person context but cannot contribute/curate;- per-action overrides may later distinguish add-face, remove-face, rename, merge, split, transfer ownership, and invite/share actions.
Some actions are always admin-only unless explicitly transferred/delegated:
- transfer ownership;
- archive/delete person;
- change sharing policy;
- remove or rewrite other contributors' accepted contributions beyond policy limits.
Person Contribution
A provenance-preserving link from a face/media/person assignment to a Collaborative Person.
Fields/concepts:
- Person ID.
- Face annotation / person assignment / media item reference.
- Contributing owner/user.
- Source audience/share that made the contribution possible.
- Contribution state:
suggested,pending_person_admin_approval,accepted,rejected,revoked,superseded. - Retention policy snapshot for what happens if the share/audience relationship ends.
- Provenance including model/profile/recognition confidence when ML suggested the contribution.
Person Roles
Roles are person-scoped, not only group-scoped:
person_owner: ultimate authority over the Person identity, unless ownership is transferred.person_admin: can approve contributions and manage curation according to delegated rights.contributor: can suggest or add eligible contributions according to policy.viewer: can see the Person and visible retained contributions but cannot curate.
Fork
A fork creates a new Person identity from a subset of contributions when collaboration boundaries split.
Forks are not failures. They are the privacy-preserving way to say: “we no longer share one curation graph, but both sides keep a usable person.”
Fork provenance records:
- source Person ID;
- fork reason: owner left group, share revoked, ownership transfer declined, explicit split;
- retained contribution set;
- removed contribution set;
- new owner/admin selection rule.
Workflows
User curates and shares a Person
- Christian uploads media.
- Core detects faces and stores embeddings.
- Christian names/curates a Person:
William. - Christian shares
Williamwith Rikke, a grandparent user, or a family group. - The audience can contribute their eligible William faces/media according to Christian's Person policy.
- Christian/person admins approve, reject, rename, merge, split, or remove contributions according to policy.
Shared user contributes to a Person
- Rikke has photos containing William.
- Rikke has access to Christian's shared
WilliamPerson. - Core may suggest that Rikke's accepted owner-local William faces match the shared Person.
- If Christian's Person policy is
allow, eligible contributions may be accepted automatically with provenance. - If policy requires approval, contributions remain pending until Christian/person admin approves.
- Rikke still owns her original media.
Rename or remove faces
- Renaming the shared Person changes the collaborative Person name only when the actor has person-admin authority or policy allows it.
- Removing a face contributed by another user requires person-admin authority or that user's own revoke action.
- Contributors may remove/revoke their own contributions according to retention policy.
- Owner-local media metadata is not silently rewritten unless that media owner explicitly accepts the change back into their own library.
Transfer ownership
- Person owner chooses another user as owner.
- Target user accepts ownership.
- Prior owner may remain person admin or become contributor/viewer depending on policy.
- Provenance records transfer, actor, target, and time.
Person owner leaves a group
If Christian shared William with a group and then leaves that group:
- Christian keeps his Person with his own retained contributions and any contributions he is allowed to retain outside that group.
- The group receives a forked copy containing the group's retained contributions, excluding Christian's contributions unless the leave policy explicitly keeps them visible.
- Ownership/admin of the group-retained fork is selected by:
- Christian-selected successor, if provided and eligible;
- existing person admin in the group;
- group admin;
- highest eligible contributor by accepted contribution count;
- archived/dormant if no eligible successor exists.
- Fork provenance links both Persons so future manual merge is possible if relationships change.
Shared user loses access
If Christian unshares William with Rikke:
- Christian's Person keeps Christian-retained contributions and any Rikke contributions that policy allows Christian to retain.
- Rikke receives or keeps a fork/copy over her own contributed faces/media and any retained contributions she is allowed to keep.
- Rikke becomes owner of her fork.
- Neither side loses owner-local person curation or original media.
Multiple groups and one real person
If Christian is in several groups where William appears, Christian's UI should resolve linked/fork-related Persons into one visible person when Christian has authority/visibility to understand they represent the same real person.
This resolution is viewer-local. It must not create transitive sharing between groups.
Example:
- Rikke's parents group has William photos.
- Christian's parents group has William photos.
- Christian can see both and may see one resolved
Williamin his UI. - Rikke's parents do not automatically see Christian's parents' photos unless an explicit Person Share or Shared Collection grants that visibility.
Sharing Person vs Sharing Media Collections
Sharing a Person is not the same as sharing every media item that matches that person.
Person sharing grants collaboration over the identity/curation graph and eligible contributed face/media references. Media visibility still requires explicit contribution/share grants and owner policy.
The representative Person thumbnail is the intentional exception: the selected face crop is shared as identity metadata for the Person itself. Serving that crop does not grant access to the original media item, its preview/thumbnail, surrounding image content, or unrelated metadata. Revoking Person visibility revokes access to the Person thumbnail, and a later representative-thumbnail change is automatically reflected for all currently authorized Person viewers.
For broader scenarios such as “share William vacation photos with both grandparent sides” or “share photos from this location/timeframe,” Memories should later introduce Shared Collections / Smart Shares:
- Audience: who can see/collaborate.
- Eligibility rule: person, location, timeframe, album, manual selection, or combinations.
- Curated contents: included/excluded items, cover, ordering, captions.
- Contribution policy: how owners approve matching media.
The Person identity graph can help evaluate rules like person = William, but it does not itself grant cross-audience media visibility.
UI Implications
- Users should normally see one visible
William, not separate owner/group Williams, when the system knows they represent the same real person for that viewer. - The UI may show provenance such as “Shared by Christian” or “Also contributed by Rikke's parents,” but should not expose internal records as duplicate people.
- If names conflict, resolve deterministically and transparently:
- viewer's explicit local preferred name;
- Person owner's display name;
- most recent accepted person-admin name;
- prompt the viewer/admin to choose.
- Actions that mutate shared curation should explain whether they affect only the viewer's copy, the shared Person, or a pending contribution.
Migration / Incremental Implementation
The current implementation has:
- owner-local
PersonRecords; GroupPersons and merge request bridge;OwnerFaceRecognitionService;GroupFaceRecognitionServicetransitional suggestions.
Memories is not live yet. Therefore we choose a pre-live reset rather than a compatibility-preserving migration of existing person curation.
Pre-live reset policy:
- Existing legacy owner-local
PersonRecord,PersonAssignment,GroupPerson, and group merge/link curation may be deleted/reset. - Existing uploaded media, original bytes, face detections, face thumbnails, and face embeddings should be preserved where possible because they are reproducible processing evidence and useful inputs to the new model.
- Users may need to rerun owner recognition and re-curate people after the collaborative Person foundation is introduced.
- This destructive reset is acceptable only before Memories has real live users/data expectations. After live use, future migrations must preserve/export/fork person curation instead.
Incremental path:
- Keep owner-local recognition as-is.
- Do not expand the current
GroupPersonbridge much further except for migration safety and tests. - Add collaborative Person tables behind a feature/implementation boundary:
collaborative_persons;person_shares;person_roles;person_contributions;person_forks.
- Clear pre-live legacy person curation instead of mapping existing
PersonRecord/GroupPersonrecords. - Build new curation flows on CollaborativePerson/PersonShare/PersonContribution from a clean slate.
- Build resolved-person query APIs before broad UI exposure so users do not see duplicate Williams.
- Add fork/unshare/leave workflows only after contribution provenance and retention snapshots are in place.
Consequences
- This model is more flexible and closer to user expectations than group-owned Person spaces.
- It increases data-model complexity: ownership, roles, contributions, shares, forks, and resolved views are all explicit.
- It avoids privacy surprises because identity sharing and media visibility remain separate.
- It supports future cross-group and smart-share workflows without treating groups as the only collaboration boundary.
- Current ADR 0012 remains useful as historical stepping stone but is superseded as the target model.
- The pre-live reset avoids over-engineering a migration for data that does not need preservation yet, but it must not become precedent for post-live destructive migrations.
Non-Goals for v1
- Fully automated cross-group person merging.
- Automatic sharing of all media containing a shared Person.
- Generic social-network tagging semantics.
- Cloud-based face/person graph synchronization.
- Destructive merge of media ownership or original bytes.
Revisit Triggers
Revisit if:
- Person sharing/forking is too complex for family users to understand.
- Fork behavior creates too many duplicate persons in common workflows.
- Users expect group-level people rather than person-owner-level sharing.
- Shared Collections become the dominant collaboration model and person sharing can be simplified.
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