change-risk-triagelisted

# Change Risk Triage — the express lane The full gated pipeline is correct for a new platform or a risky feature; it's overkill for a typo. This skill picks the lane. Owned by the `delivery-manager` (TPM); the orchestrator runs it FIRST on every build/change and applies the resulting gate matrix. Honors vibegod-principles (simplicity; never skip a SAFETY gate). User > skills > default. ## Fits in the pipeline Runs at Stage 0 (new build) and Stage 9 (change request) BEFORE committing to the full flow. The tier selects which downstream gates run vs skip. ## Score the tier (the tier = the WORST dimension) Score the change on each dimension; one high dimension promotes the whole change: - **Blast radius** — one internal user → one tenant/region → all users / a critical workflow. - **Reversibility** — instant flag-off/rollback → redeploy → hard/irreversible (data migration). - **Coupling** — does it touch billing, **authN/Z**, security, data consistency, queues, caches, or a third-party contract? - **Data / security / compliance impact**, **user-facing vs internal**, **diff size** (keep CLs ~100 lines so most work qualifies for the fast lane by construction), and **incident history** of the area. | Tier | Looks like | |---|---| | **Trivial** | copy/typo, log-level, comment, a flag-OFF code path, docs | | **Low** | small reversible CL, flag-gated, narrow blast radius, no sensitive coupling | | **Standard** | user-facing or medium blast radius, normal rollback | | **High / E