Platform accepts the additive weekly revenue-recognition grouping path for finance-mart

Short answer

Confirmed. Platform accepts groupings.revenue_recognition_weekly as an additive finance-mart grouping, and Finance is right not to derive the weekly report from cohort_summary. The existing cohort_summary compute intentionally emits one current-week observation per cohort today; it is not a clean weekly-period recognition source.

The weekly grouping should read Revenue recognition truth directly, following the same source policy as the existing monthly revenue_recognition grouping. Existing monthly rows stay unchanged.

Serving shape

Platform will wire the new grouping under GET /api/mart/sections/finance at groupings.revenue_recognition_weekly.

The served grain is one row per recognition_week x org_market_id, plus one organization rollup row per recognition_week x organization_id. That mirrors the additive pattern the current pipeline.deferred_revenue grouping uses: org-market rows first, then an org rollup with org_market_id: null and rollup_scope: org.

The row shape Finance proposed is accepted with one explicit Platform convention: include rollup_scope so consumers can distinguish org_market rows from organization rollups without inferring from null geography fields. recognition_week should use the ISO key shape IYYY-"W"IW, aligned to Revenue's recognized_at timing. reporting_period_grain is week.

The money columns keep the existing recognition policy:

• gross_recognized_revenue_cents sums non-contra recognition rows.
• contra_revenue_cents sums contra rows as positive contra.
• recognized_revenue_cents is gross minus contra.
• Service-recovery or adjustment rows without paid consideration do not become recognized revenue.

Exception columns should follow the existing manifest semantics. If the live Revenue silver face still lacks exception fields at the exact source object Platform reads, Platform will surface the same honest null coverage note rather than blocking the grouping.

Implementation

Platform will wire this as a small compute and registry change in lib/mart/sections/finance.ts, the finance section registry, and snapshot refresh where needed. The implementation should add a new weekly query over the same Revenue silver recognition source instead of reusing cohort_summary.

Because this is an additive grouping with no change to existing monthly rows, Platform reads it as a minor finance-mart surface addition. If Finance wants the formal contract artifact to carry finance.v2.2.0, Platform will mirror that in the registry when the grouping lands. This reply is enough for Platform to start the compute work; Finance can land the manifest patch in parallel or fold it into the same thread after Platform serves the first rows.

References

• 2026-06-15-finance-weekly-revenue-recognition-mart-ask
• contracts/finance-mart/revenue-recognition-rollup.md
• contracts/finance-mart/cohort-summary.md
• Platform compute: lib/mart/sections/finance.ts