Change Management Policy¶
| Field | Value |
|---|---|
| Owner | Puneet Gupta (Co-Founder) |
| Classification | Internal (shareable under NDA) |
| Version | 1.0 |
| Effective date | 2026-06-11 |
| Next review | 2027-06-11 |
1. Purpose¶
Ensure changes to applications and infrastructure are made in a controlled, reviewed, and traceable manner.
2. Application & infrastructure changes¶
- All code and configuration changes are managed through Git version control.
- Changes require a pull request with peer review and approval before merge/deploy.
- Database changes are made through versioned migrations (dbmate) with up/down scripts.
- Infrastructure is defined as version-controlled configuration (e.g. Docker Compose), so infra changes follow the same review path.
- Development and production environments are separated.
3. Traceability¶
Every change is attributable to an author and an approving reviewer through git history and PR records, providing a complete change audit trail.
4. Managed network infrastructure¶
Network infrastructure provided by the cloud provider is maintained under the provider's own change-control processes.
5. Emergency changes¶
Emergency fixes follow the same review process where feasible; where an expedited change is required, it is reviewed retrospectively and recorded.
Revision history¶
| Version | Date | Author | Change | Approved by |
|---|---|---|---|---|
| 1.0 | 2026-06-11 | Puneet Gupta | Initial draft | Puneet Gupta (Co-Founder) |