Scoring Configuration
Dimension weights, tier thresholds, and the in-scope rule are configuration, not code. Changes are versioned, and tier migrations are previewed live before commit — no surprise re-tiering.
Dimension weights (v1 active)
Customer impact20%
Market impact20%
Financial impact20%
Operational impact20%
Reputational impact20%
Weights sum: 100%
In-scope rule: Tier 1 ⇒ resilience deep dive (Modules 5–9 unlock for the service).
Tier-migration preview
Adjust weights or thresholds to preview which services would migrate tier before committing anything.
Configuration history
v1active{"customer":0.2,"market":0.2,"financial":0.2,"operational":0.2,"reputational":0.2}T1 ≥ 3.8 · T2 ≥ 2.5Marcus Chen (Admin) · Feb 16, 2025, 02:00 PMInitial program scoring configuration (equal weights).