diff --git a/workplans/RAILIANCE-WP-0024-audit-core-custody-and-recovery-coordination.md b/workplans/RAILIANCE-WP-0024-audit-core-custody-and-recovery-coordination.md index 2064a0f..9a52991 100644 --- a/workplans/RAILIANCE-WP-0024-audit-core-custody-and-recovery-coordination.md +++ b/workplans/RAILIANCE-WP-0024-audit-core-custody-and-recovery-coordination.md @@ -4,7 +4,7 @@ type: workplan title: "Coordinate audit-core temporary custody and recovery exercises" domain: financials repo: railiance-platform -status: ready +status: active owner: codex topic_slug: railiance created: "2026-08-22" @@ -33,10 +33,12 @@ lease revocation, firewall change, or host reboot. response bodies in Git, State Hub, command output, evidence, or chat. - Use exact paths and non-secret handles only. Temporary files, if later approved, must be outside Git, mode `0600`, and securely removed. -- A sender token stored in the current audit-core registry has no intrinsic - OpenBao lease. Expiring its projection credential does not expire the copy - accepted by audit-core. E2 live execution therefore remains blocked until - audit-core enforces an `expires_at` value for each temporary identity. +- A sender token stored in the audit-core registry has no intrinsic OpenBao + lease. Audit-core deployed boundary enforcement for timezone-aware + `expires_at` at commit `abd22fa` / image digest + `sha256:c2fe39a0185b99be3fc0cb14d2de69772b8e66e20490097c9d11d90cc39719a6`. + Reverify that exact prerequisite before projection; projection-credential + expiry alone is still not sufficient. - All live exercises require a separate engagement acknowledgement, attended operators, a named window, and explicit abort authority. @@ -44,7 +46,7 @@ lease revocation, firewall change, or host reboot. ```task id: RAILIANCE-WP-0024-T01 -status: todo +status: wait priority: high state_hub_task_id: "c4da371a-f35d-5377-9f6a-d34e274c98d0" ``` @@ -63,6 +65,13 @@ and value-safe positive/negative evidence. Done when audit-core and the engagement owner can review a complete path whose failure mode is expiry or denial, not a long-lived accepted bearer. +**Window update (2026-08-22):** engagement `WH-ENG-20260822-AUDIT-E2-01` is +operator-approved and target-owner-acknowledged for 18:00Z–18:15Z. The task is +waiting for that attended window. Do not mint before approximately 17:59Z; +both identities must expire no later than 18:15Z and cleanup/reload must be +attended. No unattended scheduler or background credential job is authorized +by this record. + ## T02 — Define the runtime database lease recovery exercise ```task