coulomb/audit-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Prepare compatible audit receiver with verified container lifecycle
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc
This commit is contained in:
tegwick 2026-09-11 06:46:15 +02:00
parent f1b0577095
commit cb23dc82fd
8 changed files with 426 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

20
workplans/AUDIT-WP-0009-evidence-role-conformance.md
View file

@ -456,8 +456,8 @@ CCR-2026-0021 (approval-engine) and CCR-2026-0022 (informed-decision), with
exact-path ESO projections and CAS-preserving first provision/resume. Its
receiver check refuses the current image before credential access. Seventeen
new tests, including eleven local OpenBao cases, and 53 existing credential-change
tests pass. Named owner reviews, compatible receiver release and target namespace
readiness remain prerequisites. No native sender credential or deployment changed.
tests pass. The user approved both named owner review sets on 2026-09-11.
Compatible receiver release and target namespace readiness remain prerequisites.
See railiance-platform/docs/credential-lane-designs/factory-audit-senders-review.md
and its dated preparation evidence. Existing sender/source scopes are preserved.
@ -483,3 +483,19 @@ to cover.
T05's dependency is real and should not be worked around. audit-core argued the
cadence obligation up to a MUST; inventing a local cadence shape ahead of the
Taxonomy schema would fragment the very interface it asked for.
### Compatible receiver release rehearsal — 2026-09-11
229 receiver/contract tests pass with real disposable PostgreSQL. The full suite
exposed five historical SQLite-import failures, now handed off as AUDIT-IN-0004;
that importer is not used by the native receiver. No migration SQL changed.
The new image uses the factory Alpine baseline and hashed runtime dependencies.
Candidate scan went from 81 High/3 Critical to zero reported vulnerabilities,
with the Alpine lifecycle-list warning retained. SIGTERM previously killed
PID 1 with exit 137; explicit handling now exits 0, preserves one in-flight
write and returns duplicate on restart/retry. Both synthetic senders pass exact
scope, redaction, independent readback and seven read-route denials.
[Rehearsal evidence](../docs/evidence/2026-09-11-factory-receiver-release.json).
Publish and native rollout are the next steps; T09/T11 remain progress until
real sender custody, delivery and owner acceptance are evidenced.