change-risk-evaluation

PR risk evaluation generates a structured report covering blast radius, deploy strategy, monitoring signals, and rollback triggers. It maps affected modules and importers to classify changes as internal, API-compatible, breaking, or behavioural for safe release decisions.

Rollback planning is included in a structured risk report that specifies rollback triggers and rehearsal guidance. The report outlines deployment approach, monitoring signals, and stakeholder notifications to ensure documented rollback rehearsals before merge.

Change classification categorizes modifications as internal, API-compatible, breaking, or behavioural. The evaluation maps affected modules and importers, specifying any data or infrastructure impact to ensure compliance with an 18-rule checklist.

A change management risk report includes rating, blast radius, deploy strategy, monitoring signals, rollback design, and stakeholder communication. It provides pre-merge sign-off coordination, staging validation guidance, and documented rollback rehearsals.

Blast radius analysis is needed when a planned PR change affects multiple modules or importers. It enumerates affected components, classifies the change type, and specifies data or infrastructure impact to guide safe deployment and rollback decisions.

PR risk evaluation requires no external dependencies. It references patterns in the repository and follows an 18-rule checklist to ensure completeness and compliance when producing the structured risk assessment report.