Start Building

Lesson 78: Waiver Renewal Divergence Causal Factor Register and Monthly Executive Readout in RPG Live-Ops

Lesson 77 closes individual triage rows. Executives still see a flat list of incidents unless you theme divergence into causal factors and show recurrence.

This lesson adds a divergence causal factor register: a rolling map from divergence_class and evidence to named factors, with monthly readouts that drive mitigation budgets.

Kitsune Elements illustration representing multiple recurring forces that need one named pattern

What this lesson solves

You need:

  1. A stable factor vocabulary so the same failure mode does not get five labels in five months
  2. A register that links factors to triage_row_id and replay_row_id history
  3. A monthly executive strip (one page) that shows recurrence, cost band, and lane ownership

Prerequisites: Lesson 77 triage queue; Lesson 76 replay log for divergence_class discipline.
Expected time: 85-100 minutes including one rollup dry-run.

What you will build

  1. A waiver_renewal_divergence_causal_factor_register_policy.md contract
  2. A waiver_renewal_divergence_causal_factor_register.csv append-only or versioned schema
  3. One executive_readout_template.md for the monthly summary

Step 1 - Define factor naming rules

In policy, specify:

  • when a new divergence_class becomes a new factor versus a sub-tag of an existing factor
  • who may create or merge factors (usually release ops plus one engineering lead)
  • merge rule: if two factors describe the same root cause within one quarter, merge IDs and carry forward alias_labels

Step 2 - Author the register

Suggested columns for waiver_renewal_divergence_causal_factor_register.csv:

column purpose
factor_id stable id (dcf-014)
factor_title short executive-readable name
primary_divergence_class ties to Lesson 76/77 labels
first_observed_at_utc
last_observed_at_utc updated on each qualifying triage close
recurrence_count integer; bump when a closed triage row maps here
linked_triage_row_ids semicolon list or json pointer
linked_replay_row_ids optional cross-check
dominant_severity_band sev-1, sev-2, or sev-3 from historical triage
owner_lane accountable mitigation lane
mitigation_budget_band low, medium, high policy bucket
register_status active, suppressed, retired

Step 3 - Monthly executive readout

Once per month (or per release train in high churn), produce executive_readout_template.md sections:

  • Top five factors by recurrence in the window
  • New factors created this month
  • Retired factors with reason (fixed root cause or merged)
  • Budget ask tied to mitigation_budget_band changes

Keep each factor blurb to five sentences: symptom, root theme, last incident date, owner, next gate.

Step 4 - Tie-back to promotion lineage

For each factor in the readout, cite at least one promotion_packet_id that experienced divergence in the window. This prevents the register from drifting into generic tech debt storytelling.

Common mistakes

  • Mistake: One ticket equals one factor. Fix: factors are themes; tickets are instances.
  • Mistake: Register updated only after incidents. Fix: update on triage close, not only on customer impact.
  • Mistake: Executive readout without budget bands. Fix: executives need cost language; use bands even if dollars are rough.

Mini challenge

  1. Take three closed triage_row_id rows from Lesson 77.
  2. Decide whether they map to one factor or three.
  3. Write the factor_title you would defend in a fifteen-minute review.

FAQ

How is this different from a postmortem library?

Postmortems are narrative events. The register is a recurrence index for waiver and replay divergence specifically.

Do we need tooling beyond spreadsheets?

No for small teams. Version the CSV or store rows in your ticket system with factor_id as a label.

Lesson recap

You now have a causal factor register pattern that themes divergence triage into recurring factors and feeds a monthly executive readout tied to promotion and replay lineage.

Next lesson teaser

Continue to Lesson 79: Waiver Renewal Divergence Factor Portfolio Cap per Owner Lane and Mitigation Budget in RPG Live-Ops, which limits active high-budget factors per lane per quarter with a breach protocol tied to the register.

Related learning