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

feat(AUDIT-WP-0008): admit governed E2 probe ingress
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-5.6-sol
Assistant-Session: 01a025c2-407a-7a32-b40a-f37a52f03f62
This commit is contained in:
tegwick 2026-08-22 09:37:30 +02:00
parent 34f0077a9b
commit 5b5196eea7
4 changed files with 80 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

23
workplans/AUDIT-WP-0008-tenancy-posture-alignment.md
View file

@ -393,17 +393,20 @@ minute, and requires two temporary read-enabled identities each scoped to one
fixture tenant. The production `user-engine` identity remains unchanged and is
not a test credential.
Whitehat supplied a production engagement record at `3770b41` and a bounded
adapter at `7396fe7`. Target review found that the adapter omits audit-core's
required `Idempotency-Key` header on POST, so it would abort fixture seeding
with `idempotency_key_mismatch` and cannot yet produce evidence. Review reply
`74b815ea-341f-455d-8fdb-2333f5753f76` accepted the two-identity fixture shape
in principle and requested that fix plus corrected production-approval and
owner-acknowledgement provenance before formal acknowledgement.
Whitehat supplied and corrected a bounded adapter, including audit-core's
required `Idempotency-Key` and deterministic retry payloads. The original
production engagement was then cancelled at the session cutoff with zero
target requests and its identifier is terminal. Whitehat subsequently added
the governed test-plane contract and fail-closed admission at `95129d7`.
This is progress, not evidence and not live authorization. T05 becomes `done`
only when the corrected engagement is acknowledged, the bounded run completes,
and its sanitized target report has been routed to `risk-nexus`.
Audit-core now declares a dedicated ingress peer for that plane: only a pod in
namespace `whitehat` carrying both the plane and `target=audit-core` labels can
reach port 8080 through it. Authentication and tenant scope remain mandatory.
The operator runbook records the exact two-identity fixture shape and cleanup
obligation. This is readiness, not evidence or live authorization. T05 becomes
`done` only after a new engagement is approved and owner-acknowledged, the
cluster plane and value-safe custody broker are provisioned, the bounded run
completes, and its sanitized target report reaches `risk-nexus`.
```task
id: AUDIT-WP-0008-T06