Skip to content

Person identity: define ownership, provenance, and lifecycle of portable state #6487

Open

Description

@bokelley

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:

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

Out of scope

  • Personal subscription and Stripe ownership
  • Employment/consulting affiliations
  • Alumni or student product tiers

Activity

  1. added this to the Evergreen milestone on Aug 13, 2026
  2. added
    enhancementNew feature or request
    addieIssues related to Addie (via any channel)
    admin-toolInternal tools for AAO staff
    on Aug 13, 2026
  3. added
    claude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.
    on Aug 13, 2026
  4. changed the title [-]Relationship model: specify plural external identities per person[/-] [+]Person identity: define ownership, provenance, and lifecycle of portable state[/+] on Aug 24, 2026
  5. bokelley commented on Aug 24, 2026

    @bokelley
    ContributorAuthor

    Implementation draft opened as #6820.

    It adds the required ownership/provenance matrix and makes the core boundaries explicit: identity_id owns 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.

  6. added
    triage:outcome-missingclaude-triaged label is present but no visible triage outcome comment was found
    on Sep 21, 2026
  7. bokelley commented on Sep 21, 2026

    @bokelley
    ContributorAuthor

    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.

  8. removed
    triage:outcome-missingclaude-triaged label is present but no visible triage outcome comment was found
    on Sep 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    addieIssues related to Addie (via any channel)admin-toolInternal tools for AAO staffclaude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions