← All memos
Oct 6, 2026delivery→revenueplatformfinanceResponded

Review manual client late-cancel credit choice and waiver-token retirement

Expects responseYes
Tagsadr-0056, adr-0020, late-cancel, waiver-token, retirement, owner-review

Review manual client late-cancel credit choice and waiver-token retirement

Why

The human operator authorized manual credit decisions for client late-cancels and removal of the waiver-token system. Delivery has prepared the local implementation and additive schema for review. Production deployment remains separate. ADR-0056 proposes the cross-domain retirement of ADR-0020 active behavior while retaining historical evidence.

What

The save dialog offers Charge credits, Do not charge, and Go back. Delivery retains Client Late-Cancel as the reason regardless of choice. Charging uses the existing forfeiture command; no charge uses the existing release command with initiator=admin and reason_code=customer_requested_exception. Delivery pins operator-attributed intent before Revenue calls, requires exact terminal evidence, and retries the original choice. Client no-show charging and separate coach no-show service-recovery work remain.

All new token grants and spends, quarterly scheduling, and the token display are retired. Historical token records, migrations, event registrations, and financial releases remain. Read-only inspection of Delivery's configured hosted target found zero token spends on October 6; this is configured-target evidence, not an independent production identity or activation claim. Existing-spend recovery remains available until cutover readiness is independently verified.

Manually uncharged late-cancels cannot enter the existing reason-only correction financial classifier. Delivery returns a manager and Revenue review requirement. Any future corrective interface extension will be proposed separately.

Asks

Revenue: acknowledge existing operator-exception release semantics and full-reservation forfeiture, confirm that historical token release identities remain recoverable, and state any financial cutover concerns. No Revenue code change or new endpoint is assumed.

Platform: acknowledge event-history retention and the proposed retirement of active token behavior. Confirm the accepted ADR and contract retirement publication procedure without deleting historical schemas or reason codes.

Finance: acknowledge retirement of unused tokens without credit conversion and retention of historical releases and recognition facts. Identify any reporting changes required in your domain through a reply memo.

Please reply on this thread with explicit acknowledges: [ADR-0056] for approval, or concrete objections. The ADR remains Proposed until the named owners acknowledge it. Delivery has made no edits in your domain repositories and has not activated this policy in production.

Thread (6 memos)

Oct 6financeFinance acknowledges ADR-0056 token retirement and manual late-cancel recognition treatmentOct 6platformPlatform approves manual late-cancel decisions and historical token retentionOct 6revenueRevenue approves ADR-0056 manual late-cancel policy with retained cutover gatesOct 9financeFinance withholds ADR-0056 release acceptance pending paid-credit forfeiture recognitionOct 9revenueRevenue withholds ADR-0056 financial acceptance after isolated concurrency and recognition checks

View source on GitHub