Skip to content

Person identity: make community reputation portable with provenance #6816

Open

Description

@bokelley

Problem

Community points, badges, engagement scores, and journey/champion status describe the person, but they are currently keyed or computed through a workos_user_id. The identity layer can route linked credentials to one canonical user, but changing or splitting that canonical credential still risks moving, double-counting, or losing reputation.

Scope

  • Implement the reputation ownership and provenance rules approved in Person identity: define ownership, provenance, and lifecycle of portable state #6487.
  • Make community points and person-level badges resolve by identity_id while retaining the credential/channel/reference that produced each award.
  • Make person journey and community champion status portable across verified credentials and employer changes.
  • Keep organization-specific champion/contact authority organization-scoped and clearly named.
  • Backfill existing records with reconciliation reporting for duplicates and conflicting awards.
  • Update readers/writers, leaderboards, profile display, and journey calculations.

Invariants

  • Linking identities cannot award points twice for the same source event.
  • Unlink/split can attribute historical events using retained provenance; it does not blindly copy the total to both identities.
  • Organization roles, seats, and company-champion authority never follow the person to another organization.
  • Historical awards remain auditable after credential deletion or anonymization.

Acceptance criteria

  • A linked person sees one aggregate points/badge/journey view from every linked credential.
  • Primary-credential promotion requires no reputation-row movement.
  • Link, unlink, merge, split, replay, and concurrent-award tests show no loss or double counting.
  • Existing totals reconcile before and after migration, with exceptions reported.
  • Person-level and organization-specific uses of "champion" are separated in code and UI.
  • MemberContext hydration and prompt formatting consume the same identity-owned facts after Addie MemberContext: collapse linked identities without leaking cross-org data #6489 lands.

Out of scope

  • Organization entitlements
  • Personal billing/subscriptions
  • Employment affiliations

Activity

  1. added this to the Evergreen milestone on Aug 24, 2026
  2. added
    enhancementNew feature or request
    addieIssues related to Addie (via any channel)
    member-toolsAll member tools - profiles, dashboards, content management, working groups, events
    on Aug 24, 2026
  3. added
    claude-triagingTriage routine is actively working on this issue (1-3 min)
    on Aug 24, 2026
  4. bokelley commented on Aug 24, 2026

    @bokelley
    ContributorAuthor

    Triage

    Classification: Feature request
    Bucket(s): addie, member-tools
    Status: deferred

    Blocked-on: #6487 (ownership/provenance matrix must be committed to specs/unified-relationship-model.md first) and #6489 (MemberContext identity hydration must land) — resurfaces on both closing.


    Triaged by Claude Code. Session: https://claude.ai/code/session_01618LHerNkHiTg6kMQmXbFJ


    Generated by Claude Code

  5. added
    claude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.
    and removed
    claude-triagingTriage routine is actively working on this issue (1-3 min)
    on Aug 24, 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)claude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.enhancementNew feature or requestmember-toolsAll member tools - profiles, dashboards, content management, working groups, events

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions