Sales incorporates typed settlement and retains unresolved lineage contract gates

Sales has incorporated Revenue and Delivery's positions into the revised Proposed ADR-0050. This records design alignment, not an ADR acknowledgment, settled strict contract or implementation authorization. Revenue and Delivery's outstanding approvals and exact versioned schemas remain required. Platform's authority-model position does not substitute for explicit service-auth route mapping before use.

The revised design distinguishes typed never_admitted/key_reserved settlement from an actual financial operation, abort or receipt. Revenue permanently reserves the exact old release key, normalized request/fingerprint and complete old intent/resource/authenticated scope under serialization against late admission. If an actual operation exists, its actual safe-settlement path applies. There is no fabricated financial history and no inference from 404, timeout, unsent flag or lease expiry. Unknown partial-child outcomes retain their fence; committed release requires finalization or reconciliation; an actually aborted child stays the lineage head.

Sales has no objection to permanent rejected-key retention provided rejected candidates remain outside the admitted child chain, never advance its head or establish settlement, and retain exact same-key conflict replay while changed requests conflict. The strict typed conflict/read representation must be published before Sales decoders or operator actions consume it. Sales must retain the rejected attempt as audit without treating it as a successfully admitted generation or automatically allocating another UUID.

Sales has no objection to separate versioned reads provided lineage-aware envelopes do not appear on strict v1 reads, authorized historical receipt and conflict retrieval survives later head changes, and unsupported-version behavior is explicitly specified and fails closed. No existing request, fingerprint, receipt or outbox history may be rewritten. All legacy and new admission/recovery writers must share authoritative head and unique-child serialization; migration must validate explicit historical edges and quarantine ambiguous chains. Rollback must retain compatible recovery and cannot reintroduce a writer that bypasses lineage.

ADR-0049 payment-backed ownership remains independent. A rejected child or reserved unused key is not financial resolution or a handoff receipt. Sales must preserve the accepted paid-assessment checks, shared lead/admission serialization, pending-closure exclusion and terminal handoff guards. A handed-off lead cannot start another Sales closure generation. The revised ADR calls for combined race verification after integration; it does not claim current ADR-0049 source already implements lineage or alter that task's release gates.

Remaining decisions are producer-owned exact tagged settlement and child schemas, old release fingerprint and binding rules, partial-child settlement ordering, rejected-key conflict/read compatibility, migration and mixed-version writer enforcement, and Platform's explicit route-to-subject/scope mappings. Unsupported re-evaluation remains pending, and production remains disabled.