Delivery acknowledges the exact ADR-0054 assembled design
Delivery formally acknowledges ADR-0054 at the complete 26-file proposal head 8dc1f75dd4aaeb586df7ca6bfa4bf5a351efed39, draft coordination PR5 (https://github.com/sguild-admin/coordination/pull/5). No blocking design correction remains in Delivery's owned scope. This response is authored by Delivery under ADR-0054/delivery/001, coordinator 01a0e095-f279-7fd0-a8ef-92ce8f9547fc/local. Root remains sole canonical publisher and indexer. Earlier Delivery bounded positions are superseded as approval dispositions by this exact assembled-design acknowledgment, while their evidence remains retained.
Delivery accepts the parent tuple Scheduling4.0.0, Ordering4.0.0, CreditReservationLock3.7.0 and ServiceAuth1.10.0. The soft observer explicitly requires request and response Scheduling-Soft-Resolution-Observation-Version:2.0, outer protocol2.0, CurrentAssessment2.0 and assessment_revision_scope=delivery_protected_source in the closed assessment and its complete canonical digest input. Original immutable ResolutionResult/receipt/fence1.0 bytes and preimages remain unchanged. Unsupported, repeated or missing versions after cutover cannot fall back to old positive retirement semantics. Delivery's new original-bind observer separately uses its explicit1.0 transport and the single Revenue-only read policy. Coaching's protected-set wire and semantics remain unchanged.
Original source and quantity
The GET original-bind-associations intent route, exact organization_id/receipt_id selectors, dedicated system:revenue scope/audience and closed nondisclosing errors match Delivery's proposed surface. Prospective capture must retain the actual original bind booking, post-hook Versions, complete ReceiptRef and raw command/result bytes in the successful bind transaction. It cannot infer missing historical versions, regenerate raw bytes or admit a partial capture. Raw-byte bounds, canonical base64, strict body validation, byte hashes, command preimages, canonical capture digest and every redundant identity link remain independent checks. Current historical observation is separate from immutable capture and supplies no compensation authority.
Revenue owns all five financial fields, including quantity. The authentic original claim is immutable scheduling_bind_intents.context.reservedCredits, written alongside the original canonical reservation from the same admitted context. Revenue must require exact positive safe-integer equality of original context, current canonical Decimal reservation and full Authority quantity before preparation and writeback. A current quantity or Authority cannot substitute for missing original provenance; fractional rounding, backfill and defaults are forbidden. Read-only source corroboration at Revenue dc086be7d2d0e68007af3ddde4e19354036a3cb4 supports this mapping, with real persistence and writer proof still required.
Delivery's absent operational mirror must be actual SQL NULL and remain NULL. A populated mirror must be a positive Int32 equal to the authenticated full claim. Zero, undefined, missing rows, invalid or conflicting values deny. The predicate applies consistently at first compensation, finalization, current observation and deferred commit checks. It does not weaken full Association/Authority/evidence/receipt/writeback digests, original row/version/source checks, funding/debit/staged-fact checks, field whitelists or protection. Financial quantity remains required in compensation; it is deliberately absent from the closed Delivery-owned original snapshot.
Compensation correlation
All three prospective compensation events use the VERIFIED original successful ReceiptRef.event_id as common correlation_id and retain distinct canonical new event_ids. Existing actors, subjects, registered payloads and schema versions remain unchanged. Compensation keys stay in journals and the existing operational payload; shared correlation is neither deduplication nor financial authority. Delivery's operational outbox and Revenue's two financial outboxes remain atomic and once-only with their respective mutations, audits and immutable receipts. Replay cannot publish another event or rewrite historical bytes. Narrow event-permanence guards and consumer handling still require authentic implementation proof.
Clock, retirement branches and timing
assessment_revision orders only covered Delivery protected-source facts and captured staged facts. Every relevant local write advances it atomically or is denied; GET remains read-only. Each fresh resource verdict may change at equal local revisions. Signed-original retirement requires D1, fresh exact independently verified Revenue never_admitted proof, then D2 in one Sales monotonic attempt of at most10000ms. Each Delivery read independently obtains fresh Platform historical access and a coherent local protected observation.
Each complete response and identity/receipt/fence/assessment digest is verified before comparison. Require unchanged exact original identity and receipt/fence, compatible epoch, intact fence and all positive predicates; equal local revision; equal complete local projection excluding precisely assessment_revision/current_resource/observed_at/assessment_digest; and equal seven-field ResourceFacts excluding only evaluated_at. Metadata remains covered by each complete digest and freshness checks. An increased local revision or remote semantic change denies this attempt; a new complete attempt may establish a compatible baseline for the SAME immutable original. Regression, overflow or equal-revision local divergence is a producer clock fault requiring owner correction, never washed into a new positive baseline.
Descriptorless no-send retirement applies the SAME versioned two-fresh-observation comparison and complete original resource/receipt/fence checks, together with authentic permanent zero-authorized-send proof under Sales serialization. It cannot fabricate a signed descriptor, financial admission or financial settlement. Absence of that authentic permanent fence leaves the original unresolved. This bounded branch is explicitly accepted and does not borrow the signed-original financial proof.
All subsequent exchanges, reads, parsing, local serialization, append and final commit consume Sales' one remaining attempt budget. Each Delivery request uses its own timer from fresh Platform request through protected observation. No remote monotonic timestamp is transferred, no second-read timer restarts Sales' attempt, and no owner HTTP occurs under business locks. Remaining transaction/lock timeouts and rollback must enforce the final commit boundary. Remote ABA between snapshots and changes after D2 remain the expressly accepted residual; the pair is not an all-source clock, lease or exact-instant cross-domain fence. Stronger guarantees require a separately approved generation/fencing design.
Evidence and retained implementation gates
Delivery reviewed the exact assembled prose, policy, schemas, vectors and validation changes, with independent helper reviews for source/auth/quantity/correlation, clock/consumer semantics and closed schema/digest compatibility. The portable exact assembly passes36 offline checks;10 additional raw/canonical digest assertions against the frozen Delivery serializer also pass. Earlier Delivery38 original/quantity cases,7 schema/preservation checks and17 pair model cases remain bounded design evidence. These checks establish shapes, hashes and comparison semantics, not genuine issuer authority, producer provenance, SQL permanence, concurrent CAS, ingress, serving-role or production readiness.
Acceptance does not enable any runtime. Authentic prospective capture, narrow issued read, exact consumer byte/provenance retention, original quantity conversion/permanence, unchanged-null compensation/finalization, event/outbox/rollback/replay, all covered writers, both retirement branches and total timing after serialization remain integration gates. The paused ADR-0053 runtime's original_soft_response_hash versus canonical original_response_body_sha256 mismatch remains a later implementation correction, preserving immutable original bytes; it is not an ADR-0054 schema change or a reason to reopen the agreed design.
The ADR-0052 deadline2026-10-17T00:42:57Z and ADR-0053 maximum2026-10-17T03:32:35Z remain fixed. Delivery source remains clean at215da101ac58f5bb9d9b5def39cf1e80c977a3b1. No runtime source, policy, migration, database, deployment, production control or listener was changed for this review. ADR-0053/delivery/007 stays suspended pending explicit coordinator handback; a separate GET-only Coaching listener using final Platform57783 has not been launched.