Portfolio reply to 100%-deployment per-domain asks — ack, no domain-side silver work owed; all manifests filed; Platform's sequencing recommendation below
Short version
Portfolio's section has no not_started metrics gated on Portfolio-side silver work. All three v1.2 manifests are filed (org-topology.md, health-composites.md, cohort-funnel-panel.md); the four asks below are accepted as written; all wiring is Platform's job. One open question about org_market_id slug conformation is carried forward from the v1.2 publish memo and is still awaiting Platform's reply.
Accepts (all four as written)
Ask 1 — Wire compute for the three v1.1.0 families (P2/M)
cross_market_performance, cross_discipline_performance, and portfolio_level_funnel_health are already at beta. Platform owns the compute wiring. Portfolio's contract input is contracts/portfolio-mart/ v1.1.0 manifests (unchanged in v1.2). The seven-day soak clock starts once compute is live and no contract drift is detected; Portfolio has no action that gates this.
Accepted as written.
Ask 2 — Surface org_market_id as conformed silver columns (P3/M)
growth.touchpoint.org_market_id, revenue.credit_reservation.org_market_id, and delivery.attendance.org_market_id as conformed slug columns remove Portfolio's spine-join derivation overhead for the cohort_funnel_panel and org_topology families. Platform owns this work; it is not a blocker per the memo (Portfolio can derive via spine join in the compute logic until the column is conformed). The ask is listed as P3 and is confirmed as non-blocking in Portfolio's v1.2 publish memo.
Accepted as written. Portfolio's cohort-funnel-panel.md already documents both paths (conformed column or spine-join derivation) so Platform can implement whichever is available.
Ask 3 — Wire compute for the six org_topology entries at beta (P2/S)
The org_topology manifest is now at contracts/portfolio-mart/org-topology.md (v1.2.0). Platform noted this is gated on org_market_id slug shape consistency (ADR-0019). Portfolio's manifest already uses {org_slug}-{market_slug} slug format per ADR-0019, so no ambiguity on Portfolio's side. Platform can proceed once ADR-0019 settles the slug shape.
Accepted as written.
Ask 4 — Wire compute for cohort_funnel_panel (P2/M)
The manifest is at contracts/portfolio-mart/cohort-funnel-panel.md (v1.2.0). Silver inputs, grain, composition rules, and the caller-side join pattern with finance-mart cohort_summary are all specified. The three source faces (growth.touchpoint, revenue.credit_reservation, delivery.attendance) each require an org_market_id column; the manifest's "Known coverage gaps" section specifies the derive-via-spine-join fallback if the slug column is not yet conformed on those faces.
Accepted as written.
No domain-side silver work owed
Portfolio owns no silver face. Every silver input Portfolio reads is authored by another domain. The v1.2 publish memo named three potential gaps (org_market_id slug columns on growth, revenue, and delivery silver faces); those are P3 asks on those domains per the deployment memo, not Portfolio-side work. Portfolio's contribution in this round was filing the v1.2 manifests, which is complete.
Platform's recommended implementation sequence
Per the health-composites.md manifest's "Known implementation sequence" section, and consistent with the dependency graph:
org_topology— pure spine reads, no silver face involved; can start as soon as ADR-0019 slug shape is confirmed. Six entries currently atbeta.cross_market_performance,cross_discipline_performance,portfolio_level_funnel_health— v1.1.0 families already atbeta; compute needs to go live to start the seven-day soak. Parallel with or immediately afterorg_topology.cohort_funnel_panel— depends on growth, revenue, and delivery silver faces having the required columns. Can start once those silver gaps are assessed and the spine-join fallback path is confirmed.health_composites— implement last; depends on the v1.1.0 families having live data for the same period and slice before composite materialization is meaningful. Do not fliphealth_compositesentries tobetauntil constituents are live.
One open question still awaiting Platform reply
The v1.2 publish memo (2026-05-19-portfolio-mart-v1-2-published) asked Platform to confirm whether the silver faces carry org_market_id as a conformed slug column or whether Portfolio must derive it via spine join at gold section time. That question is still open. Platform's answer determines which compute path Portfolio's sections use for cohort_funnel_panel and which path Platform encodes in lib/mart/sections/portfolio.ts. Platform does not need to wait for Portfolio's approval on this — a reply to the v1.2 publish memo with Platform's confirmation is the only remaining ask.
References
contracts/portfolio-mart/v1.2.0 — org-topology.md, health-composites.md, cohort-funnel-panel.md (all new in v1.2)contracts/portfolio-mart/v1.1.0 — cross_market_performance, cross_discipline_performance, portfolio_level_funnel_health (unchanged)2026-05-19-portfolio-mart-v1-2-published— v1.2 publish memo; carries theorg_market_idslug question still awaiting Platform replylib/mart/registry.ts— Platform's compute registry; Portfolio entries currently atbeta(v1.1.0 families) andbeta/not_started(v1.2 entries per the publish memo's registry-update asks)