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

Record approved requester delivery and attended execution packet
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a10780-6d41-7952-9718-dfbc1f41236f
This commit is contained in:
tegwick 2026-10-04 23:02:28 +02:00
parent 267814b90c
commit a7bc33b867
4 changed files with 75 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

1
docs/provisioning-windows/2026-10-04-1000/informed-decision/approved-ccr.sha256 Normal file
View file

@ -0,0 +1 @@
c54dd86fd1bd754e64b135f02cac8d9a8f4db314cb3ca44c9645565aa816eee7 credential-change-requests/CCR-2026-0032.yaml

41
docs/provisioning-windows/2026-10-04-1000/informed-decision/checklist.md
View file

@ -1,9 +1,32 @@
# Attended provisioning preparation: 2026-10-04
Decision: 0d6792b6-59e4-4fa0-887a-c4e51ea8e131
Preparation only. Founder window approval and each exact CCR revision remain required.
1. INFD-WP-0005-T05: NOT READY (CCR is not approved; never replay applied custody)
CCR: credential-change-requests/CCR-2026-0032.yaml
Lane: docs/credential-lane-designs/informed-decision-requester-workload.md
Owner receipt contract: docs/provisioning-windows/2026-10-04-1000/informed-decision/receipt-contract.json
Revalidate exact digest, upstream gates and native readiness before attended execution.
Checklist complete: false
# Requester delivery: approved, awaiting attended execution
CCR-2026-0032 was approved by Bernd Worsch in the informed-decision session on
2026-10-04 after owner runtime acceptance at c084600. This is the exact requester
delivery approval; broader service cutover and issuer rotation remain separate.
Approved CCR SHA256:
`c54dd86fd1bd754e64b135f02cac8d9a8f4db314cb3ca44c9645565aa816eee7`
The metadata child validates this digest, approved status, confirmed reviewed
binding, policy and role before execution. It compares both live objects before
writing missing metadata, refuses conflicts, and reads back exact configuration.
It neither reads credential values nor deploys Kubernetes objects.
Run from the founder's terminal with the existing OpenBao tunnel and browser:
```sh
BAO_ADDR=http://127.0.0.1:18200 VAULT_ADDR=http://127.0.0.1:18200 \
warden access openbao-platform-admin-login --exec -- \
python3 /home/worsch/railiance-platform/scripts/informed_decision_requester_metadata.py \
--expected-ccr-sha256 c54dd86fd1bd754e64b135f02cac8d9a8f4db314cb3ca44c9645565aa816eee7
```
Warden performs OIDC/MFA, runs the silent child, revokes its session and removes
private custody. Return only the exit code. Exit zero confirms this metadata
operation and Warden cleanup; it does not prove workload delivery or acceptance.
On nonzero exit, inspect bounded native metadata before any retry.
After successful metadata execution, continue owner-controlled ESO deployment,
exact workload positive/negative proof, mounted projection and requester exchange.
Keep the receipt-contract checks pending until observed. No credential rotation
is included. Checklist complete: false; no live metadata applied by the agent.