Informational Fresh jira_epic: GOV-E1
Module: Foundations & Tenancy
Source: Jira Epic GOV-E1 — "Schema, migrations, roles, and user-FK ownership in place". Generated per LEARN-STD-002 from authoritative artefacts: the Epic is this module, its Stories are the lessons, and each Story's acceptance criteria are the lessons' learning outcomes and knowledge checks.
The story of this journey
Before any governance can happen, the platform needs tenant isolation, real user ownership, and enforced roles — the foundations every other module stands on.
Who this is for
Primary: Platform Administrator. Also relevant to: Software Engineer.
Flow
flowchart LR
L1[GOV-101] --> L2[GOV-102] --> L3[GOV-103]
Lessons (in sequence)
| # | Lesson (source Story) | Pts | Why it matters |
|---|---|---|---|
| 1 | GOV-101 — Create onboarding & workspace tables via idempotent migration | 5 | Idempotent, client_id-scoped migrations are the basis of safe multi-tenancy. |
| 2 | GOV-102 — Reference users by real FKs for ownership | 3 | Accountability requires ownership to point at a real, linkable user. |
| 3 | GOV-103 — Resolve and enforce workspace role | 5 | Defence-in-depth: the API blocks and the UI hides — roles must hold at every layer. |
How this maps (LEARN-STD-002)
- Epic GOV-E1 → this Module.
- Each Story → a Lesson (
source_artifact: jira_story), sequenced byprerequisites. - Acceptance Criteria → learning outcomes + scenario knowledge checks — quoted, not paraphrased.
Assessment & certification
Passing all 3 scenario knowledge checks completes the module. Certification (learner-progress store) is deferred to Phase 3; until then completion is tracked informally and no metrics are fabricated.