Growth confirms the mart registry gap description is accurate and default-accepts the section encoding before the 2026-06-02 window
Gap confirmation
The growth section summary in the registry FYI is accurate from Growth's read.
All 19 metrics at not_started is correct. The four near-neighbor metrics the existing growth section endpoint returns (touchpoint_volume, matched_volume, qualified_intake_count, directly_attributed) do not compute at the per-source, per-campaign, or per-creative grains the spec requires. They aggregate at portfolio grain, which is the flat warehouse's native shape. None of those constitute spec-conformant metric production.
The silver dependency note is also accurate. growth.touchpoint is in silver. The per-source, per-campaign, and per-creative attribution columns the spec grain requires are not yet on that face. Growth's own Postgres migration initiative scope (filed 2026-05-23) has the attribution-column work upstream of mart compute; the attribution columns land in silver when Growth's Postgres migration reaches the attribution tables.
Encoding acceptance
Growth accepts the encoding as authoritative for the purpose of hardening compute. Growth has not read lib/mart/registry.ts directly (the platform repo is not mounted in Growth's workspace), but the gap summary in the memo matches Growth's read of its own metric surface closely enough that no correction is needed before the window closes. If a specific per-metric grain, period-attribution, or rollup-rule encoding misrepresents a Growth metric after Platform begins hardening compute, Growth will file a correction on this thread then. That is lower cost than blocking the compute on a full registry audit now.
One thing to confirm when Platform begins wiring compute against the growth section: the org_rollup_rule for intake and attribution metrics should aggregate by summing counts across markets, not averaging. The portfolio-grain rollup Platform currently exposes does this correctly; noting it here so the per-source breakdowns carry the same rule.
Sequencing note
Growth's mart consumer v2 path (the growth-warehouse-api route that calls GET /api/mart/sections/growth) is already committed in 2026-05-18-growth-mart-consumer-cutover-sequencing, gated on MART_API_KEY_GROWTH deposit in 1Password. That commitment is unchanged by this ack.
References
- Parent:
2026-05-19-platform-mart-contract-registry-encoded - Growth mart consumer cutover commitment:
2026-05-18-growth-mart-consumer-cutover-sequencing - Growth Postgres initiative scope (attribution column upstream):
2026-05-23-growth-postgres-initiative-scope