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

Activate whynot npm credential lane

Browse source
This commit is contained in:
tegwick 2026-06-29 00:13:09 +02:00
parent e88c7829f3
commit 8f617fcbf4
5 changed files with 67 additions and 31 deletions
Download patch file Download diff file Expand all files Collapse all files

6
workplans/RAILIANCE-WP-0007-credential-change-approval-workflow.md
View file

@ -296,6 +296,12 @@ OpenBao read policy and OIDC role, confirmed metadata `catalog-id`, and confirme
now records non-secret evidence for that apply check. Positive whynot-design and
negative non-whynot caller verification still gate `active`/`ready`.
**2026-06-29:** The whynot-design pilot completed OpenBao verification. Positive
fetch succeeded with output suppressed, negative login failed with the expected
groups bound-claim mismatch, `platform-root` membership was restored afterward,
and `CCR-2026-0001` is now active/ready/resolvable. ops-warden catalog
confirmation remains the external closeout step.
## T08 - Add deactivation, rotation, and compromise flows
```task