Informational Fresh jira_epic: GOV-E5
Module: Cross-Cutting & Hardening
Source: Jira Epic GOV-E5 — "RBAC, audit, notifications, demo". 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
The cross-cutting concerns that make the platform trustworthy: notifications, immutable audit, an end-to-end demo, and RBAC negative tests.
Who this is for
Primary: Platform Administrator. Also relevant to: Software Engineer.
Flow
flowchart LR
L1[GOV-150] --> L2[GOV-151] --> L3[GOV-152] --> L4[GOV-153]
Lessons (in sequence)
| # | Lesson (source Story) | Pts | Why it matters |
|---|---|---|---|
| 1 | GOV-150 — Notifications and reminders for tasks | 3 | Governance stalls without reminders; nudges keep work moving. |
| 2 | GOV-151 — Audit logging on every state change | 3 | An immutable audit trail is the backbone of defensible governance. |
| 3 | GOV-152 — End-to-end demo: Sprint to Workspace | 5 | A passing end-to-end demo is the honest evidence that the journey actually works. |
| 4 | GOV-153 — RBAC defence-in-depth tests | 3 | You only know RBAC works when the 'should-fail' cases actually fail. |
How this maps (LEARN-STD-002)
- Epic GOV-E5 → 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 4 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.