Clarify remaining Scaleway custody and operating acceptance
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a11fd9-caf6-7a63-b578-9daaaa134ff2
This commit is contained in:
tegwick 2026-10-09 19:50:25 +02:00
parent 9a2cf213d1
commit 4ecbb0fb62

View file

@ -63,7 +63,7 @@ id: EMAIL-WP-0007-T03
status: progress
priority: high
needs_human: true
intervention_note: "First provider capture/retrieval and workstation recovery are proved. Retention/capacity, independent receipt/key/image escrow and separate recovery caller admission remain open."
intervention_note: "Scaleway selected; email-connect-backup-primary remains the existing prefix-only publisher. Closure package and local offline kit are tested. Owner-provided durable age/kit custody and separate recovery reader grants are still absent; existing archive bucket expires objects after 30 days."
state_hub_task_id: "680fe4d6-12af-5296-acf9-15c9a01a0db3"
```
@ -82,7 +82,7 @@ id: EMAIL-WP-0007-T04
status: progress
priority: high
needs_human: true
intervention_note: "First admitted backup/recovery and platform-root State Hub inbox failure delivery pass. Recurring schedule, retention/capacity, independent recovery custody and operator response acceptance remain open; timers stay disabled."
intervention_note: "First backup/recovery and platform-root inbox delivery pass. Daily schedule, retention and capacity targets are prepared in deploy/closure/plan.json. Independent Scaleway custody and recurring-operation acceptance remain open; timers stay disabled."
state_hub_task_id: "66401e5c-a5cf-5e67-beab-e503ae079964"
```