3.6 — Module manifest extensions (declare once)
Add per-module mapping lines in the same ASCII manifest; pin all bounds/scales so knobs_hash is meaningful and replays are exact.
# Manifest snippet (illustrative)
mappings = {
AR: coverage(window=30d, tail_weight=0.5),
Revenue: { adj_ratio(b=0.02), agree(b2=0.005), realization(b3=0.05),
zeozo(c=?, Z_ref=pilot_median) },
Cash: { schedule(due=on_or_before), resid(s=?, k=?),
zeozo(c=?, Z_ref=?), syasys(rho=0.90, kappa=0.50, R=8.0) },
Cohort: { retention(window=90d), hazard(b=?), refunds(b=?), zeozo(c=?) }
}
# Note: each symbol in mappings must be pinned once and feeds the hash:
# {b, b2, b3, s, k, c, Z_ref, rho, kappa, R, ...}
# knobs_hash := sha256( ascii(canonical_json({declared knobs & mappings})) )
3.7 — Acceptance & decision triggers (portfolio-ready)
Band governance (defaults).
A++: a>=0.75
A+ : 0.50<=a<0.75
A0 : 0.25<=a<0.50
A- : 0.10<=a<0.25
A--: a<0.10
promote if delta_a >= +0.05
demote if delta_a <= -0.05
Trigger policy (examples).
Yellow: any lane drops by 1 band for 2 consecutive days -> owner RCA + note
Orange: 2+ lanes drop within the same module -> director review
Red: cross-module drop (e.g., a_agree & a_cash/a_gap) -> CFO stand-up
Scaling rule.
After ~2 weeks with benefits:
- add 2–3 more KPIs or a new slice (region/segment)
- keep the same knobs until the quarterly review
Evidence pack (keep per pilot).
- Stamped pilot CSVs + manifest (ASCII) + knobs_hash
- CI report (PASS/WARN/FAIL per check)
- 1–2 page executive brief (band movements, early warnings, actions)
Navigation
Previous: SSM-Audit – Deeper Finance Modules (3.3–3.5)
Next: Case Studies: Strategy & Generic Guidance (4.0)
Directory of Pages
SSM-Audit – Table of Contents
Frequently asked questions
SSM-Audit Q & A