RESOURCES
Operational evidence
Runbooks and evidence boundaries for a production identity service.
| Evidence area | Current boundary | Required evidence |
|---|
| D1 continuity | Migration state and local smoke tests are automated | Current remote backup/restore rehearsal and documented recovery owner |
| Migrations | Additive, ordered migrations are checked before deployment | Rollback rehearsal and restore-point review before any production migration |
| Incident response | Safe classifications, request IDs, and bounded telemetry exist | Approved runbook, escalation contacts, exercise record, and status-communication procedure |
| Secrets and signing keys | Secrets remain server-side and are excluded from public output | Rotation procedure, owner, emergency disable path, and post-rotation verification |
| Privacy operations | Scoped export is live and secret-free | Retention schedule, legal hold process, deletion approval, and completion evidence |
| Independent assurance | No compliance or penetration-test claim is made | External assessment and approved publication decision |
Safe release practice
- Inspect remote D1 migration state and create/check a current restore point before applying an additive migration.
- Run the complete dependency, security, source, migration, artifact, and Cloudflare gate before deployment.
- Verify /api/health, /api/v1/readiness, /api/v1/rehearsal, /release-manifest.json, and the preserved Replay QA nonce after deployment.
- Treat a launch approval as authorization for the configured runtime boundary, not as evidence that every manual operational action is complete.