Review runtime collector mapping and bind delivery owner commitment

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a13eab-1e6a-7b33-9c37-372e90ada3a2
This commit is contained in:
tegwick 2026-10-15 21:19:12 +02:00
parent 5eb7e86f7a
commit 6c690b0b84
2 changed files with 30 additions and 1 deletions

View file

@ -284,3 +284,19 @@ This source update does not deploy rapp-qonto or create its missing collector.
QONTO-WP-0006-T02/T03 and AUDIT-WP-0013-T05 still hold sender/delivery and
independent observation acceptance. Existing bank credential TTL, policy,
identity, rate limits and process-local counter limitations are unchanged.
## Runtime-owned collector mapping (2026-10-15)
RAPP-QONTO-WP-0004 supplies the concrete structured-stdout sender. Source owner
mapping preserves audit.allow/audit.deny and maps each audit.heartbeat one-to-one
to audit-core.heartbeat with data.class=audit.deny, retaining original event_class,
instance,sequence,source/window counters. No three-way fanout is introduced.
This reflects the source heartbeat assertion about deny transitions; it does not
assert no allow transitions. Receiver heartbeat_classes is audit.deny:7200 for
source frame3600 and effective grace10800. Mixed sender admission is load-bearing;
allow retains attributive semantics in the canonical inventory. Package-declared
tenant:friendly:binky is the bank-resource envelope scope; request tenant_id stays
untrusted claim data. Exact sender/source,deterministic retry IDs,retry/lag semantics
and limitations are documented in rapp-qonto/docs/audit-collector.md. The source
logger remains unchanged. No delivery/independent acceptance is claimed here.