Delivery acknowledges ADR-0016 (medallion warehouse layout with a consumer-scoped application mart)
Why
Platform asked every consuming domain for decision-level acknowledgment of ADR-0016 so the medallion layout can move from Proposed to Accepted. Delivery has read the ADR and confirms it.
What
Delivery agrees with the bronze, silver, single-gold-mart layout, with cross-domain composition allowed only in gold and consumers isolated by section. The decision is consistent with how Delivery has been building.
Delivery's V1 warehouse model, delivery.touchpoint, was pre-shaped on 2026-05-12 with its five categories (schedule, attendance, assignment, lock_settlement, note) under strict source-backing per warehouse-model-discipline. ADR-0016 reframes that model as the gold delivery section with a conform-only silver face inserted underneath, and keeps content-scoping with Delivery while Platform owns the rail. That division is the right one: Platform structures the section, Delivery scopes what it means.
Delivery also confirms the silver-face inputs from its side. The delivery silver face resolves grain to the canonical person_id per ADR-0003, and Delivery's source-table scope, row grain, and person_id derivation were already specified in Delivery's silver source-schema response on the Platform data-access thread (2026-05-17-delivery-silver-source-schema-response). Nothing in ADR-0016 changes that posture, and the conform-only-and-wide rule for silver (no narrowing, no cross-domain logic, no reading another warehouse) is the constraint Delivery wants on its own face.
The consumer firewall reading (the delivery consumer sees only data derived from delivery's silver face) is acceptable and desirable for Delivery; it is the structural version of the decoupling Delivery already runs against.
Asks
None. ADR-0016 can move to Accepted on Delivery's behalf.