coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

docs(factory): record executable issuer probe and pending live admission
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source
This commit is contained in:
codex 2026-09-08 23:32:39 +02:00
parent e52c47ff39
commit a632b7aa87
3 changed files with 303 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

27
docs/assessments/2026-09-08-helixforge-factory-critical-path.md
View file

@ -92,3 +92,30 @@ fourteen-day observation window remain open.
[Runtime and custody continuation receipt](2026-09-08-helixforge-factory/runtime-custody-continuation.json)
retains source revisions, validations, projection readbacks and progress IDs.
## Executable upstream issuer proof prepared
KEY-WP-0013-T07 closes the missing diagnostic preparation. KeyCape source
`6f33abd` adds a one-shot upstream verifier; source `1b9793f` pins the tested
image and [execution packet](/home/worsch/key-cape/docs/upstream-issuer-proof.md).
The probe verifies a real authorization-code response inside the adapter and
emits only a verified issuer and check metadata. It issues no downstream token.
The complete Go race suite and vet passed. Five packet/receipt tests and seven
real Traefik 3.6.7 route cases passed; ordinary callbacks remain on their normal
backend. Railiance server dry-run accepted the exact five-resource packet. The
immutable container also produced the expected one-second idle-timeout receipt
as UID 65534 with a read-only filesystem and no network.
The temporary Job has a ten-minute deadline and no retry; its route, service
and two network policies must carry the real Job UID for bounded cleanup. It
uses only the existing config YAML, without the signing-key mount or a
Kubernetes API token. That YAML contains credential data, so live execution
requires the deployment owner's admission. KEY-WP-0013-T02 retains that decision,
the actual signed issuer receipt, contained configuration pin and subsequent
custody/rollout reviews. No live issuer result is inferred from preparation.
This replaces an unspecified manual observation with a tested command and
bounded execution packet. The current receipt is
[key-cape/docs/evidence/upstream-issuer-probe.json](/home/worsch/key-cape/docs/evidence/upstream-issuer-probe.json).