4864b7852d
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.
32 lines
1.1 KiB
Markdown
32 lines
1.1 KiB
Markdown
---
|
|
id: "e274defb-28f2-571e-abcb-c17b57eab473"
|
|
name: "RMASTER-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
|
|
---
|
|
|
|
# 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.
|
|
|
|
```rule
|
|
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"]
|
|
```
|