coulomb/railiance-master
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
railiance-master/activity-definitions/openbao-retention-closeout.md
codex 4864b7852d chore: use RMASTER-WP prefix for master workplans 
Rename RAILIANCE-WP-0017..0021 to RMASTER-WP-* so railiance-master
IDs no longer collide with railiance-platform's RAILIANCE-WP series.
Hub UUIDs are unchanged.
2026-08-14 14:29:18 +02:00

1.1 KiB
Raw Blame History

id name type version enabled owner governance status created trigger
e274defb-28f2-571e-abcb-c17b57eab473 RMASTER-WP-0020 OpenBao Retention Closeout activity-definition 1.0 true railiance-master custodian active 2026-08-04
type at timezone
scheduled 2026-08-17T08:00:00+02:00 Europe/Berlin

RMASTER-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.

id: reactivate-openbao-retention-closeout
condition: ""
action:
  task_template: "Reactivate RMASTER-WP-0020 for OpenBao retention closeout"
  description: "Move RMASTER-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: RMASTER-WP-0020-T08."
  target_repo: railiance-master
  priority: medium
  labels: ["railiance", "openbao", "retention", "reactivation", "RMASTER-WP-0020-T08"]