Handover checklist
The Four Handover Pillars
Section titled “The Four Handover Pillars”flowchart TD A[Operational Handover] --> B[1. Code & Manifest Repositories] A --> C[2. Infrastructure & Cloud Resources] A --> D[3. Secrets, Keys & Access Rotation] A --> E[4. Knowledge Transfer & Runbooks]1. Code & Manifest Repositories
Section titled “1. Code & Manifest Repositories”- Repository Ownership Transfer: Full administrator transfer of GitHub/GitLab organizations or repositories to client engineering team.
- Clean Git History: All commits signed and verified; zero temporary debug branches or lingering mock commits.
- Pinned Dependencies: All
package.json,Dockerfile, and Helm requirements pinned to deterministic, reproducible releases. - Documentation in Repo:
README.md,ARCHITECTURE.md, and local developer setup instructions verified on a fresh workstation.
2. Infrastructure & Cloud Resources
Section titled “2. Infrastructure & Cloud Resources”- Cloud Account Ownership: All AWS/GCP/Hetzner accounts and Cloudflare domains belong exclusively to the client; zero billing dependency on Jampuk accounts.
- Infrastructure as Code (IaC): All Terraform/OpenTofu, CloudFormation, or Ansible playbooks committed and verified with clean plan outputs.
- Clean Kubernetes Clusters: Namespaces, network policies, and Helm releases running without pending pods or crash-looping containers.
- Automated Backup Schedules: Snapshots and cold database dump cron jobs verified and operational.
3. Secrets, Keys & Access Rotation
Section titled “3. Secrets, Keys & Access Rotation”- Master Secrets Migration: All environment variables and production secrets migrated into the client’s HashiCorp Vault, AWS Secrets Manager, or Kubernetes Secrets.
- Jampuk Access Revocation: Remove all Jampuk engineer SSH keys, IAM users, and API tokens from production perimeters.
- Database Master Credentials: Client generates new administrative passwords and rotates existing service account tokens.
- DKIM & TLS Certificates: Private keys secured inside client-owned keystores.
4. Runbooks, Observability & Knowledge Transfer
Section titled “4. Runbooks, Observability & Knowledge Transfer”- Runbooks Delivered: Incident playbooks, routine maintenance guides, and DR procedures reviewed with client leads.
- Observability Dashboards: Prometheus/Grafana or Datadog dashboards shared and verified for primary KPIs (traffic, error rate, p95 latency).
- Alert Channel Integration: Slack/PagerDuty notification endpoints routed directly to the client’s on-call rotation.
- Walkthrough Session: Dedicated 60–90 minute technical walkthrough recording and architecture Q&A session completed.
- Formal Acceptance Sign-Off: Client technical representative confirms acceptance of all fixed-scope deliverables.