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

AUDIT-WP-0009-T03/T09 — evidence_kind, and approval-engine's registration inputs
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
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
This commit is contained in:
tegwick 2026-09-06 22:31:37 +02:00
parent a07c52e34a
commit 15e54369be
10 changed files with 592 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

18
SCOPE.md
View file

@ -103,11 +103,19 @@ effect of its own.
freshness window. Until `AUDIT-WP-0009-T02` schedules attestation, the
honest answer in production is `false` — the overclaim is gone, the
precondition is not yet met.
- No cadence, heartbeat, reconciliation, or load-bearing classification exists.
The §9.6 obligations Audit Core argued for are not yet supportable by Audit
Core.
- `approval-engine` is not yet registered as a source.
- No negative test asserts the absence of an approval-validity surface.
- No cadence, heartbeat, or reconciliation surface exists. The §9.6 detection
obligations Audit Core argued for are not yet supportable by Audit Core, so
a suppressed load-bearing event still produces silence
(`AUDIT-WP-0009-T04`/`T05`/`T06`).
- Load-bearing classification **does** now exist: `evidence_kind` on
`SenderIdentity` and the registration schema, defaulting to `attributive`
(`AUDIT-WP-0009-T03`, closed 2026-09-06).
- `approval-engine` registration inputs are prepared and inert pending its
token, a confirmed tenant scope, and an operator apply —
`docs/approval-engine-source-registration.md` (`AUDIT-WP-0009-T09`).
- ~~No negative test asserts the absence of an approval-validity surface.~~
**Closed 2026-09-06 (`AUDIT-WP-0009-T08`)**,
`tests/test_approval_validity_prohibition.py`.
## Getting Oriented