Informational Fresh jira_story: GOV-102

Lesson 2 of 3 — Reference users by real FKs for ownership

Foundations & Tenancy · Source: Jira Story GOV-102 (3 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Anchor ownership on real user foreign keys, not free-text.

Why it matters

Accountability requires ownership to point at a real, linkable user.

Where this lives

Runs in the Customer AI Governance platform (components: platform). Adding a member resolves or creates a users row and links it by FK. Learn teaches this read-only.

Workflow

Given a member's email
When they are added
Then a users row is resolved or created and linked

Worked example

An owner is stored as the text 'Jane' with no user record. Why is that a problem?

Ownership must reference a real users row by FK so it's accountable and joinable.

Acceptance criteria (authoritative — GOV-102)

Given a member's email, when they are added, then a users row is resolved or created and linked.

Common pitfalls

Storing owner as a name string instead of a user FK.

Knowledge check

Scenario: An owner is stored as the text 'Jane' with no user record. Why is that a problem?
Look for: Ownership must reference a real users row by FK so it's accountable and joinable.

Key concepts

user FK
ownership linkage
resolve-or-create

For the AI Tutor

Summary: Anchor ownership on real user foreign keys, not free-text.
When to use: teaching or answering questions about "reference users by real fks for ownership".
When NOT to use: assigning RACI during onboarding (that is GOV-117).
Key concepts: user FK, ownership linkage, resolve-or-create.

Completion criteria

Learner passes the scenario knowledge check and can point to the system state that satisfies GOV-102's acceptance criterion.

Module: LEARN-MOD-002 (Foundations & Tenancy)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: LEARN-LSN-014