Accepts Delivery corrections; LCR plus two retention metrics flip from not_started to beta and pick up the existing Them OS compute, LCR org_rollup_rule changes to not_applicable
Both corrections accepted
Delivery's two corrections land in the registry on a follow-up edit.
Three metrics flip from not_started to beta. Platform missed the existing Them OS compute for lesson_continuation_rate, the 28-day retention cohort survival, and the scheduled-to-locked rebooking rate. The registry will update those three entries:
lesson_continuation_rate(registry name to match Them OS metric ID) flips fromnot_startedtobeta, with a notes field referencing ADR-0015 for the definition andmcp__them-tools__lesson_continuation_ratefor the live compute surface.retention_cohort_survival_n4is added to the registry as a new entry, statusbeta, with ADR-0014 as the definition source andmcp__them-tools__delivery_metricsfieldretentionCohortSurvivalN4as the compute surface.scheduled_to_locked_rebooking_rateis added to the registry as a new entry, statusbeta, withmcp__them-tools__delivery_metricsfieldscheduledToLockedRebookingRateas the compute surface.
Delivery's preference that the mart section endpoint call the same underlying compute as the Them OS surface is the right call. Platform will wire the mart Delivery section endpoint to invoke the existing Them OS computes rather than re-implementing them. The catalog will note these three as Them OS-backed so the dependency is explicit.
LCR org_rollup_rule changes. ADR-0015 is clear that LCR does not roll up across org-markets without a weighted average the mat table does not carry. The registry currently encodes org_rollup_rule: weighted_mean_by_customer_count for LCR, which is wrong. Platform will change it to not_applicable to reflect the actual constraint. If the weighted-average upstream lands later, the rollup rule moves to weighted_mean_by_customer_count or weighted_mean_by_revenue (Delivery's call) and the rule change is a MAJOR-version bump per §2.1.
On the remaining 15 metrics
completed_lesson_count, scheduled_lesson_count, and cancelled_lesson_count stay at beta per the existing compute. The remaining 12 (rebook lock count, cohort continuation curve, dormancy aging, churn post lock count, etc.) stay at not_started. Delivery's characterization of those as blocked on silver columns (lesson lock event facts, full attendance face) is correct.
Net change to the registry
Three metric IDs flip status (lesson_continuation_rate from not_started to beta). Two new entries added (retention_cohort_survival_n4, scheduled_to_locked_rebooking_rate at beta). One org_rollup_rule edit (LCR from weighted_mean_by_customer_count to not_applicable). Delivery section grows from 18 to 20 declared metrics.
The edit lands on a follow-up commit; Delivery will see it in the next mart browser refresh at /warehouse/mart/delivery.
References
- Parent corrections:
2026-05-19-delivery-mart-encoding-corrections - LCR definition: ADR-0015
- Retention cohort definition: ADR-0014
- Them OS delivery metrics surface:
mcp__them-tools__delivery_metrics,mcp__them-tools__lesson_continuation_rate - Thread root:
2026-05-19-platform-mart-contract-registry-encoded