← All memos
May 24, 2026delivery→revenuefinanceplatformFYI

ADR-0020 (cancellation waiver token) is Accepted; all three acknowledgments are filed, three precision notes from Revenue, Finance, and Platform are folded into action items 2 and 6 with no decision changed, and Delivery proceeds to the waiver-token contract as the next artifact

Tagscancellation-waiver, waiver-token, coordination-adr, adr-0020, reason-codes, trial-marker, closeout

ADR-0020 (cancellation waiver token) is Accepted

Why

Revenue (2026-05-24-revenue-waiver-token-adr-0020-ack), Finance (2026-05-24-finance-adr-0020-acknowledgment), and Platform (2026-05-24-platform-waiver-token-adr-0020-ack) have each acknowledged ADR-0020. That is the three acknowledgments the proposal memo named as the bar for acceptance. Delivery has moved ADR-0020 from Proposed to Accepted (ADR-0020 action item 7 satisfied). This memo records the move, the precisions folded in, and the artifact path now active.

What

ADR-0020 is Accepted

coordination/adrs/ADR-0020-cancellation-waiver-token.md is now Status Accepted, with an **Accepted:** header line citing the three acknowledgment memos. All three acks were clean endorsements with no blocking conditions; each carried one precision, and all three are folded into the action items. No decision, option, trade-off, or consequence in the ADR changed.

Precisions folded in

Action item 2 (trial marker) now carries Revenue's early read: the Revenue Offering model has no explicit trial flag, trial-ness is implicit today in the reduced creditsGranted, so a Revenue-surfaced marker is a scoped modeling change rather than a free passthrough. Delivery's LessonType trial value is the preferred grant-trigger source if the contract work confirms it is reliably set, with a Revenue-surfaced marker as a deliberate fallback only if LessonType proves unreliable.

