Start Building

Lesson 79: Waiver Renewal Divergence Factor Portfolio Cap per Owner Lane and Mitigation Budget in RPG Live-Ops

Lesson 78 names recurring divergence factors. Without caps, every executive readout ends with “fund everything” while lanes quietly drown.

This lesson defines a portfolio cap: how many active high-budget factors each owner_lane may carry at once, what happens on breach, and how the cap ties back to factor_id rows.

Ramen Shop Isometric illustration representing a finite kitchen line that cannot serve unlimited simultaneous orders

What this lesson solves

You need:

  1. Numeric caps per lane per quarter for mitigation_budget_band = high (and optionally medium)
  2. A breach protocol that blocks new factor promotions or forces merges before new work enters
  3. A single portfolio ledger reviewers can audit beside the register

Prerequisites: Lesson 78 register columns, especially owner_lane, mitigation_budget_band, and register_status.
Expected time: 85-100 minutes including one cap table workshop.

What you will build

  1. A waiver_renewal_divergence_factor_portfolio_cap_policy.md contract
  2. A waiver_renewal_divergence_factor_portfolio_ledger.csv (or quarterly snapshot table)
  3. One breach checklist block embedded in policy (five bullets max)

Step 1 - Define budget bands and caps

In policy, map mitigation_budget_band to cap consumption:

band typical cap weight
low 0.5 cap units (example)
medium 1.0 cap units
high 2.0 cap units

Assign each lane a max active cap units per quarter (example: integration lane = 4.0 units). Tune numbers to headcount, not ambition.

Step 2 - Count active factors per lane

An factor is active when register_status = active and mitigation_budget_band is in scope for caps (often medium plus high).

Sum cap weights by owner_lane. If a factor spans lanes, policy must declare a primary_lane field in the register or split weight; avoid silent double-counting.

Step 3 - Author waiver_renewal_divergence_factor_portfolio_ledger.csv

Suggested columns:

column purpose
ledger_row_id monotonic id
quarter_label 2026-Q2 style
owner_lane
active_cap_units computed sum
cap_limit_units from policy
breach_flag yes or no
breach_ack_owner who accepted the exception or freeze
notes merges, borrow agreements, or retirements

Refresh the ledger whenever the monthly executive readout from Lesson 78 ships.

Step 4 - Breach protocol

When breach_flag = yes, default order:

  1. Freeze new high band factor activations for that lane until under cap
  2. Merge or retire factors with lowest recurrence in the window
  3. Escalate a single written exception on the promotion packet (Lesson 74) if a freeze would miss a regulator deadline

Document that order in policy so release week does not become negotiation theater.

Common mistakes

  • Mistake: Caps only on factor count, not budget band. Fix: a lane with five low factors is not the same as five high factors.
  • Mistake: Ignoring borrowed capacity. Fix: if lane A borrows B’s capacity, log a borrow_agreement_id in ledger notes.
  • Mistake: Caps without register updates. Fix: ledger rows must cite factor_id lists or hashes for audit.

Mini challenge

  1. Pick three real lanes in your org sketch.
  2. Assign cap limits and explain one lane that would breach first under stress.
  3. Write the merge rule you would use to recover without firing people.

FAQ

Do caps apply to triage rows?

Indirectly. Caps apply to active register factors. Triage should escalate into factors; raw triage volume is a symptom, not the portfolio unit.

What if every factor is legitimately high budget?

Raise cap limits in policy with executive sign-off, or drop scope elsewhere. Caps exist to force that trade visible.

Lesson recap

You now have a portfolio cap pattern that limits active high-budget divergence factors per owner lane per quarter and ties breaches to explicit freeze, merge, or exception discipline.

Next lesson teaser

Continue with Lesson 80: Cross-Lane Capacity Borrowing for a cross-lane factor capacity borrowing protocol that documents temporary cap transfers when one lane clears factors faster than another, without breaking ledger accountability.

Related learning