Sync State Hub workstream and task IDs for all workplans

Rebind DISCTL-WP-0001/0002 after stale hub references and register
DISCTL-WP-0003 with fix-consistency.
This commit is contained in:
tegwick 2026-07-07 17:04:06 +02:00
parent b0f804f872
commit 3604ff6ea0
3 changed files with 19 additions and 13 deletions

View file

@ -9,7 +9,7 @@ owner: claude-code
topic_slug: custodian
created: "2026-07-04"
updated: "2026-07-04"
state_hub_workstream_id: "359d7db1-bea1-4ad4-b99c-29c37bbad7c2"
state_hub_workstream_id: "73d2ecb3-e594-4a7c-920d-8753198eb6ec"
---
# Resilience foundation: registers, policy, first tested restore
@ -34,7 +34,7 @@ items 78 are T03/T04/T06 below; its cross-repo items are tracked by T08.
id: DISCTL-WP-0002-T01
status: todo
priority: high
state_hub_task_id: "0d7e27f6-1290-45da-b76a-407b7b039e95"
state_hub_task_id: "f2f8648e-110c-455e-9745-6e2aa7f4fdfa"
```
This repo must survive the disasters it describes. Add at least one mirror on
@ -48,7 +48,7 @@ mirror is refreshed.
id: DISCTL-WP-0002-T02
status: todo
priority: high
state_hub_task_id: "59f04771-25cf-4bde-adf0-8a1cd418dc1f"
state_hub_task_id: "99bb7f1b-3ab4-4cee-b7ff-f55f0c2b287a"
```
Write `AssetRegister.yaml` and `DataRegister.yaml` seeded with the current
@ -64,7 +64,7 @@ Every T1 entry must name its source of truth and backup mechanism (or mark it
id: DISCTL-WP-0002-T03
status: todo
priority: high
state_hub_task_id: "8c119835-0c97-4556-ab98-42267688e432"
state_hub_task_id: "a6f87f9d-5fbd-4586-bb97-62e0ce99cb27"
```
Write `ResiliencePolicy.md` (operating principle, tier definitions, drill
@ -78,7 +78,7 @@ RTO ≤ 1 day full recovery, RTO ≤ 48h for code/content/control plane.
id: DISCTL-WP-0002-T04
status: todo
priority: high
state_hub_task_id: "d6b9b621-c901-48c0-be4c-7bc98245de99"
state_hub_task_id: "75ce1886-e53e-4382-9a39-07f638cb59a8"
```
Write `BackupPolicy.md`: 3-2-1 + immutable/offline model, per-stream mechanisms
@ -94,7 +94,7 @@ defined schedule with a named alerting path.
id: DISCTL-WP-0002-T05
status: todo
priority: medium
state_hub_task_id: "c413734b-7a17-4164-bf72-0de18fd509c4"
state_hub_task_id: "da73d8fd-13d0-4549-a196-c29e9f418784"
```
Write `RestoreRunbooks/01-full-server-loss.md` (new machine → Ansible → secret
@ -109,7 +109,7 @@ stranger could execute it.
id: DISCTL-WP-0002-T06
status: todo
priority: high
state_hub_task_id: "c816efa0-bbc2-4612-9a8f-a03bd83ca7c0"
state_hub_task_id: "b08f1b02-4937-42aa-9989-042f50cc2e01"
```
The 2026-07-04 Forgejo drill (evidence in `railiance-infra`) proved that path;
@ -127,7 +127,7 @@ workplan: no drill evidence here, not finished.
id: DISCTL-WP-0002-T07
status: todo
priority: medium
state_hub_task_id: "ee7254a8-5adf-4913-bb47-bf94e59c88ec"
state_hub_task_id: "b1b9df65-1dc9-45a2-89fb-c6e0655be85d"
```
Write the five playbooks under `IncidentPlaybooks/`: ransomware/hostile access,
@ -141,7 +141,7 @@ page of numbered steps per the spec (§6).
id: DISCTL-WP-0002-T08
status: todo
priority: medium
state_hub_task_id: "af9ae2ca-5af8-45af-9301-8c28e78ea32a"
state_hub_task_id: "2c8f432e-dc63-4a6b-a838-e60eb514d848"
```
Drive closure of the cross-repo items from the Forgejo assessment's pickup