Informational Fresh jira_story: GOV-145

Lesson 6 of 6 — Signed board pack

Executive Command Centre · Source: Jira Story GOV-145 (5 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Produce a signed, board-ready governance pack on demand.

Why it matters

Boards need a defensible, point-in-time snapshot they can trust.

Where this lives

Runs in the Customer AI Governance platform (components: command-centre). A generator renders current data into a signed PDF and records the generation event. Learn teaches this read-only.

Workflow

Given current governance data
When a board pack is generated
Then a signed PDF downloads and the generation is recorded

Worked example

A board pack is produced but nothing logs that it was generated. Why does that matter?

The generation must be recorded so the pack is attributable and defensible later.

Acceptance criteria (authoritative — GOV-145)

Given current governance data, when a board pack is generated, then a signed PDF downloads and the generation is recorded.

Common pitfalls

An unsigned or unrecorded pack, undermining defensibility.

Knowledge check

Scenario: A board pack is produced but nothing logs that it was generated. Why does that matter?
Look for: The generation must be recorded so the pack is attributable and defensible later.

Key concepts

board pack
signed PDF
generation record

For the AI Tutor

Summary: Produce a signed, board-ready governance pack on demand.
When to use: teaching or answering questions about "signed board pack".
When NOT to use: scheduled auto-emailing of the pack (that is Phase 2, GOV-222).
Key concepts: board pack, signed PDF, generation record.

Completion criteria

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

Module: LEARN-MOD-004 (Executive Command Centre)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: (module complete)