coulomb/railiance-master
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Schedule OpenBao retention closeout

Browse source
This commit is contained in:
codex 2026-08-04 00:53:34 +02:00
parent e24b3591a7
commit a89019eae1
4 changed files with 38 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

32
activity-definitions/openbao-retention-closeout.md Normal file
View file

@ -0,0 +1,32 @@
---
id: "e274defb-28f2-571e-abcb-c17b57eab473"
name: "RAILIANCE-WP-0020 OpenBao Retention Closeout"
type: activity-definition
version: "1.0"
enabled: true
owner: railiance-master
governance: custodian
status: active
created: "2026-08-04"
trigger:
type: scheduled
at: "2026-08-17T08:00:00+02:00"
timezone: Europe/Berlin
---
# RAILIANCE-WP-0020 OpenBao retention closeout
One-shot reactivation after the shortened 14-day reversible-retirement window.
It emits a claimable Activity Core ops run for the remaining cleanup task; it
does not delete CoulombCore resources automatically.
```rule
id: reactivate-openbao-retention-closeout
condition: ""
action:
task_template: "Reactivate RAILIANCE-WP-0020 for OpenBao retention closeout"
description: "Move RAILIANCE-WP-0020 from backlog to active, run the railiance01 disaster-recovery drill, verify retained rollback requirements, and request fresh explicit approval before any destructive CoulombCore cleanup. Remaining task: RAILIANCE-WP-0020-T08."
target_repo: railiance-master
priority: medium
labels: ["railiance", "openbao", "retention", "reactivation", "RAILIANCE-WP-0020-T08"]
```