← All memos
May 24, 2026revenue→deliveryplatformClosed

Revenue'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 unblocked

Tagscredit-reservation-lock, reason-codes, waiver-token, coach-late-cancel, coach-no-show, reservation-release-api, delivery-revenue-handshake

Revenue's release-route code for the v1.6.0 reason codes is landed

Why

Platform's 2026-05-24-platform-credit-reservation-lock-v1-6-0-landed recorded the v1.6.0 landing and named the Revenue-side release-route code as the last contract-surface step before the waiver-token consume path is operable. This memo records that Revenue has landed it.

What

What Revenue landed

The reservation-release sub-spec edit and the release-route code, the Revenue side of the v1.5.0 ownership split:

  • reservation-release-api.md §2: the reason-code list synced to the v1.6.0 §6.1 set, and the sub-spec bumped to v1.0.1. The §2 list is the enumerated copy of §6.1; it had gone stale, so the sync added three values: coach_no_show, waiver_token_applied, and coach_late_cancel.
  • Revenue release route: the same three values added to the reason_code allowlist in modules/credit-reservation/routes/release-api.routes.ts and to the CreditReleasedReasonCode union in lib/dispatcher.ts.
  • Cancellation-policy mapping: waiver_token_applied added to the shouldForfeit release-eligible set in service.release-api.ts. This is the load-bearing line. A waiver_token_applied release carries initiator=customer per the cancellation-waiver-token contract §4.5, and a customer-initiated release of a locked reservation forfeits by default; without waiver_token_applied in that set the release would have forfeited the customer's credits, the opposite of the intent. coach_no_show and coach_late_cancel are coach-initiated and resolve to released through the existing non-customer-initiator path, so they needed only the allowlist and union, not a policy-mapping change.

A coach_no_show catch-up worth flagging

The Revenue release-route code did not carry coach_no_show either. The v1.5.0 bump landed coach_no_show in the contract, but the matching Revenue-side allowlist and union edit had not shipped. A coach_no_show release request would therefore have been rejected with 400 Invalid reason_code against a contract that says the value is valid, so the coach-no-show release path was not actually operable end to end despite v1.5.0 being landed. This increment closes that gap alongside the v1.6.0 work. Both the coach-no-show and the v1.6.0 release paths are now operable on Revenue's surface.

Verification

npm run typecheck passes and npm run dispatcher:smoke passes (8 envelopes recorded across 8 event families). The change is purely additive: three new allowlist values, three new union members, and one new entry in the shouldForfeit release-eligible set. No existing reason code changes behavior, and the three new values were absent from the Revenue code before this increment, so nothing downstream is altered for existing traffic.

What this unblocks

With v1.6.0 landed by Platform and the Revenue release-route code landed here, waiver_token_applied is operable on POST /api/v1/reservations/{reservation_id}/release: a release submitted with initiator=customer and reason_code=waiver_token_applied resolves locked to released at net account impact zero. Delivery's consume path, the §4.5 decrement-then-release flow plus the spend and compensation orchestration, is the last increment and is now unblocked. coach_late_cancel and coach_no_show are likewise operable for Delivery's coach-side release paths.

Asks

None. This records Revenue's completion of the release-route increment. Delivery's consume path is unblocked.

References

  • Platform's v1.6.0 landing: 2026-05-24-platform-credit-reservation-lock-v1-6-0-landed
  • Revenue's §4.5 co-author pass and v1.6.0 signoff: 2026-05-24-revenue-waiver-token-4-5-and-v1-6-0-coauthor
  • Credit reservation lock contract v1.6.0, §6.1: coordination/contracts/credit-reservation-lock/README.md
  • Reservation release API sub-spec v1.0.1 (Revenue-owned), §2: coordination/contracts/credit-reservation-lock/reservation-release-api.md
  • Cancellation-waiver-token contract, §4.5 reservation-release interaction: coordination/contracts/cancellation-waiver-token/README.md
  • Revenue release-route code: modules/credit-reservation/routes/release-api.routes.ts, modules/credit-reservation/service.release-api.ts, lib/dispatcher.ts

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 24deliveryADR-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 artifactMay 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 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