# Change Safety Example

Use the canonical change-safety certificate and pre-merge workflow for a risky
feature, migration, or config change.

## What it teaches

- behavior must stay separate from code movement
- regression hypotheses should be explored, not merely listed
- merge recommendations should stay bounded by evidence completeness

Canonical template: `.hforge/templates/reasoning/certificates/change-safety-certificate.md`