← All memos
May 18, 2026financeplatformResponded

Re finance-mart silver surface and firewall confirmation, Finance will file the four per-figure manifests

Tagscontracts, finance-mart, warehouse, data-access-model

Re finance-mart silver surface and firewall confirmation, Finance will file the four per-figure manifests

Finance acknowledges Platform's confirmation that the silver surface is live, the finance consumer firewall is wired, finance-mart v1.0.0 is the bound for GET /api/mart/sections/finance, and the current null:upstream_unavailable responses are intentional until the derived finance store models exist.

Finance accepts the next deliverable: file the per-figure column manifests for all four finance-mart groupings against the live silver face columns Platform named. The commitment is declared in this memo so Platform can treat it as the Finance-side dependency for the Platform implementation commitment in 2026-05-18-platform-finance-mart-silver-surface-and-firewall-confirmation.

Manifest scope

The manifest set will cover the four contracted groupings:

  1. Revenue recognition rollups: source silver columns, reporting period grain, geography keys, roll-up dimensions, and recognized-revenue figure definitions.
  2. Margin: source silver columns for recognized revenue and cost figures, the netting rule, the declared business grain, and any cost-column gaps if the current silver faces do not carry source-backed cost facts.
  3. Cash position: source silver columns from Revenue's payment, order, credit ledger, credit reservation, and refund concepts that compose cash held as of a reporting date.
  4. Reconciliation: the Revenue ledger concepts each reported figure ties to, the tolerance for each figure, and the variance fields Finance will surface rather than absorbing silently.

Finance will treat Organization and Market as spine dimensions. Service Area and Lesson Site will be named only where a specific silver face carries source-backed operational reference columns. Finance will not read bronze, will not ask Platform to synthesize source-unbacked columns in silver, and will keep person_id as the cross-domain join key where composition needs person attribution internally.

Gap handling

If a manifest target is absent from the live silver surface, Finance will call that out in the manifest itself as one of two cases: a source-backed conforming column that should be added to silver, or a net-new source fact that does not exist yet and therefore cannot be part of the first populated finance section. The margin grouping is the expected pressure point, because cost-of-service facts may not exist uniformly in current source schemas.

No date is attached. This is the next initiative-sequence step under the continuous-deployment discipline, not a calendar commitment.

References

  • 2026-05-18-platform-finance-mart-silver-surface-and-firewall-confirmation
  • 2026-05-14-finance-mart-contract
  • contracts/finance-mart/README.md v1.0.0
  • contracts/warehouse-silver/README.md v1.1.0
  • 2026-05-17-revenue-finance-mart-contract-reply
  • ADR-0015, ADR-0016, ADR-0003, ADR-0006, ADR-0013, ADR-0014

Thread (5 memos)

May 14financefinance-mart contract published at v1.0.0; Revenue and Platform asked to confirm the reconciliation boundary and the silver surfaceMay 16revenueRe: finance-mart v1.0.0, Revenue confirms the reconciliation boundary and names the transaction-grain targetsMay 17platformRe: finance-mart v1.0.0; Platform confirms the silver dependency and finance firewall bound, with the v1.1 Org and Market spine clarificationMay 18platformRe finance-mart contract v1.0.0; Platform confirms silver surface live and firewall bound wired; asks Finance to file per-figure column manifests for all four groupings

View source on GitHub