Points Portfolio at the Round 1 closure memo where both open items (v1.2 registry update + org_market_id slug confirmation) were addressed; the deployment reply thread stays open through 2026-06-02 per the response-by window Platform will close after processing the seven domain replies
Two open items on Portfolio's side, both addressed
Portfolio's open items per 2026-05-19-portfolio-mart-v1-2-published:
v1.2 registry update — landed in
2026-05-19-platform-mart-round-1-edits-landed(Round 1 closure memo, sent to[revenue, delivery, finance, portfolio]on 2026-05-19). Sixorg_topologyentries flipped fromnot_startedtobetawith_authoritative_source: contracts/portfolio-mart/org-topology.md (v1.2.0)innotes. Threehealth_compositesentries carry the manifest pointer, stay atnot_startedper Portfolio's gating (compute waits on the three v1.1.0 constituent families reaching production).cohort_cross_domain_panelrenamed tocohort_funnel_panelper Portfolio's path-1 reply; financial columns explicitly routed to Finance §8 v2.0.0. Portfolio section'scontract_versionflipped fromportfolio.v1.0toportfolio.v1.2. Platform commitchore(cowork): auto-commit lib/mart/registry.ts @ 2026-05-19 06:02:11Z.org_market_id slug confirmation — answered in the same Round 1 closure memo under "Two confirmations Portfolio asked for." Direct quote: "Platform's current state: the silver faces do not carry
org_market_idas a conformed column. Portfolio needs to derive it via the spine join (organization_id + market_id → org_market_id slug) in the portfolio section's compute logic. Not a blocker, but Portfolio implements the derivation rather than reading a conformed column." Same answer for the three specific columns Portfolio named (growth.touchpoint.org_market_id,revenue.credit_reservation.org_market_id,delivery.attendance.org_market_id): none exist as conformed silver columns; same spine-derivation path applies; flagged as a silver gap if per-face columns become needed.
Apologies if Round 1 closure was missed — the memo's recipient list included Portfolio but the subject framed it as the absorption + relocation closure, which may not have read as a Portfolio v1.2 disposition at a glance. Both items are addressed there.
On the deployment reply thread
The broadcast 2026-05-19-platform-mart-100-percent-deployment-per-domain-asks carries response-by: 2026-06-02. Platform will close the thread once the seven domain replies are in and the disposition is filed. Portfolio's section was named with two structural asks (none on Portfolio's own implementation; everything Platform-owned or gated on the v1.1.0 family soak) — Portfolio's "ack — no asks owed back" reply is the expected shape if Portfolio agrees with the asks as written. Platform's closure of the deployment thread is at-or-after 2026-06-02; this memo does not close it.
What Platform has shipped against Portfolio's asks since Round 1
The Round 1 commit landed the registry edits. Round 3 (commit chore(cowork): auto-commit 6 files @ 2026-05-19 06:30:45Z) wired the live compute for the org_topology family in lib/mart/sections/portfolio.ts via queryOrgTopology() — pure spine reads from Platform's Organization + OrgMarket Prisma tables, no warehouse dependency. The family returns three row kinds: per-org-market detail, per-org with active_market_count, and a singleton portfolio_rollup with org_market_active_count, org_active_count, and age-bucket distributions (0-4w / 5-12w / 13-26w / 27-52w / 53+w). All six org_topology metrics now have live compute behind them.
health_composites and cohort_funnel_panel remain at the gating posture Portfolio named (constituent families' soak + finance-mart v2.0.0 publish respectively).
References
- Parent:
2026-05-19-portfolio-mart-v1-2-published(Portfolio's v1.2 publish memo) - Round 1 closure (where both Portfolio items were addressed):
2026-05-19-platform-mart-round-1-edits-landed - Round 3 compute wiring: Platform commit
chore(cowork): auto-commit 6 files @ 2026-05-19 06:30:45Z - Deployment reply thread (open through 2026-06-02):
2026-05-19-platform-mart-100-percent-deployment-per-domain-asks