Module: Governance Onboarding
Source: Jira Epic GOV-E2 — "Convert an assessed estate to a governed one; emit a seed package." 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
A customer arrives having assessed their AI estate (via the Cost & Portfolio Sprint) but not yet governed it. This module walks the Governance Lead from that assessed starting point to a live, owned, defensible governance posture — one decision at a time. Each lesson is a single, reversible step; the sequence is deliberate: you cannot own systems you haven't registered, or baseline an estate you haven't classified.
Who this is for
Primary: Governance Lead (Product Manager persona). Also relevant to Platform Administrators and Customer Success. This is the customer's first-success journey.
Outcome
A governed AI estate: registered systems, EU AI Act classifications, attached obligations, accountable owners, a signed baseline, a readiness summary, and a launched Workspace seeded in the Command Centre.
Flow
Lessons (in sequence)
| # | Lesson (source Story) | Pts | Why it matters |
|---|---|---|---|
| 1 | GOV-110 — Start a resumable, Sprint-seeded onboarding session | 5 | Reusing Sprint results avoids re-discovering the estate and lets onboarding survive an interruption. |
| 2 | GOV-111 — Confirm organisation profile and data residency | 3 | Residency and org profile scope every downstream obligation and storage decision. |
| 3 | GOV-112 — Choose discovery methods (reuse / upload / questionnaire) | 5 | Recording HOW each system was found (discovery_source) gives provenance for every candidate. |
| 4 | GOV-113 — De-duplicate discovered systems | 5 | Duplicates and shadow AI inflate the estate and corrupt baselines if they enter the record. |
| 5 | GOV-114 — Register in-scope systems to the relational record | 8 | First-class relational rows are what every later control, obligation, and audit hangs off. |
| 6 | GOV-115 — Confirm or override EU AI Act classification | 5 | Risk classification drives which obligations apply; overrides must be defensible. |
| 7 | GOV-116 — Select frameworks and compute applicability | 5 | Rule-based applicability makes obligation coverage consistent instead of manual and error-prone. |
| 8 | GOV-117 — Assign accountable owners (RACI) | 8 | A single accountable owner per system is the backbone of governance and of Segregation of Duties. |
| 9 | GOV-118 — Compute the governance baseline | 8 | The dated, signed baseline is the anchor every future posture snapshot is compared against. |
| 10 | GOV-119 — Produce the readiness summary | 5 | A signed pillar-level RAG summary is the customer's first tangible, shareable governance artefact. |
| 11 | GOV-120 — Launch the Workspace and hand off the seed package | 5 | Launch turns the onboarding outputs into live, owned work in the Command Centre. |
How this maps (Authoritative Content Generation, §14.5 / LEARN-STD-002)
- Epic GOV-E2 → this Module.
- Each Story GOV-110…120 → a Lesson (
source_artifact: jira_story), sequenced byprerequisites. - Acceptance Criteria → learning outcomes + scenario knowledge checks — quoted, not paraphrased.
Assessment & certification
Passing all 11 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.