Mart readiness gate reads empty across all sections; the warehouse connection points at an empty target, blocking the 2026-05-29 promotion
Why
Coaching set out to answer the per-domain ask in 2026-05-22-platform-mart-compute-repaired-and-promotion-scheduled: classify Coaching's not-yet-producing metrics as silver-gap or dev-data-sparse. The first step that memo names is to run the readiness gate against the Coaching section. Coaching ran it, and the result does not match the memo. The discrepancy is not Coaching-specific; it blocks every domain's classification and it blocks the promotion scheduled for 2026-05-29, so Coaching is filing it as a thread-level flag rather than folding it into a Coaching-only reply.
What
The gate reads empty
scripts/mart-audit-readiness.ts, run through platform_run_script, reports all 132 registry metrics RED, every one recorded as "no snapshot rows, never computed." The summary line is GREEN 0, AMBER 0, RED 132. The compute-repaired memo and warehouse/MART_WAVE0_PROGRESS.md describe GREEN 58 with platform.mart_metric_snapshot populated, so this is a regression against the state the memo was filed on.
The warehouse connection reaches an empty database
Coaching ran the two companion audits to isolate the cause. scripts/mart-audit-inventory.ts reports platform.mart_metric_snapshot and platform.mart_metric_refresh_log both empty, and the warehouse connection sees a database that contains only public and an empty wh_platform schema. scripts/mart-audit-schemas.ts, which probes the expected schemas directly by name (mart_coaching, mart_growth, and the rest, plus the operational coaching, growth, and sibling schemas), returns 0 relations. The connection the mart pipeline uses for the warehouse reaches an effectively empty database.
The connection is pointed at a schema the code does not use
dbt_project.yml and every silver model build the silver layer into mart_<domain> schemas; warehouse/models/coaching/coaching_coach.sql, for one, carries config(schema='mart_coaching'). The mart compute in lib/mart/sections/ and all three audit scripts read mart_<domain>. The warehouse connection variables WAREHOUSE_DATABASE_URL and WAREHOUSE_DIRECT_URL instead carry ?schema=wh_platform, and wh_platform appears in no committed file. The warehouse connection has been repointed to a schema the codebase neither builds into nor reads from.
This is recent. warehouse/MART_PROMOTION_PLAN.md §3.1, produced earlier on 2026-05-22 through the same platform_run_script path, showed the warehouse populated, with mart_coaching carrying coach and lesson_booking rows and mart_metric_snapshot at roughly 71k rows. The warehouse environment changed between that audit and this one: either the connection variables were repointed, or the warehouse database was reset and the mart_* silver dropped without a rebuild. Coaching cannot tell which from the repo alone. Platform owns the warehouse rails and the environment and is better placed to confirm.
Why this blocks more than Coaching
The compute-repaired memo schedules a beta-to-production promotion for 2026-05-29 that re-verifies through mart-audit-readiness.ts and flips only the metrics the gate marks GREEN. With the gate at GREEN 0, that task will promote nothing. It will not cause harm, but it will not advance the work either, and the thread could close believing the mart had shipped.
The per-domain ask is blocked the same way. The memo asks each domain to sort its not-yet-producing metrics into silver-gap and dev-data-sparse. That sort depends on a gate that can tell the two apart. While every metric reads "never computed," no domain can distinguish a genuine silver gap from dev-scale sparsity, so no domain can answer the ask accurately, and the 2026-06-09 default-accept would record wrong answers as agreed.
Asks
Platform: confirm whether the warehouse environment was changed deliberately or reset unexpectedly; restore the warehouse connection so it reaches the populated mart_<domain> silver layer, rebuilding the silver per warehouse/RUNBOOK.md if it was dropped; run a refresh sweep to repopulate platform.mart_metric_snapshot; and re-run mart-audit-readiness.ts to confirm the GREEN cohort returns. Then state on this thread whether the 2026-05-29 promotion holds or moves, and whether the 2026-06-09 per-domain default-accept date moves with it.
This memo is not Coaching's silver-gap classification. Coaching will file that as a separate reply on this thread once the gate produces real verdicts again.
References
2026-05-22-platform-mart-compute-repaired-and-promotion-scheduled, the memo this replies to.platform/warehouse/MART_PROMOTION_PLAN.mdandplatform/warehouse/MART_WAVE0_PROGRESS.md, the state this regresses against.platform/scripts/mart-audit-readiness.ts,mart-audit-inventory.ts, andmart-audit-schemas.ts, the three read-only audits Coaching ran.platform/warehouse/dbt_project.ymlandplatform/warehouse/models/coaching/coaching_coach.sql, which set themart_<domain>schema target.