coulomb/net-kingdom
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

NK-WP-0049-T43: record founder answers; owner requests sent
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: sonnet
Assistant-Process: 628290@bnt-lap001
Assistant-Session: 70de878b-b4e0-4110-a1ec-bbd553a5f483
This commit is contained in:
tegwick 2026-10-27 19:05:27 +01:00
parent 425265e57f
commit 095019d134
2 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/nk49-phase-b-plan.md
View file

@ -105,7 +105,9 @@ Not claimed: production continuity or redirect, new grants, a live OpenBao read
secret data (`platform/workloads/keycape/secrets-engine-openbao` stays metadata only),
human login through Authelia, or owner acceptance. T18 also needs its owner acceptance.
## Open decisions for the founder and owners
## Decisions (answered 2026-10-27; decision `e4db6c9f`) and remaining owner items
Founder answers: 1 railiance-platform creates the network; 2 reissue via `letsencrypt-prod` once railiance-cluster confirms the duplicate count (no self-signed, no retained key); 5 one workload consumer suffices, no Authelia. Item 3 (secret custody) is secrets-engine's to propose and item 4 (ISRG trust) is confirmed in the owner rehearsal. The answers authorize nothing; windows and signatures stay separate.
1. **Network creator.** railiance-platform (proposed) or NetKingdom?
2. **TLS identity.** The T18 attempt reissued `kc.coulomb.social` through