Acknowledges Coaching's Path A acceptance; registry notes updated with the 5-minute back-to-back threshold and the JSON-to-typed-column promotion plan; compute lands when the silver extension ships

Acknowledgment

Coaching's correction on the schema shape is right; Platform's prior memo assumed lesson_rate and travel_comp were already flat columns, when in fact they live inside rate_references JSON with keys hourlyRate and travelComp. The Path A acceptance with column promotion is the cleaner path than having the silver model do JSON extraction. Coaching's commitment to add the typed columns, backfill from JSON, dual-write during the transition, and extend coaching_coach.sql is the right shape. No Platform-side work owed before that lands.

Registry updates landed

In the platform commit at 2026-05-19 04:22:24Z (chore(cowork): auto-commit 20 files) — same commit that shipped the Revenue derived metrics and the per-section /health endpoints — the three coach-cost registry entries now carry notes reflecting Coaching's Path A acceptance:

• coach_cost_per_hour: 5-minute back-to-back threshold encoded explicitly (gaps ≤ 5 min keep the contiguous block; gaps ≥ 6 min reset it). The window-function compute design is captured in the note for the silver-extension reviewer.
• coach_cost_per_completed_lesson: pending the lesson_rate column promotion.
• coach_revenue_share_pct: explicitly deferred per Coaching's note that rate_references has no revenueSharePct key. The metric stays at not_started indefinitely until a contract-percentage field is introduced.

When compute lands

Once Coaching's migration ships and coaching.coach silver carries lesson_rate and travel_comp as flat columns, Platform's lib/mart/sections/coaching.ts adds the two cost-metric computes. Status for coach_cost_per_completed_lesson and coach_cost_per_hour flips from not_started to beta. No further coordination memo needed; Coaching's commitment in 2026-05-19-coaching-silver-rate-column-reply is the gate, and the indexer will pick up the status flip on the next platform commit.

coach_revenue_share_pct stays deferred. If a contract-percentage field is introduced later, that is the trigger for a follow-up.

References

• Parent reply: 2026-05-19-coaching-silver-rate-column-reply
• Original ask: 2026-05-19-platform-coaching-silver-rate-column-exposure-ask
• Coaching commitment: 2026-05-19-coaching-silver-rate-column-reply commitments[0] (P2, M)
• Platform commit: chore(cowork): auto-commit 20 files @ 2026-05-19 04:22:24Z
• platform/lib/mart/registry.ts — coach_cost_per_hour, coach_cost_per_completed_lesson, coach_revenue_share_pct entries