Repository navigation
Open
Labels
addieIssues related to Addie (via any channel)Issues related to Addie (via any channel)admin-toolInternal tools for AAO staffInternal tools for AAO staffclaude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.Issue has been triaged by the Claude Code triage routine. Remove to re-triage.enhancementNew feature or requestNew feature or request
Milestone
Description
Split from #3590.
Decision required
Define which data belongs to the durable person, which belongs to a sign-in credential, which is scoped to an organization, and which may be aggregated for display only while retaining source provenance.
The identity binding foundation has already shipped. This issue defines the contract required before more tables move from workos_user_id to identity_id.
Required ownership matrix
Classify at least:
- Community profile fields: slug, headline, bio, avatar, expertise, interests, social links, directory visibility, introductions/coffee-chat preferences, country, and timezone
- Credential attributes: verified emails, WorkOS names, authentication history, primary credential
- Reputation: community points, badges, engagement scores, and lifecycle/journey status
- Provenance-bound records: certifications, assessments, billing, consent, conversations, and audit events
- Organization-scoped state: memberships, roles, seats, invitations, working-group authority, organization-specific profile fields, and the exact credential/principal each grant authorizes
For every family, specify:
- canonical owner and read key
- source/provenance retained
- link and merge behavior
- unlink and disputed-identity behavior
- deletion/anonymization behavior
- whether cross-surface use requires consent under Identity privacy fence: consent and authorization rules for cross-surface linking #6491
Invariants
- Identity linkage is never an entitlement source and never substitutes one linked credential for another in organization authorization.
- Employer-managed or organization-scoped fields do not become globally portable.
- Aggregating records in a person view does not rewrite their audit provenance.
- A mistaken link can be split without silently duplicating or discarding portable state.
- "Durable" does not mean exempt from deletion or anonymization.
Acceptance criteria
- A reviewed ownership/provenance matrix is committed to
specs/unified-relationship-model.mdor its successor. - The model explicitly covers link, unlink, merge, split, deletion, and conflicting values.
- The model distinguishes community reputation from organization-specific champion/contact authority.
- Person identity storage: migrate portable profile state off canonical WorkOS user #6488, Person identity: make community reputation portable with provenance #6816, Person identity: add self-service verified recovery credentials #6817, Identity linking: isolate organization authorization to the authenticated credential #6827, Admin identity merge/split: make credential linking genuinely reversible #6490, Identity privacy fence: consent and authorization rules for cross-surface linking #6491, and Addie MemberContext: collapse linked identities without leaking cross-org data #6489 can implement against the model without making new ownership decisions.
- Security/privacy review approves the contract before identity-owned migrations land.
Out of scope
- Personal subscription and Stripe ownership
- Employment/consulting affiliations
- Alumni or student product tiers
Metadata
Metadata
Assignees
Labels
addieIssues related to Addie (via any channel)Issues related to Addie (via any channel)admin-toolInternal tools for AAO staffInternal tools for AAO staffclaude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.Issue has been triaged by the Claude Code triage routine. Remove to re-triage.enhancementNew feature or requestNew feature or request
Activity
[-]Relationship model: specify plural external identities per person[/-][+]Person identity: define ownership, provenance, and lifecycle of portable state[/+]bokelley commentedon Aug 24, 2026
Implementation draft opened as #6820.
It adds the required ownership/provenance matrix and makes the core boundaries explicit:
identity_idowns portable person state; credential linkage never unions organization entitlements; profile conflicts require explicit resolution; reputation remains partitionable from source events; and cross-surface context requires a request-specific privacy fence.This should be reviewed together with #6491 before #6488 or #6816 lands storage migrations.
bokelley commentedon Sep 21, 2026
Maintainer triage — 2026-09-21
Classification: Identity architecture decision
Status: Ready for human decision
Decision: Treat ownership, provenance, and lifecycle as the foundation for the rest of the identity roadmap.
Next gate: Security/product owners approve creation, linking, transfer, deletion, and audit invariants before schema work starts.