Owns publish validation and the deduplication ledger protocol for every transport (03 §2.1, §1.1): topic lookup →
topic rejections → per-request validation → envelope → transport. Results stay aligned with requests.
Database transport: per message, in one transaction (the caller's when given, else an independent one with
transient retry): Reserve → driver.Publish → Confirm → commit only when accepted. Enlisted publishes take every
publish-order lock up front in sorted key order and let every database error propagate to the caller.
Cloud transport: Reserve each keyed request → one driver.Publish for the batch → Confirm accepted, Release the rest,
with the ledger on an independent executor the coordinator owns (F8).
Owns publish validation and the deduplication ledger protocol for every transport (03 §2.1, §1.1): topic lookup → topic rejections → per-request validation → envelope → transport. Results stay aligned with requests.
Database transport: per message, in one transaction (the caller's when given, else an independent one with transient retry): Reserve → driver.Publish → Confirm → commit only when accepted. Enlisted publishes take every publish-order lock up front in sorted key order and let every database error propagate to the caller. Cloud transport: Reserve each keyed request → one driver.Publish for the batch → Confirm accepted, Release the rest, with the ledger on an independent executor the coordinator owns (F8).