Scope, risks, and acceptance criteria first, then staged delivery
From diagnosis to route, launch, and maintenance, step by step. Nothing critical stays in verbal agreements; every stage produces an artifact and a condition to continue.
Diagnose
Regions, servers, DNS, certs, traffic, risks.
Route
Regions, CDN, storage, video, backups, monitoring.
Launch
Migration, content, key-path verification, rollback point.
Maintain
Checks, alerts, backups, updates, and scaling continue with the service.
Diagnosis report
Current state, risks, and what must be decided before routing.
Route plan
Regions, storage, delivery, backup, monitoring — with acceptance criteria.
Launch record
Migration list, key-path verification, rollback point.
Maintenance schedule
Scheduled checks, alert levels, backup status, access review.
Every change has a rollback path
Material changes keep operator, reason, and rollback on file.
Service state is traceable
Deployments, certificates, backups, and incidents all leave records.
The site keeps running after handover
Checks, backups, and recovery continue after launch.