38 lines
1.3 KiB
Markdown
38 lines
1.3 KiB
Markdown
---
|
|
taskmaster_id: "4.9"
|
|
status: "done"
|
|
priority: "medium"
|
|
depends_on: ["8"]
|
|
parent_id: "4"
|
|
source: "taskmaster"
|
|
generated_at: "2026-05-24T07:26:29.052Z"
|
|
---
|
|
|
|
# 4.9 - Create migration and operational runbooks
|
|
|
|
- [x] 4.9 - Create migration and operational runbooks #taskmaster #priority/medium #status/done 🔼 🆔 tm-4-9 ⛔ tm-8
|
|
|
|
## Metadata
|
|
|
|
| Field | Value |
|
|
| --- | --- |
|
|
| Taskmaster ID | 4.9 |
|
|
| Status | done |
|
|
| Priority | medium |
|
|
| Dependencies | 8 |
|
|
| Parent | 4 - Define backend security and refactor strategy from latest audit |
|
|
|
|
## Description
|
|
|
|
Document rollout, rollback, and incident response for the selected backend/funds architecture.
|
|
|
|
## Details
|
|
|
|
Completed. Produced `08 - Operations/Backend Funds Migration and Operational Runbooks.md`.
|
|
|
|
Include SHKeeper legacy read path, provider feature flag, ledger backfill, validation report before enforcement, rollback criteria, webhook cutoff, manual reconciliation, failed webhook, duplicate/missing payment, stuck release, disputed release attempt, compromised admin, leaked API key, provider outage, chain/RPC outage, suspicious payment proof, and npm/package compromise.
|
|
|
|
## Verification
|
|
|
|
Runbooks identify owner, trigger, detection signal, immediate action, recovery action, and post-incident documentation for each scenario.
|