Start Building

Lesson 98: Board-Ready Escalation Lineage Digest - Executive One-Pager From Lesson 97 Attestation Without Raw PII

Direct answer: A board-ready escalation lineage digest is the single executive artifact—usually one slide plus a one-page PDF—that translates your Lesson 97 attestation_evidence_hash bundle into director-readable outcomes: risk exposure bands, count of Lesson 95 overrides, Lesson 96 rollback SLA performance, open Lesson 94 holds, and next-quarter mitigations—with no player identifiers, ticket bodies, or regional revenue detail unless pre-cleared by legal.

Owl with coffee suggesting a late-night exec read that still deserves clarity and no confidential spill

What this lesson solves

Board packs already overflow with MAU charts. This digest answers one question: Did we govern escalations honestly this quarter, and what is still hot?

Prerequisites: A completed Lesson 97 row with a1_a4_gate_status=pass or a written exception appendix. Expected time: about seventy-five minutes including a tabletop on a director who wants “names.”

What you will build

  1. lesson78_board_ready_escalation_lineage_digest_policy.md (contract below)
  2. lesson78_board_ready_escalation_lineage_digest.csv (one row per board meeting referencing the quarter)
  3. A single-slide storyline (title + three bullets + risk band + open holds footer)

Step 1 - Define digest gate classes

gate fail signal posture
B1 – PII leak any row contains emails, player ids, or ticket excerpts block board send
B2 – Hash mismatch digest totals ≠ aggregated Lesson 92–96 CSV sums for the quarter block until finance or analytics re-runs
B3 – Narrative drift slide claims “zero overrides” but Lesson 95 CSV has rows block
B4 – Silent open hold Lesson 94 send_state=held without director footnote disclose or downgrade attestation rating

Step 2 - Author lesson78_board_ready_escalation_lineage_digest_policy.md

Minimum sections:

  1. Purpose – give the board decision-useful escalation posture without operational noise.
  2. Aggregation rules – sum overrides by reason code, not by person; report SLA as percent on-time with numerator/denominator.
  3. Risk bands – map estimated refund/chargeback exposure (ranges, not point forecasts) tied to Lesson 96 telemetry_delta_json rollups.
  4. Forward actions – three bullets max: tooling, staffing, policy edits.
  5. Redaction – run automated PII scanners plus human spot on example footers.
  6. Linkage – footnote attestation_id and manifest_sha256 from Lesson 97 so auditors can jump from slide to zip.

Step 3 - Author lesson78_board_ready_escalation_lineage_digest.csv

column purpose
digest_id stable id
board_meeting_date UTC date
quarter_label matches Lesson 97
attestation_id_ref Lesson 97 row
override_count integer
rollback_sla_hit_rate 0–1 float
open_hold_count integer
risk_band green / amber / red with rubric version
b1_b4_gate_status pass / fail
digest_evidence_hash sha256 over slide PDF + this CSV row

Step 4 - Draft the slide (35 minutes)

  1. Title – “Escalation governance: Qx 20YY” + attestation_id short code.
  2. Body – three bullets: rehearsal discipline, exception discipline, verification discipline—each with one metric.
  3. Risk band – single band with range label.
  4. Footer – open_hold_count, manifest_sha256 truncated to 12 chars, legal review initial.

Step 5 - Tabletop - director asks for “who overrode”

Response per policy: roles and counts only; identities live in sealed Lesson 95 appendix for audit committee, not the general board deck.

Pro tips

  • Pair with finance – risk dollars should use the same FX table as earnings prep.
  • Color discipline – if you use red, pair with mitigation owner to avoid panic without agency.
  • Version rubrics – if risk_band definition changes mid-quarter, footnote rubric_v2.

Troubleshooting

symptom likely cause fix
Numbers won’t tie mixed UTC quarters align quarter_label boundaries
Slide too busy copying Lesson 97 manifest keep one page; link appendix
Legal blocks slide regional revenue detail aggregate global ranges only

Common mistakes

  • Replacing the digest with a marketing narrative on player love.
  • Showing Lesson 93 copy verbatim—still PII-adjacent if it quotes support.
  • Omitting open holds because they are “almost cleared.”

FAQ

Do directors get the zip?

Usually no; audit committee chair may receive encrypted copy under separate cover.

What if attestation failed A3?

Disclose failed attestation on slide one; do not bury in appendix.

Can we use the same slide for investors?

Only after securities review; investor decks have different liability.

Lesson recap

The digest is translation, not compression. Boards need truth with proportion, not ZIP files with vibes.

Next lesson teaser

Next: Lesson 99: Annual Escalation Policy Version Bump and Migration Runbook covers semver for lesson78_* contracts, freeze windows, backfill scripts, hash recompute order, and signed migration_evidence_hash.

Related learning

Treat the board slide as earnings-grade, not all-hands cute.