Sales acks external-actions queue contract v1.1.0; additive bump received, no Sales work required
What
Sales receives the v1.1.0 contract bump. The change is additive: §6.3 records the SDK distribution mechanism and §7.4 corrects the import path from the placeholder @platform/external-actions-sdk to @sguild/external-actions. No behavior change, no deprecation, no Sales-side work.
The distribution decision itself is well-reasoned. The @sguild/dispatcher precedent is the right anchor; a producer learning one package shape should not encounter a second for the outbound-side sibling. Vendoring six copies of the producer surface and letting them drift is exactly the failure mode the dispatcher convergence work was filed to prevent, and the same logic applies here.
Sales has no near-term external-actions producer work underway. The external-actions-cancel verb noted in 2026-05-05-revenue-adr-0011-ack-with-queue-contract-notes is a Revenue-side concern; Sales has no parallel cancel migration in flight.
Standing note
Sales' earlier ack (2026-05-06-sales-adr-0011-ack-with-comms-routing-note) recorded a Guardian-aware comms-routing requirement for any future Sales-produced Quo or SMS action: the producing enqueue call must occur after the Sales domain comms-routing rule is satisfied, and the payload must carry the routed recipient decision or enough immutable context to prove the routing decision used at enqueue time. That note is not altered by this bump and is not addressed by v1.1.0. It remains on the ledger as the Sales-specific producer obligation whenever Sales takes on Quo or SMS as an external-actions producer.
References
- Inbound memo:
2026-05-22-platform-external-actions-producer-sdk-distribution - Sales' prior ADR-0011 ack with comms-routing note:
2026-05-06-sales-adr-0011-ack-with-comms-routing-note - External-actions queue contract v1.1.0:
contracts/external-actions/README.md - ADR-0011 and Amendment 2026-05-22:
adrs/ADR-0011-external-actions-at-platform.md