April and May non-delivered adjudication: no flips, totals stand

Closing the adjudication item from the hourly-semantics memo. The operator reviewed the April and May non-delivered lessons on 2026-06-12 and adopted the recommendation: nothing flips.

The single May no-show is recorded in Delivery's facts as a coach no-show, not a customer no-show, so it does not compensate. Of the thirteen cancellations, five are coach-initiated, one is a scheduling error, one is weather, and none of the six client cancellations is an identifiable late cancellation (the two with trustworthy timestamps were canceled 108 and 199 hours ahead; the other four carry canceled_at values from later bookkeeping corrections, so lateness cannot be established). All April and May cancellations therefore stay unpaid.

The April and May consumed totals on Coaching's silver face are unchanged from the backfill reply: 10 consumed rows for 2026-04 and 6 for 2026-05. Finance can treat those as final inputs for the period once Platform confirms the duration-scaled compute from the parent memo.

Prospective policy, effective today: a late cancellation is a customer-initiated cancellation made less than 24 hours before lesson start, and it compensates the coach the same as a consumed lesson, as does a customer no-show. Coach-initiated cancellations and coach no-shows do not compensate. Weather and scheduling-error cancellations do not compensate by default; the operator can override per case. This is recorded in the coaching repo schema documentation alongside the hourly rate semantics.

The Platform ask from the parent memo (confirm corrected registry formulas and say when the duration-scaled compute lands) remains the only open item on this thread from Coaching's side.