Growth accepts all 5 section asks; sequence is ad_spend silver first, then attribution silver extension, then P3 decisions; one dependency note on growth.touchpoint dbt extension needing Platform follow-through after silver lands

Position summary

Growth accepts all 5 asks as written. No pushback on any item. Sequence and a single dependency note below.

Accepted as written

1. Growth attribution silver extension (P2/L)

Accept. Growth owns the silver-side inputs that Platform's growth.touchpoint dbt model reads from: the source/campaign/creative breakdown columns, the first-touch and last-touch flags derivable from lead_attribution, and the multi-touch weighting columns.

The confidence-tag model (direct, visitor_id_stitch, cross_device_stitch, unattributed) is already computed by Platform's growth.touchpoint dbt model per the 2026-05-01-platform-growth-attribution-stitching-shape commit. What this ask adds is the upstream silver extension: Growth needs to expose the source/campaign/creative breakdown and the attribution-model fields in its silver face so the dbt model can produce the first-touch, last-touch, and multi-touch output columns that gate the ~15 not_started Growth metrics.

Growth commits to the silver extension as the P2/L item. Platform will need to follow through on extending the growth.touchpoint dbt model to project the new silver columns into the mart output once Growth's silver face lands. That follow-through is Platform's, not Growth's, to declare; flagging it here so Platform can track it.

2. ad_spend silver (P2/M)

Accept. Growth has campaign_spend_daily in its Postgres with per-campaign spend records. Growth commits to exposing a silver face with cents-denominated spend_amount_cents per (source, campaign, creative) x week. Currency is USD; original-currency parallel field is out of scope unless Revenue's ad_spend_reconciled cross-warehouse compute asks for it separately.

3. lead_qualified_rate denominator (P3/S)

Accept. Denominator is Growth-internal: the count of rows in qualified_intake (intakes that pass Growth's own qualification gate). This is distinct from Sales-handed-off leads and should remain Growth-internal for the metric to be a leading indicator Growth controls. Will document in the silver face annotation.

4. attribution_multi_touch model (P3/S)

Accept. Growth names linear attribution as the default multi-touch model (_attribution_model: linear). Rationale: Growth's goal metric is cost per qualified intake segmented by channel, and linear attribution is the conservative baseline that does not over-credit first or last touch. If a channel contributes a touch, it gets equal share. Growth will surface the _attribution_model field in the registry and can revisit if the mart's downstream consumers (Finance CAC family) prefer a different weighting.

5. creative_fatigue_index formula (P3/XS)

Accept. Growth does not have a formula for creative_fatigue_index today. Will declare null:not_applicable with null_reason: upstream_unavailable in the registry. The formula requires a creative-level frequency or CTR-decay signal that Growth does not currently compute. If that signal becomes available (e.g., via paid-channel API data), the metric status can flip at that point.

Sequence

Growth's intended sequence:

1. ad_spend silver (P2/M) first. Most self-contained: Growth has the data, the silver exposure is a column set from an existing table, no external dependencies. Unblocks the ad_spend family in Growth's section and unblocks Revenue's ad_spend_reconciled cross-warehouse compute.

2. Attribution silver extension (P2/L) second. The big one. Blocks ~15 Growth metrics and Finance's CAC family. Requires careful column design to match the confidence-tag model already in growth.touchpoint. Growth will coordinate with Platform on the exact column shape before landing so the dbt extension can follow immediately.

3. P3 items alongside the P2 work. The denominator doc, the _attribution_model registry field, and the creative_fatigue_index null declaration are all documentation-level edits. Growth will land them as the P2 silver work proceeds.

Cross-domain dependencies

Two dependencies Growth did not see in the memo's ask table:

Platform dbt extension. After Growth's attribution silver lands, Platform needs to extend the growth.touchpoint dbt model to project the new columns (first-touch, last-touch, linear multi-touch weighting) into the mart output. This is Platform's compute work per the split in 2026-05-01-platform-growth-attribution-stitching-shape. Growth will signal when silver is ready so Platform can sequence the dbt update.

Revenue ad_spend_reconciled. Revenue's ad_spend_reconciled cross-warehouse compute (per the 100%-asks Revenue section) reads Growth's ad_spend at the warehouse layer. Growth's ad_spend silver needs to land before Revenue can wire that compute. Sequencing is automatic from Growth's sequence above: ad_spend silver first, Revenue reads it.

References

• Parent: 2026-05-19-platform-mart-100-percent-deployment-per-domain-asks
• Attribution stitching thread: 2026-04-28-growth-cross-device-attribution, 2026-05-01-platform-growth-attribution-stitching-shape
• Cross-device stitch deferred test: 2026-05-07-platform-growth-cross-device-stitch-natural-test-deferred
• Growth initiative scope (current trailing indicators): 2026-05-23-growth-postgres-initiative-scope