ADR 0036: Observation Producer Authority and Instance Candidate Arbitration
Status: accepted Date: 2026-05-26
Context
ADR 0020 defines typed observation domains for generalized discovery. The next boundary question is authority: if several local workers, scripts, or future providers submit observations for the same media, domain, or class-instance candidate, Memories must have deterministic ownership and conflict semantics.
The durable rule from v1 still applies: Core API owns authoritative metadata, sharing, backup/export, and user-visible state. Producers execute analysis and submit evidence. A worker lease proves the right to complete one scheduled job; it does not make that worker authoritative for the domain.
This matters especially for class-instance identities. A producer may claim that a face is William or that a vehicle region is our Opel Astra, but the identity assignment has ownership, privacy, merge/split, contribution, and sharing consequences. That cannot be delegated to arbitrary producer code.
Decision
Core API is authoritative for accepted observations and class-instance assignments.
Observation producers are evidence sources only. They may be:
- Core-scheduled workers holding an active job lease;
- authorized local scripts or tools using an inbound observation API;
- future explicit provider integrations with privacy disclosure.
Class Occurrence Observations
For class occurrences such as robin, Bellis perennis, car, passport, or OCR text:
- Core validates producer authorization, media/input version, domain key, schema version, scope, confidence semantics, payload shape, and idempotency.
- Core stores accepted observations with producer provenance.
- Core-scheduled jobs are exclusive per leased job. Only the worker credential that owns the active lease may complete that job.
- Inbound producer submissions are independent submissions. They do not take over or complete Core-scheduled jobs.
- A domain may configure one default producer/profile for automatic Core-scheduled observations.
- Results from additional producers may coexist as provenance-bearing observations unless a domain-specific policy supersedes or rejects them.
- User-facing summaries/search must use Core-selected active observations, not producer authority.
The first inbound API slice accepts class-occurrence observations only. It does not create class-instance identities or accepted instance assignments.
To make this boundary enforceable, generic observation ingestion reserves People/face/person-like domain keys and rejects identity-bearing fields such as person record IDs, face annotation IDs, embeddings, embedding hashes, assignment IDs, candidate identity keys, or equivalent aliases. These are not ordinary class labels; they are evidence for a class-instance domain.
Class-Instance Occurrence Candidates
For class-instance domains such as People, pets, or owned vehicles:
- Producers may submit candidate evidence such as regions, embeddings, proposed instance IDs, labels, or confidence values only through a domain-specific adapter. This keeps the identity algorithm pluggable while preserving Core authority over acceptance.
- Core domain logic owns accepted assignments, merge/split, lifecycle, aliases, sharing, contribution policy, and rejection history.
- People remains the first class-instance identity domain. External producers must not directly create accepted
PersonAssignmentrows. - People worker result types such as current
class_instance_candidatewithdomainKey=peopleand historical compatibilityperson_assignment_candidateare People evidence adapters, not generic discovery domains. They may carry face regions, embeddings, clusters, proposed owner-localpersonRecordIdreferences, confidence, and provenance, but those references are candidate evidence only. Core validates ownership/lifecycle and decides whether the candidate remains tentative, is rejected/superseded, or is accepted by owner action or owner-enabled auto-approval. Fresh bundled workers must not produce newperson_assignment_candidateresults; People grouping is worker-computed from Core-leased owner snapshots and Core-governed on acceptance. - Conflicting producer evidence remains candidate/evidence until Core policy or owner action accepts, rejects, merges, or supersedes it.
Consequences
- Multiple producers can be supported without turning Memories into a plugin host.
- Worker leases remain useful for exclusive execution of Core-scheduled work but do not imply domain truth.
- The inbound observation API can be model-runtime independent: Core stores what was observed, where, taxonomy/class namespace, confidence, and provenance.
- The UI and search layers must treat producer output as Core-governed metadata, not direct truth.
- Instance identity domains remain intentionally more complex than class occurrences.
Revisit Triggers
Revisit this decision if:
- a production domain needs ensemble voting or weighted producer arbitration before storing active observations;
- a third-party producer ecosystem requires stronger producer isolation/sandboxing;
- non-People class-instance domains need shared infrastructure beyond what the People model can generalize;
- inbound producer submissions need to operate on shared media owned by another user rather than only the credential user's own owner profile.
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