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

Record functional pilot walkthrough and prepare attended inventory handoff
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.1-sol
Assistant-Session: 01a1abf1-7e95-7141-87c9-ee78332bf790
This commit is contained in:
tegwick 2026-11-05 22:50:58 +01:00
parent 177a85d05f
commit fab81f0086
5 changed files with 221 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

30
docs/proposals/2026-11-05-vergabe-recovery-preflight/README.md
View file

@ -36,6 +36,36 @@ new standing agent grant is requested by the packet. The result must report
`native_inventory_complete: true` before using its expected release as the
baseline of a separately reviewed capture/restart operation.
## Founder-terminal handoff
The user has now confirmed cross-account task edits and the functional flow
through Zuschlag/Nachlese, with UI follow-up. The remaining first step is native
inventory. A restricted SSH check as `custodian-agt` was refused at authentication;
the agent did not try an elevated account or issue its own certificate.
From a synced `railiance-apps` checkout on **railiance01**, run:
```bash
python3 tools/vergabe_pilot_inventory_attended.py --submit
```
The launcher asks for the **path** to the existing gexec approver key. The normal
gexec review/signature step follows. It stages the fixed proposal in the existing
exchange directory, then uses `sudo -u custodian-agt` only to enqueue the signed
request under the required UID and read its sanitized result. Kubernetes access
runs through gexec's configured `kube:railiance01` target. The founder needs the
existing exchange access and ability to use that restricted account via sudo.
No new key, standing grant or privileged kubeconfig is installed. Keep the
approver key in its existing custody. If it is held only on the workstation,
sign the action there with the existing gexec CLI and supply that public signed
approval on the node with `--submit --approval /path/to/approval.json`; do not
copy the private key to the node. Gexec verifies the signature and its expiry.
Share the final result JSON. A pending result retains its request ID; inspect
that request before submitting again. The launcher defaults to local packet
review when `--submit` is omitted and refuses a changed action digest. The
existing gated executor remains responsible for signature/nonce/profile checks.
Validation: source compilation and synthetic command responses cover success,
immediate wrong-cluster refusal, image drift and exclusion of a private canary
from the receipt. Ruff is unavailable in the current shell. No native pass,