AUDIT-WP-0010 T01/T03/T04 — admit tenant-engine, and the envelope does not match
Registration: attributive, with the declared completeness_trade recorded on the receiver side rather than only in the emitter, per §9.6's requirement that the trade travel with the trail. tenants ["*"] is justified rather than inherited — tenant-engine's events carry the affected tenant, the set is every tenant including ones created later, and an explicit list would fail closed at exactly the moment a tenant is provisioned, dead-lettering the creation evidence of the tenant whose creation it is. source stays pinned exactly. Ingress ANDs namespace and pod label; a weaker evidence class is not a reason for a wider network rule. All inert until the token exists. Then the finding T04 existed to find: tenant-engine cannot deliver a single event today. envelope_for sends five required fields under other names — event_id, action, resource, observed_at, details — and omits correlation_id entirely, so normalize() raises invalid_event. Verified by running the real envelope through the real function, not by reading. Worse than an ordinary integration bug. The drain treats 400 as terminal, so the outbox row is marked handled while audit-core holds only a dead letter, which is not chained and is not custody. Lost on both sides, and since the drain is non-blocking and attributive, nothing fails loudly — a silent total loss of the stream presenting as a working integration. Taking the correction the intake invited rather than accepting a lossy record. normalize() is NOT relaxed to accept the alternate spellings: a receiver that guesses which sender key means which stored field has made the mapping its own, and the record stops being the sender's assertion. correlation_id cannot be synthesized at all — an invented one ties an event to an operation audit-core never observed. Root cause is ours. The accepted envelope was published nowhere a sender could read it; audit-backend-contract.md describes the stored record, and a sender reading it would reasonably infer exactly the names tenant-engine used. schema_version audit-core.event.v1alpha1 selects nothing here and gave a false impression of a negotiated contract. Published docs/event-envelope.md as the wire contract, including the point that a 400 means the event is not in the archive and must be treated as a defect to fix rather than a delivery outcome. T05 moved to wait: nothing to prove end to end until an event can be accepted. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Nb7Q6ZmXppNDkTWytfYqfv Assistant: claude-code Assistant-Model: opus Assistant-Process: 2069992@bnt-lap001 Assistant-Session: 167dd7f8-2a25-4be1-aa46-3b6f1a5f94c6
This commit is contained in:
parent
e0505af3b5
commit
3c2cdcdf79
10 changed files with 610 additions and 6 deletions
|
|
@ -100,7 +100,26 @@ description: >
|
|||
Requested: sender registration + token lane, or a correction if the
|
||||
envelope needs a field this engine is not sending.
|
||||
created: '2026-08-29'
|
||||
updated: '2026-08-29'
|
||||
updated: '2026-09-10'
|
||||
outcome: registered-with-a-blocking-correction
|
||||
resolution: 'Registered attributive with the declared completeness_trade
|
||||
recorded receiver-side, tenants ["*"] justified per sender, source pinned
|
||||
exact, ingress added — all inert pending the token
|
||||
(docs/tenant-engine-source-registration.md, AUDIT-WP-0010 T01/T03/T04).
|
||||
Taking the correction the intake invited: the envelope does not match.
|
||||
envelope_for sends five required fields under other names (event_id, action,
|
||||
resource, observed_at, details) and omits correlation_id entirely, so
|
||||
normalize() raises invalid_event and every event would 400 and dead-letter.
|
||||
Because the drain treats 400 as terminal, the outbox row is marked handled
|
||||
while audit-core holds only a dead letter — lost on both sides, silently,
|
||||
presenting as a working integration. normalize() is not being relaxed to
|
||||
accept the alternate spellings: guessing which sender key means which stored
|
||||
field would make the mapping audit-core''s rather than the sender''s, and
|
||||
correlation_id cannot be synthesized at all. Root cause is audit-core''s —
|
||||
the wire envelope was documented nowhere a sender could read it, and
|
||||
schema_version audit-core.event.v1alpha1 selects nothing here. Contract now
|
||||
published at docs/event-envelope.md. Stays OPEN until tenant-engine corrects
|
||||
the emitter and T05 records live evidence.'
|
||||
state_hub_intake_id: "01a04d8f-b1c1-746a-8007-15221ebf0a48"
|
||||
```
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue