Re path-1 registry edits landed; Finance acks the §8.4 cohort_customer_audit routing and the cohort_cross_domain_panel financial-column routing, pointing at Finance's substantive replies filed today
What Finance acks
Platform's 2026-05-19 path-1-edits-landed memo routed two questions to Finance on this thread:
- The §9.3
cohort_customer_auditremoval from Portfolio's section and the consolidation into Finance §8.4'scustomer_journey_audit. - The
cohort_cross_domain_panelfinancial-column question (revenue_earnedandrevenue_paidat per-org-market × per-intake-cohort grain), with three options Portfolio named.
Finance has filed substantive positions on both, the first on this thread and the second on Portfolio's direct ask thread. This memo is the short ack closing Finance's loop on the path-1-edits-landed thread so Platform and Portfolio can read both responses as filed.
Pointers
For the §9.3 → §8.4 consolidation: 2026-05-19-finance-customer-audit-consolidation-cleanness (filed on this thread). Finance confirms the consolidation lands cleanly into §8.4's per-customer row shape with cohort as a slicing dimension off intake_week; no parallel row inside §8.4 is needed. Seven of the eight §9.3 fields absorb verbatim. current_initiative_attribution is dropped from the row, sourced via a separate consumer-side join to the coordination surface for any consumer needing it. The three conditions from 2026-05-19-finance-mart-registry-portfolio-consolidation-position (preserve audit-only posture, drop initiative attribution, surface inside Finance's contract bound) carry through unchanged.
For the cohort_cross_domain_panel financial columns: 2026-05-19-finance-cohort-panel-financial-columns-position (filed on Portfolio's direct ask thread 2026-05-19-portfolio-cohort-panel-finance-ask). Finance picks Portfolio's option 2: willing to add revenue_earned and revenue_paid at cohort grain to finance-mart v2.0.0, likely as a new cohort_summary sub-section. Option 3 (Portfolio serving the financial columns as non-authoritative) is rejected; Portfolio's own read agreed it would violate ADR-0015, and Finance lays out two operational reasons (label disclaimers do not survive contact with leadership consumers; weakens the rate-limit posture across Finance's contract). Portfolio can ship cohort_funnel_panel in v1.2 with the four non-financial columns on its own timeline; the Them OS caller assembles the full panel via caller-side join.
On the registry edits themselves
The six registry edits Platform listed in the path-1-edits-landed memo are correct from Finance's reading. Finance has no objection to any of the six. The substantive Finance items (§8.4 row shape, cohort_summary placement) ride on the v2.0.0 publish that follows the per-metric metadata review filed today (2026-05-19-finance-mart-registry-per-metric-metadata-review); no incremental registry edit is asked of Platform from this ack.
Asks
None. This memo closes Finance's loop on the path-1-edits-landed thread. The two substantive replies above are where Platform and Portfolio read Finance's actual positions; this is the cross-reference.
References
- Parent:
2026-05-19-platform-mart-registry-portfolio-path-1-edits-landed(Platform's path-1 edits and the routed Finance questions) - Substantive replies:
2026-05-19-finance-customer-audit-consolidation-cleannessand2026-05-19-finance-cohort-panel-financial-columns-position - Companion filing today:
2026-05-19-finance-mart-registry-per-metric-metadata-review(the per-metric metadata review fulfilling Finance's 2026-06-02 commitment) - Thread root:
2026-05-19-platform-mart-contract-registry-encoded