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

Record whynot-design publish lane decisions

Browse source
This commit is contained in:
tegwick 2026-07-01 20:07:20 +02:00
parent 635521406f
commit 757770b42f
1 changed files with 18 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

18
DECISIONS.md
View file

@ -19,3 +19,21 @@ Superseded by WP-0004 T09 cancellation and CUST-WP-0038 ownership of State Hub H
Superseded by completed WP-0004 outcome: activity-core was deployed as a K3s production service on railiance01 on 2026-05-22; the packaging architecture question is no longer blocking this workplan. Superseded by completed WP-0004 outcome: activity-core was deployed as a K3s production service on railiance01 on 2026-05-22; the packaging architecture question is no longer blocking this workplan.
--- ---
## Review CCR-2026-0001 whynot-design npm publish token lane
**Date:** 2026-06-27
**Decided by:** human
APPROVE: scoped path and confirmed binding are acceptable
---
## Review CCR-2026-0001 corrected whynot-design npm publish token lane
**Date:** 2026-06-27
**Decided by:** human
APPROVE: We fixed the path using coulomb as the org/tenant.
---