History

tegwick 15e54369be All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 2s Details AUDIT-WP-0009-T03/T09 — evidence_kind, and approval-engine's registration inputs T03. §9.6 gives load-bearing and attributive sources different obligations, so the archive must record which one a source declared rather than infer it from traffic. evidence_kind and completeness_trade now sit on SenderIdentity, the AUDIT_CORE_SENDERS schema, and the non-secret scope overlay. Two asymmetries are deliberate. The default is attributive, because the other default would have audit-core imply a completeness obligation no source ever accepted. And the overlay may raise the kind but never lower it — the same principle that stops an ExternalSecret refresh shrinking user-engine's tenants: a ConfigMap refresh must not drop a source's atomicity and detection obligations without anyone deciding to. A load-bearing source may not carry a completeness trade at all, since §9.6 requires atomicity of it, and evidence_declaration() reports completeness_claimed: false for both kinds. T09 (in progress). approval-engine's registration inputs are prepared and recorded in docs/approval-engine-source-registration.md: scope entry declared load-bearing, and audit-core-approval-engine-ingress with namespace and pod label ANDed in one `from` peer — narrower than user-engine's namespace-only rule, which is left unchanged. The scope entry lands ahead of the credential because the overlay only applies to senders the Secret already carries, so it admits nothing until the token exists; a test asserts that rather than trusting the reading. Two inputs remain approval-engine's: a confirmed tenant scope, since senders.py requires a missing tenant restriction be justified per sender and audit-core cannot justify it on another repo's behalf, and an explicit secret_policy choice. Applying the manifests is an operator action. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0185wifnLzCxjEY2MT1XbK7L Assistant: claude-code Assistant-Model: opus Assistant-Process: 713962@bnt-lap001 Assistant-Session: 2718d99d-d3ff-478f-83a2-3a30f01a02fc		2026-09-06 22:31:37 +02:00
..
audit-core.yaml	deploy(AUDIT-WP-0008): pin sender-expiry image	2026-08-22 12:01:08 +02:00
clustersecretstore.yaml	Read mounted DB credentials from a Kubernetes snapshot	2026-08-13 12:25:32 +02:00
externalsecret-senders.yaml	Stand up railiance01 receiver without founder bao kv put	2026-08-13 10:27:13 +02:00
externalsecrets.yaml	Stand up railiance01 receiver without founder bao kv put	2026-08-13 10:27:13 +02:00
migrate-job.yaml	deploy(AUDIT-WP-0008): pin sender-expiry image	2026-08-22 12:01:08 +02:00
networkpolicies.yaml	AUDIT-WP-0009-T03/T09 — evidence_kind, and approval-engine's registration inputs	2026-09-06 22:31:37 +02:00
README.md	deploy(AUDIT-WP-0008): pin sender-expiry image	2026-08-22 12:01:08 +02:00
senders-scope.json	AUDIT-WP-0009-T03/T09 — evidence_kind, and approval-engine's registration inputs	2026-09-06 22:31:37 +02:00
senders-scope.yaml	AUDIT-WP-0009-T03/T09 — evidence_kind, and approval-engine's registration inputs	2026-09-06 22:31:37 +02:00

README.md

railiance01 package

Target: railiance01 only. The workstation kubeconfig that talks to that API is the k3s-api-railiance01 tunnel (local port 16444). ~/.kube/config-hosteurope currently points at 16443 (coulombcore); rewrite the server port or export a copy before applying.

Apply order is documented in docs/operator-runbook.md. Do not apply the Deployment until:

The image digest is pinned (currently sha256:c2fe39a0… from commit abd22fa).
Secrets audit-core-database, audit-core-database-migrate, and audit-core-senders exist. ConfigMap audit-core-senders-scope is applied (deploy/senders-scope.yaml) before the Deployment mounts it.
Job audit-core-migrate has completed.

make image-build
make deploy-dry-run