Informational Fresh jira_epic: GOV-E6
Module: Automated Review Cadence
Source: Jira Epic GOV-E6 — "Self-running review loop". 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
These turn the manual review loop into a self-running cadence: cycles open on time, overdue reviews escalate, and stale evidence reopens itself.
Who this is for
Primary: Product Manager. Also relevant to: Platform Administrator, Customer Success.
Flow
flowchart LR
L1[GOV-201] --> L2[GOV-202] --> L3[GOV-203]
Lessons (in sequence)
| # | Lesson (source Story) | Pts | Why it matters |
|---|---|---|---|
| 1 | GOV-201 — Scheduler auto-opens review cycles | 5 | Manual scheduling drifts; automation keeps governance current. |
| 2 | GOV-202 — Escalation and overdue board alerts | 3 | Overdue governance needs visibility at the right altitude. |
| 3 | GOV-203 — Evidence-freshness sweep reopens lapsed items | 5 | Stale evidence silently inflates posture; the sweep keeps it honest. |
How this maps (LEARN-STD-002)
- Epic GOV-E6 → 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.