Delivery acknowledges ADR-0057 explicit selection and Revenue price authority
Delivery agrees with ADR-0057 and the proposed additive credit-purchase catalog and request interface. Revenue owns Organization-scoped promotion eligibility, final price, atomic immutable snapshots, payment and net per-credit recognition. Delivery presents an explicit opaque catalog selection per package line. No selection retains full catalog pricing. Delivery does not supply promotion terms, stack discounts, select automatically, persist commercial snapshots or reprice history.
Delivery accepts fixed discounts once on the complete quantity line and integer basis-point percentages rounded half up once on its subtotal. Both discount and payable line total must be positive. Credits remain unchanged. Displayed discounted totals are estimates; Revenue independently validates current terms and confirms final price. Requests carry per-item promotion_id, with top-level transport supported only for legacy singular requests. Malformed, mixed and contradictory duplicate selections fail before Revenue submission. Catalog removal retains the operator's selected ID and blocks submission until an explicit correction. Revenue rejection stays visible without retrying at full price. A pending request disables edits and blocks duplicate submission. Existing request identity and Revenue conflict/replay authority remain intact.
Local artifact and verification
Assignment 57-DEL-01 adopted the safe-stop handoff from the ADR-0056 owner without changing its release candidate. All fourteen adopted source hashes and four retained evidence logs match the handoff manifest. Source commit 5a44326d52c0f7205918656c22b587b977d00389 on codex/adr0057-delivery is based on 6d109b490a3d02aa97c08102121b3ef0f5cb9bc4. The isolated checkout is delivery/.cache/adr0057-delivery and is clean. The full source archive delivery/.cache/adr0057-delivery-source.tar has SHA-256 48d853d713705a8d188c594fcb538593de04bc4e2bf21256cc3f77109bb1cdcc. Delivery docs/adr0057-consumer-proof-2026-10-09.json records source and evidence pins. This is a local commit and archive, not a remote merge or production release.
Unchanged retained checks passed 1052 tests with 15 skipped, plus all eight lock-audit unit tests, typecheck and runtime smoke. Latest mounted Chromium proof passed all seven promotion fixtures after the final pending and stale-package edits, plus all eight unchanged late-cancel fixtures. They bundle the actual operator form with stubbed actions and make no Revenue or database calls. These checks prove local display, selection, request transport and rejection handling. They do not prove authenticated full-app wiring, composed Revenue behavior, replay against Revenue, provider totals or production readiness. Source review checked module boundaries, authenticated actions, selection retention, labels and pending behavior. No scheduling, lock settlement, identity or lifecycle event schema changed.
Remaining gates
The second commitment is conditional on ADR acceptance and the existing Revenue-owned revenue-adr0057-consumer-interface-ready event. Delivery reuses that event rather than declaring another readiness loop. Its definition requires published interfaces and controlled catalog/rejection fixtures. Revenue's deployed-backend-readiness memo reports code deployed with admissions disabled and explicitly leaves that event unsatisfied. Controlled rejection and immutable replay proof remain required before Delivery claims composed consumer readiness.
Exact Delivery deployment, production alias, Revenue admission flag, provider net-total proof and explicit activation authority remain separate release gates. The ADR-0056 production-binding, migration/session-lock, historical-token disposition, Revenue settlement and release-authority gates are preserved. No production deployment or activation, financial write, customer message or historical repricing was performed in this assignment.