chore(consistency): sync task status from DB [auto]
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

Updated by fix-consistency on 2026-10-09:
  - update .custodian-brief.md for railiance-platform

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 327203@bnt-lap001
Assistant-Session: 55028ae3-4914-4bd1-8f5c-815f3527aef0
This commit is contained in:
custodian-sync 2026-10-09 00:32:26 +02:00
parent 0b2e7ddb5f
commit 5e67a425c4

View file

@ -2,29 +2,19 @@
# Custodian Brief — railiance-platform
**Domain:** financials
**Last synced:** 2026-10-08 22:06 UTC
**Last synced:** 2026-10-08 22:32 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### Admit Coulomb paired archives and independent email-ledger recovery
Progress: 1/6 done | workplan_id: `cb55e474-c7a5-5c6f-bd72-ce65f853e3e3`
### Coordinate KeyCape live Secret exposure recovery
Progress: 4/6 done | workplan_id: `b2c25a01-4a80-55c1-90cf-8538000f7e0e`
**Open tasks:**
- ! T02 — Admit offsite prefix, retention and caller custody `b06f1a44`
- ! T03 — Activate and verify retrieval and application recovery `871c14da`
- ► T01 — Review and accept the paired backup execution identity `ceb58abf`
- ► T05 — Admit the independent email-connect ledger archive caller `3f744ce6`
- · T04 — Bind monitoring and recurring recovery custody `687fd36d`
### Coordinate audit-core temporary custody and recovery exercises
Progress: 2/4 done | workplan_id: `f4640325-e89c-591d-b58e-ec6b087900ac`
**Open tasks:**
- ! T02 — Define the runtime database lease recovery exercise `fda4262a`
*(wait: Value-safe lease revoke/expire exercise must be coordinated with rapp-postgres and audit-core.)*
- ! T03 — Define the coordinated railiance01 reboot exercise `ba729d18`
*(wait: Single-node outage exercise needs operator access and a declared restart order coordinated with railiance-infra, railiance-cluster, audit-core and the OpenBao package owner.)*
- ! T03 — Collect exact owner acknowledgements `714ae011`
*(wait: Attended resolver run: postchecks outstanding; NetKingdom asked to package the complete sequence as one receipt-producing command for the next attended session.)*
- ! T06 — Publish the Railiance/OpenBao custody handoff `3b9748c4`
*(wait: Platform/OpenBao owner must publish the non-secret routing receipt for both lanes through the attended handoff; values are never inferred.)*
### ArgoCD phase B: adopt the four existing Applications on railiance01
Progress: 2/8 done | workplan_id: `98140775-3b9a-5cf9-9af6-722502d487dc`
@ -50,14 +40,14 @@ Progress: 3/4 done | workplan_id: `7beec1a7-aa82-5a36-9a66-6b60008a2455`
- ! Establish primary full-archive delivery and application recovery `a4807df0`
*(wait: Operator chooses the independent archive prefix and confirms retention/caller contract and bounded worker credential delivery before the primary archive retrieval.)*
### Coordinate KeyCape live Secret exposure recovery
Progress: 4/6 done | workplan_id: `b2c25a01-4a80-55c1-90cf-8538000f7e0e`
### Coordinate audit-core temporary custody and recovery exercises
Progress: 2/4 done | workplan_id: `f4640325-e89c-591d-b58e-ec6b087900ac`
**Open tasks:**
- ! T03 — Collect exact owner acknowledgements `714ae011`
*(wait: Attended resolver run: postchecks outstanding; NetKingdom asked to package the complete sequence as one receipt-producing command for the next attended session.)*
- ! T06 — Publish the Railiance/OpenBao custody handoff `3b9748c4`
*(wait: Platform/OpenBao owner must publish the non-secret routing receipt for both lanes through the attended handoff; values are never inferred.)*
- ! T02 — Define the runtime database lease recovery exercise `fda4262a`
*(wait: Value-safe lease revoke/expire exercise must be coordinated with rapp-postgres and audit-core.)*
- ! T03 — Define the coordinated railiance01 reboot exercise `ba729d18`
*(wait: Single-node outage exercise needs operator access and a declared restart order coordinated with railiance-infra, railiance-cluster, audit-core and the OpenBao package owner.)*
### Close S3 service assurance and ownership gaps
Progress: 4/7 done | workplan_id: `ca639c3d-3a87-5fa4-ad13-6f2e014b0c84`
@ -89,7 +79,7 @@ Progress: 3/9 done | workplan_id: `975db491-5412-5e27-8e34-14a2417bb039`
**Open tasks:**
- ! Accept and provision secrets-engine service JWT login `e0c82ea9`
*(wait: KEY-WP-0037 now owns protected custody, real registration and native issuance. Platform issuer-reader source CCR-2026-0033 is prepared. secrets-engine must accept exact consumer host/file/delivery/rotation coordinates before the separate custody child is finalized; KeyCape exact-primary identity repair and separate live go remain.)*
*(wait: Source ready (CCR-2026-0038, service-jwt-login applier type). Waits on founder approval + binding confirmation + delegated apply (one command, see 2026-10-09 note), then the login proof via a real KeyCape service JWT (SECRETS-WP-0012-T03 probe-openbao).)*
- ! Implement the platform operator-write CCR contract and Fluid lane `f47e5bc5`
*(wait: MASON-WP-0005-T02 source contract is done (ops-mason message 79570eb8). The attended policy/schema apply remains with the open provisioning decision.)*
- ! Admit the separate approval client-side readers `68bff751`