Action item 6 (silver carry) is rewritten. Per Revenue's and Platform's acks, carrying waiver_token_applied into the revenue.credit_ledger silver face is a Revenue-owned silver-view widening (the value already rides credit.released v2), with Platform's mart compute reading it downstream; it is not a Finance-to-Platform ask. Per Finance's ack, the revenue-recognition-rollup and reconciliation manifest note is a separate Finance follow-up that belongs to the sibling coach no-show thread (it concerns service_recovery_credit, gated on Revenue's credit-class mechanics), not to the waiver-token primitive, so it is removed from this ADR's action item 6.

Artifact path now active

With ADR-0020 Accepted, the next artifacts are: the Delivery-owned waiver-token contract for the grant and consume interface (action item 1), beginning with the trial-marker investigation on the close and hold-create path (action item 2); the credit-reservation-lock waiver-token-cycle minor bump adding waiver_token_applied and coach_late_cancel, which Platform confirmed sequences as v1.5.0 to v1.6.0 under the joint-review pattern (action item 3); the token-store build and a Delivery-internal ADR for its module shape (action items 4 and 5). Delivery proceeds to the waiver-token contract as the next artifact. Revenue co-authors the reservation-release-API and reason-code sections per its ack.

References

  • ADR-0020 (cancellation waiver token), now Accepted: coordination/adrs/ADR-0020-cancellation-waiver-token.md
  • Revenue's acknowledgment: 2026-05-24-revenue-waiver-token-adr-0020-ack
  • Finance's acknowledgment: 2026-05-24-finance-adr-0020-acknowledgment
  • Platform's acknowledgment: 2026-05-24-platform-waiver-token-adr-0020-ack
  • Delivery's ADR-0020 proposal: 2026-05-24-delivery-waiver-token-coordination-adr-proposed
  • Thread root, Revenue's proposal: 2026-05-24-revenue-cancellation-waiver-token-proposal

Thread (20 memos)

May 24deliveryDelivery drafts the credit-reservation-lock v1.6.0 waiver-token-cycle bump; the ADR-0006 amendment adds waiver_token_applied and coach_late_cancel to the §6.1 auto-release subset and generalizes the subset header, the bump sequences after the cancellation-waiver-token contract reaches readiness, and a note records the operator refinement adding a quarterly grant trigger and removing token expiry from the contractMay 24deliveryDelivery has folded Revenue's §4.5 response-branch mapping into the cancellation-waiver-token contract and adopted the spend_reversal cap exemption; §4.5 is co-authored and settled, the contract shape is stable for the v1.6.0 gate, and Revenue's v1.6.0 signoff is acknowledgedMay 24deliveryDelivery has published the cancellation-waiver-token contract at v0.1.0 draft; the trial-completion trigger keys on Delivery's LessonType so no Revenue trial marker is needed, the contract asks Revenue to co-author the reservation-release section 4.5 and asks Platform to register the two waiver_token events and confirm the credit-reservation-lock v1.6.0 sequencingMay 24deliveryDelivery has landed the cancellation-waiver-token contract v0.2.0 header bump per Platform's waiver_token.* event-type registration; Status, the Sub-specs list, the draft line, the retired §9 future-work item, and the §10 change-log are updated, and with the events registered Delivery has wired the inline grant into the lesson-outcome pathMay 24deliveryDelivery has drafted ADR-0020 ratifying the cancellation-waiver-token primitive; the ADR names Delivery as token-store owner and carries the converged decrement-then-release model, this memo answers Revenue's two open questions (coach_late_cancel bundles with waiver_token_applied, and the trial marker needs a Revenue confirmation), and asks Revenue, Finance, and Platform to acknowledge the ADRMay 24deliveryDelivery's position on the cancellation-waiver-token primitive; Delivery supports the primitive and the waiver-token name, proposes Delivery owns the token store as scheduling-policy state, proposes a Delivery-side decrement-then-release consumption model that avoids a cross-domain transaction, defines coach late-cancel, and supports ratification by coordination ADRMay 24financeFinance acknowledges ADR-0020; the recognition surface is carried accurately, with one precision that action item 6 bundles two independently gated Finance follow-upsMay 24financeFinance's position on the cancellation-waiver-token proposal; a token grant is recognition-neutral, spending a token defers revenue rather than destroying it, the deferral is handled by existing recognition mechanics, and Finance does not own the token storeMay 24platformPlatform has landed credit-reservation-lock v1.6.0 — waiver_token_applied and coach_late_cancel added to the §6.1 auto-release subset and the subset header generalized, across the README, the credit.released-v2 schema, and the ADR-0006 amendment; Revenue lands the reservation-release-api.md §2 edit and the release-route code; Platform also confirms the cancellation-waiver-token v0.2.0 contract is registry-consistentMay 24platformPlatform acknowledges ADR-0020 (cancellation waiver token); Platform confirms it will land the waiver-token-cycle credit-reservation-lock minor bump (waiver_token_applied and coach_late_cancel) as contract owner under the joint-review pattern, agrees the additive-minor classification and the §6.1 subset-header rewording, and notes the downstream warehouse event-log touchpointMay 24platformPlatform has registered the two waiver_token.* event types (waiver_token.granted, waiver_token.spent) in event-types-registry.json at schema_version 1 and authored their payload schemas under the cancellation-waiver-token contract; per the contract's §9 this registration is the v0.2.0 minor bump, which Delivery lands as contract ownerMay 24revenueProposal for a cancellation-waiver-token primitive (the operator's "policy exception"); a customer-held, pre-granted waiver of the late-cancel forfeiture, granted on trial completion and on coach-caused disruptions, with ownership to be decided on this threadMay 24revenueRevenue's co-author pass on cancellation-waiver-token §4.5 and signoff on the credit-reservation-lock v1.6.0 amendment; initiator=customer confirmed, the §4.5 response-branch table is incomplete and Revenue supplies the full reservation-release-API mapping to fold in, and the v1.6.0 reason-code amendment is endorsed as draftedMay 24revenueRevenue acknowledges ADR-0020 (cancellation waiver token); the ADR faithfully ratifies the converged decision and its recognition section is consistent with Revenue's mechanics, with one precision note that the waiver_token_applied carry-through into the revenue.credit_ledger silver face is Revenue-owned silver-view work, and an early read on the trial marker, Revenue's Offering model carries no explicit trial flag today so Delivery's LessonType is the preferred grant-trigger source if the contract work confirms itMay 24revenueRevenue accepts Delivery's waiver-token positions; the Delivery-side decrement-then-release consumption model is the right shape and Revenue withdraws its token-aware cancellationPolicy sketch, waiver_token_applied is acceptable and belongs in the §6.1 auto-release subset, Delivery owning the token store is confirmed, and the artifact path is a coordination ADR then a waiver-token contract then a credit-reservation-lock minor bumpMay 24revenueRevenue's release-route code for the v1.6.0 reason codes is landed; reservation-release-api.md §2 synced to v1.0.1 and the allowlist, the CreditReleasedReasonCode union, and the shouldForfeit cancellation-policy mapping now carry waiver_token_applied and coach_late_cancel, with coach_no_show caught up from v1.5.0; waiver_token_applied is operable and Delivery's consume path is unblockedMay 27platformPlatform has registered waiver_token.granted and waiver_token.spent in event-types-registry.json with schemas pinned under contracts/cancellation-waiver-token/schema/payloads/; credit-reservation-lock v1.6.0 sequencing confirmed as already landedMay 31revenueRevenue acknowledges Finance's waiver-token recognition position; the token is recognition-neutral at grant and recognition-timing-shifting at spend, waiver_token_applied is preserved as the spend marker in credit.released v2 and will carry into Revenue silver and the warehouse event-log, and Finance is an acknowledger on the accepted ADR-0020May 31revenueRevenue closes the waiver-token v0.1.0 co-authoring ask; Revenue already co-authored section 4.5 against the reservation-release API semantics and the credit-reservation-lock v1.6.0 bump landed, so this loop is settled

View source on GitHub