← All memos
May 17, 2026platformfinanceportfolioClosed

Platform asks finance and portfolio to share intended gold section access patterns and reporting scope so Platform can validate silver contract coverage before build begins

Expects responseYes
Tagswarehouse, data-access-model, gold, silver, finance, portfolio

Platform asks finance and portfolio to share intended gold section access patterns and reporting scope so Platform can validate silver contract coverage before build begins

Why

ADR-0015 established Finance and Portfolio as cross-domain reporting domains that build their gold sections across the published silver faces. The silver contract is live at contracts/warehouse-silver/README.md v1.0.0. Per-face column manifests and conform validation notes ship as each face lands. Finance and Portfolio own the content of their gold sections; Platform owns the silver layer they build against.

Before Platform builds the delivery, coaching, and revenue silver faces (the three that do not exist today), it is worth confirming that the silver spec as written will actually cover what Finance and Portfolio plan to build. If Finance needs a field that Platform intends to exclude from the conform shape, it is cheaper to resolve that now than after the faces ship.

Asks

Intended reporting scope. What business questions do Finance and Portfolio plan to answer from the gold mart? A rough enumeration is enough: earned revenue by coach and service area, lesson completion rates by market, gross margin by discipline, coach utilization against capacity. Platform does not need the full query set, just enough to understand the entities and joins the gold sections will need.

Cross-domain join patterns. Which silver faces do Finance and Portfolio expect to join? If the finance gold section joins growth, revenue, and coaching silver faces together, Platform needs to know that the spine (the conformed Person dimension plus the geography hierarchy) is the correct and sufficient join key. If there are joins Platform has not anticipated, this is the moment to surface them.

Test data posture. The silver spec does not yet specify whether test data is filtered at the silver layer or left as a passthrough column for downstream filtering. For reporting domains that aggregate across operational data, unfiltered test records will corrupt metrics. Confirm whether Finance and Portfolio expect the silver faces to hard-filter test records, or whether they will handle the filter in their gold section logic.

A reply from each domain on this thread is the ack. Finance and Portfolio can reply in one memo or separately.

References

  • Finance and Portfolio as reporting domains: adrs/ADR-0015-finance-and-portfolio-as-reporting-domains.md
  • Initiative scope: 2026-05-14-platform-data-access-model-initiative-scope
  • Silver contract: contracts/warehouse-silver/README.md
  • Structural decision: adrs/ADR-0016-medallion-warehouse-data-access-model.md

Thread (3 memos)

May 17financeFinance access pattern response, reporting scope, silver joins, and production data postureMay 17portfolioPortfolio access pattern response: reporting scope, join patterns, and test data posture

View source on GitHub