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

Record native factory sender proof and deployment defect correction
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-11 14:26:23 +02:00
parent dbcf6c8134
commit ce984af48d
1 changed files with 43 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -209,3 +209,46 @@ remains AUDIT-WP-0009-T12, and tamper_evidence=false remains the accurate claim.
Factory attempts and paid calls are still zero. The next useful step is actual
producer/receiver acceptance, followed by the existing service/policy/human
admission chain and the bounded reuse-surface factory attempt.
### Native producer return — 2026-09-11 10:42 UTC
Both actual source adapters used their own ESO-delivered credential inside a
bounded native Job. Each synthetic event received 202, retained its durable
outbox after an injected lost receipt, and received duplicate 200 after a fresh
process reopened the outbox. Each source's reconciliation reported exactly one
record for its unique probe class. Wrong source/tenant, seven archive read
routes, sibling reconciliation and invalid-bearer requests were refused.
The first Informed Decision probe exposed a private-store startup defect:
fsGroup volumes add inherited setgid to a newly created 0700 directory.
Informed Decision `1a12223` corrects creation without repairing unsafe existing
data. The regression failed before the fix; the available suite now passes
335 tests with 39 optional checks skipped. Native retry verifies the exact
corrected helper. Six probe tests and eleven rebuilt-container checks pass,
including actual setgid-volume startup, restart/restore and cleanup.
All temporary probe Jobs, Pods, ConfigMaps and NetworkPolicies are verified
absent. Receiver c82e0442 remains operational/durable; tamper_evidence=false.
Producer verification requires no operator registry read or new OpenBao login.
Independent readback is a separate attended command consuming the successful
receipt; it must not rerun the producer jobs. Both attended verification-login
attempts this session ended before handoff (exit 5; remote revocation
unconfirmed), so independent archive readback remains pending.
This proves synthetic outbox delivery/recovery with native sender credentials,
not domain-transaction atomicity, deployed producer services or human binding.
An invalid bearer is not a revoked formerly valid bearer. AUDIT T09/T11 and
RPF T08 remain progress for independent readback and audit bearer-revocation
acceptance; CCR21/22 remain applied. Service/policy/human admission and native
runtime/spend gates remain separate. Factory attempts and paid calls remain 0.
The practical efficiency gains are a native startup defect found before UI
cutover, a container fixture corrected to exercise real volume permissions, and
producer checks separated from privileged readback so a failed attended login
no longer discards completed verification. These are setup/verification gains;
factory throughput and the fourteen-day founder-load target remain unmeasured.
[Retained native proof and attempt history](/home/worsch/prj-helixforge-factory/evidence/2026-09-11-factory-native-producers.json)
and [exact readback resume command](/home/worsch/railiance-platform/docs/credential-lane-designs/factory-native-acceptance.md)
preserve the next step without reconstructing the session.