Informational Fresh jira_story: GOV-222

Lesson 3 of 6 — Scheduled auto-emailed board pack

Command Centre Enhancements · Source: Jira Story GOV-222 (3 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Deliver the board pack automatically on a cadence.

Why it matters

Sponsors shouldn't have to fetch the pack; push it on schedule.

Where this lives

Runs in the Customer AI Governance platform (components: command-centre). A scheduler generates the signed pack and emails it to the Sponsor on cadence. Learn teaches this read-only.

Workflow

Given a configured cadence
When it fires
Then a board pack is generated and emailed to the Sponsor

Worked example

The board meets monthly. How does the Sponsor get the pack?

The cadence fires monthly, generating the signed pack and emailing it automatically.

Acceptance criteria (authoritative — GOV-222)

Given a configured cadence, when it fires, then a board pack is generated and emailed to the Sponsor.

Common pitfalls

Emailing an unsigned pack or ignoring the configured cadence.

Knowledge check

Scenario: The board meets monthly. How does the Sponsor get the pack?
Look for: The cadence fires monthly, generating the signed pack and emailing it automatically.

Key concepts

scheduled delivery
auto-email
board pack cadence

For the AI Tutor

Summary: Deliver the board pack automatically on a cadence.
When to use: teaching or answering questions about "scheduled auto-emailed board pack".
When NOT to use: on-demand generation (that is GOV-145).
Key concepts: scheduled delivery, auto-email, board pack cadence.

Completion criteria

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

Module: LEARN-MOD-008 (Command Centre Enhancements)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: LEARN-LSN-042