Purpose
Define how changes to Perfect Wiki production systems are proposed, reviewed, tested, deployed, and rolled back so changes do not compromise availability, security, or data integrity.
Scope
All changes to production application code, infrastructure configuration, cloud resources, third-party integrations, and customer-facing service behavior.
Policy
- All production changes are made via version control (Git). Direct, unversioned modifications to production are prohibited.
- Each change passes type checking and manual functional testing on the staging environment before promotion to production.
- Production deployments are made from versioned, immutable container images. The previous image is retained to enable rapid rollback.
- Changes with security or data-integrity implications require explicit approval by the CEO/CTO.
- Database schema changes use forward-compatible patterns (additive Firestore fields, no destructive deletions) and are tested on staging first.
- Production cloud configuration (IAM, network, storage policies) is changed via Google Cloud Console or infrastructure-as-code only by Authorized Personnel; changes are recorded in GCP audit logs.
- Emergency changes (security hotfixes, critical incident response) may bypass normal review but must be documented post-hoc within 1 business day with the same rigor.
- Changes that materially affect customer-facing behavior, security posture, or sub-processors are communicated to customers via the changelog, status page, or email as appropriate.
Rollback
If a change causes a production issue, the prior container image is redeployed and the change is reverted in version control. Data-side rollback uses the most recent backup per the BCDR plan.
Baselines & drift detection
- Production configuration baselines are captured in source control (Dockerfile, package.json, build scripts, infrastructure-as-code where used).
- Google Cloud audit logging records configuration drift on managed resources.
Roles & responsibilities
- CEO/CTO: Approves and oversees production changes.
Review cadence
Reviewed annually.
Last reviewed: 2026-05-21. Next review: 2027-05-21. Approved by: Ilia Pirozhenko, CEO/CTO.