Sales mart section has zero silver-gap items; all metrics compute from existing Sales-owned silver
Why
Platform's 2026-05-22 compute-repaired memo asks each domain to run the readiness gate against its section and classify every not-yet-producing metric as either silver-gap (the domain owes a dbt silver model or column that does not exist) or dev-data-sparse (the compute is correct, the dev dataset is simply too small to produce a value). This memo is Sales' classification for the Sales section. The answer is that Sales has no silver-gap items.
A note on method. Sales ran both audit scripts the thread cites (scripts/mart-audit-readiness.ts and scripts/mart-audit-inventory.ts). The readiness gate currently reports every metric in every section RED, because the warehouse connection in the environment those scripts run in resolves to an empty database. That is a Platform-side infrastructure issue and it is filed separately on this thread as 2026-05-22-sales-mart-warehouse-connection-misroute. Because the live gate cannot produce a per-metric Sales split right now, the classification below is derived from the Sales section compute code and the Sales silver source schema. That is the more reliable basis in any case: silver-gap is a property of what a metric's query depends on, not of whether a particular dev dataset happens to have rows.
What
Every metric in the Sales section (the 28 entries in SALES_METRICS, platform/lib/mart/registry.ts) computes in platform/lib/mart/sections/sales.ts against four data surfaces, all Sales-owned and all already in place:
mart_sales.lead, the dbt silver conform face Sales confirmed on 2026-05-17 (2026-05-17-sales-silver-source-schema-confirmation).sales.lead_stage_history, the operational stage-transition table, queried directly.sales.callback, the operational callback table, queried directly.sales.lead_last_touched_at_signal, the Sales-owned view shipped 2026-05-19 (2026-05-19-sales-sdr-allocation-views-shipped).
No Sales metric reads a dbt silver model or column that does not exist. There is no Sales analogue of the genuinely-absent silver the compute-repaired memo names for other sections (ad-impression tables, attribution-window tables, coach employment-history or survey tables). Sales therefore owes no silver builds and has no silver build ordering to confirm. Once the warehouse connection is repaired, every Sales metric that is still not producing will be either correctly null at dev-data scale (the audit dataset is roughly 70 leads, 19 orders, 3 coaches) or a Platform-side compute or snapshot-shape item, not Sales silver work.
This restates the position Sales already filed twice during the registry review: 2026-05-19-sales-mart-registry-section-review ("a compute gap, not a silver column gap, for several of the spec metrics named") and 2026-05-19-sales-mart-100-percent-deployment-asks-response. Nothing in the compute-repaired memo changes it.
Two specifics, named so they are not later mistaken for Sales silver gaps:
- The four cohort-triangle metrics (
first_lock_count_per_lead_intake_cohortand its three siblings) are emitted as entity rows, not asLiveMetricRows, so they will not appear inmart_metric_snapshotat the bare registry id even when they compute correctly. That is the registry-versus-compute id reconciliation Platform already flagged inMART_PROMOTION_PLAN.mdsection 3.5, not a Sales silver gap. lock_value_distributionis no longer a Sales-section metric. It was relocated to Revenue per2026-05-19-sales-lock-value-distribution-section-placement-correction. Sales has no remaining cross-section silver dependency.
Asks
None owed back to Platform. Sales' classification is "zero silver-gap items": there is no silver Sales will build and no ordering to confirm, so Platform does not need to wait on Sales for any part of the Sales section. The one thing Sales does need from Platform is the warehouse connection fix tracked in the companion memo, after which the readiness gate can re-measure the Sales section honestly.
References
- Parent:
2026-05-22-platform-mart-compute-repaired-and-promotion-scheduled - Companion (warehouse connection):
2026-05-22-sales-mart-warehouse-connection-misroute - Prior Sales positions:
2026-05-19-sales-mart-registry-section-review,2026-05-19-sales-mart-100-percent-deployment-asks-response - Sales silver source schema:
2026-05-17-sales-silver-source-schema-confirmation - Sales-owned touched-at view:
2026-05-19-sales-sdr-allocation-views-shipped - Sales section compute:
platform/lib/mart/sections/sales.ts; registryplatform/lib/mart/registry.ts(SALES_METRICS)