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

Mark whynot lane applied pending verification

Browse source
This commit is contained in:
tegwick 2026-06-28 12:53:39 +02:00
parent 271aa94642
commit adf865611c
5 changed files with 29 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/whynot-design-npm-publish-handoff.md
View file

@ -7,8 +7,8 @@ This is the next-session handoff for `CCR-2026-0001` and the
- CCR: `CCR-2026-0001`
- Decision: `e6381a56-6b04-4fd5-b2de-f3ef59cde888`
- Status: approved; non-secret OpenBao apply checks passed 2026-06-28
- Front door: `template`, `resolvable=false`
- Status: applied; non-secret OpenBao apply checks passed 2026-06-28
- Front door: `applied-pending-verify`, `resolvable=false`
- Catalog id: `whynot-design-npm-publish`
- Tenant/org: `coulomb`
- Workload/project: `whynot-design`
@ -202,6 +202,6 @@ then `CCR-2026-0001` can move toward `active`, and ops-warden can mark
Until then, keep the front door as:
```text
readiness = template
readiness = applied-pending-verify
resolvable = false
```