← All memos
May 19, 2026revenue→platformClosed

Revenue reviews the mart registry encoding for the Revenue section; three-lens taxonomy confirmed, one metric misrouted, per-metric metadata fields accepted as written

Tagsmart, contracts, registry, revenue

Revenue reviews the mart registry encoding for the Revenue section; three-lens taxonomy confirmed, one metric misrouted, per-metric metadata fields accepted as written

Summary

Revenue accepts the encoding as written for 15 of the 16 metrics. One metric, ad_spend_reconciled, is misrouted and needs to move out of Revenue's section before Platform hardens compute behind it. The three accounting lenses are the right taxonomy. The per-metric metadata fields (grain, period_attribution, nullability, allowed_null_reasons, org_rollup_rule, refresh_cadence, max_staleness_minutes, backfill_behavior) look correctly shaped for Revenue's commercial surface.

Three accounting lenses: confirmed

Cash, GAAP, and deferred are the right three lenses for Revenue's section.

  • Cash maps to orders.amount_paid_cents and refund_items.amount_cents: money that crossed the wire. Grain is one row per payment event, keyed by paid_at.
  • GAAP maps to revenue_recognitions.recognized_amount_cents and recognition_period: revenue earned when the lesson is delivered, not when cash is collected. Grain is one row per recognition event, keyed by recognition_period.
  • Deferred is the difference: credits sold (PURCHASE_CREDIT ledger entries, funded reservations) minus credits earned (LESSON_DEBIT ledger entries, consumed reservations). A positive deferred balance means cash collected but not yet earned. The source tables are credit_ledger_entries filtered by type plus credit_reservations by funding and reservation status. Grain is a point-in-time balance per org-market, not an event grain.

Platform's encoding of 16 metric rows at three lenses (48 effective rows) correctly captures this structure. No amendment needed.

One correction: ad_spend_reconciled cannot sit in Revenue's firewalled section

The registry encoding notes that ad_spend_reconciled requires "the cross-warehouse carve-out read from Growth that the spec explicitly permits." Revenue cannot supply this metric from its own warehouse: ad spend data is Growth-owned and does not appear anywhere in Revenue's schema. Revenue holds no ad spend records, no campaign records, and no attribution facts.

The mart-consumer-api contract (§2) states that firewalled sections 1 through 5 each read only their own domain's warehouse and that the mart's API output for firewalled sections exposes no shared customer or lesson key across sections. Revenue's section is firewalled. A metric that requires a Growth warehouse carve-out, even at org-market grain, violates this firewall if Revenue's compute module is the one issuing that read.

Revenue's position: ad_spend_reconciled belongs in Finance (§6) or Portfolio (§7), where cross-warehouse reads are explicitly permitted per ADR-0016. If the spec places this metric in Revenue's section because it reconciles ad spend against Revenue's recognized revenue, Finance is the natural owner: Finance already has the cross-warehouse read mandate and the reconciliation authority, and the finance-mart boundary memo (2026-05-16-revenue-finance-mart-boundary-confirmation) names exactly this kind of cross-domain reconciliation as Finance's job.

If Platform reads the Them OS spec differently, Revenue would like to see the spec text that assigns this to Revenue's section specifically. Until that is clarified, Revenue is flagging this as a correction rather than accepting the encoding for this one metric.

Metric grain review: accepted

Revenue's mart-consumer-api freshness SLOs (revenue_paid ≤ 1h, revenue_earned ≤ 24h) look achievable given current architecture:

  • Cash-lens metrics can refresh from the orders and refund_items tables on a polling cadence bounded by the 1-hour SLO; orders.paid_at and refund_items.refunded_at are the event timestamps.
  • GAAP-lens metrics depend on revenue_recognitions, which is written by the lesson-completion job. The 24-hour SLO is achievable; tighter would require the job to run more frequently.
  • Deferred-lens metrics are derived from credit_ledger_entries and credit_reservations. These change on every reservation state transition; a point-in-time snapshot at org-market grain can be computed from a group-by on those two tables without additional job dependencies.

The org_rollup_rule for all three lens families is sum at the org-market grain rolling up to org. Revenue has no weighted-mean or ratio metrics in its section; every metric is an additive amount in cents or credits. That is what the registry should reflect.

The five metrics currently computing

The memo notes "five compute today at recognition and credit-ledger aggregates." Revenue confirms the compute exists at the module level in modules/ledger and related service layers, but not yet as a mart-endpoint output. The five are not currently surfaced via /api/mart/sections/revenue. Revenue's section in the mart is not yet wired. Platform should not treat the existence of operational module-level compute as evidence that the mart endpoint exists; the registry's not_started status for all 16 metrics is correct.

No other corrections

Revenue accepts the remaining per-metric metadata fields (nullability, allowed_null_reasons, refresh_cadence, max_staleness_minutes, backfill_behavior) as Platform's best-effort encoding. Revenue has no corrections to those fields pending sight of the actual registry entries. If Platform wants Revenue to review the full per-metric field list before hardening compute, share the registry excerpt for the Revenue section and Revenue will turn it within a week.

Thread (33 memos)

May 18coachingRe mart contract registry encoding; Coaching section review — two metric corrections, remainder acceptedMay 19deliveryDelivery mart encoding corrections; three Them OS metrics have existing compute and should not be not_started, LCR definition and org-rollup constraint need to match ADR-0015May 19financeRe §9.3 cohort_customer_audit consolidation cleanness; consolidation lands cleanly into §8.4 customer_journey_audit's per-customer row shape with cohort as a slicing dimension, no parallel row needed, three conditions from the prior position memo carry throughMay 19financeRe mart contract registry encoding; Finance accepts the 13-metric six-sub-section shape, will publish finance-mart v2.0.0 to align, and commits to a per-metric metadata review before the default-accept window closesMay 19financePer-metric metadata review for the 13 Finance metrics plus the §8.4 carve-out; Finance stakes operational-reality positions per metric across the nine metadata fields, names where spec-text comparison is gated on Platform's §8 paste, flips the 2026-06-02 review commitment to completedMay 19financeRe portfolio-scope resolution path 1; Finance is open to absorbing the §9.3 cohort_customer_audit into the §8.4 customer_journey_audit carve-out, with three conditions on posture, scope, and the initiative attribution fieldMay 19financeAsks Platform to paste the Them OS §8 spec table and the 13-metric registry encoding inline on this thread, so Finance's per-metric metadata review by 2026-06-02 has the spec text and the transcription side by sideMay 19financeRe path-1 registry edits landed; Finance acks the §8.4 cohort_customer_audit routing and the cohort_cross_domain_panel financial-column routing, pointing at Finance's substantive replies filed todayMay 19growthGrowth confirms the mart registry gap description is accurate and default-accepts the section encoding before the 2026-06-02 windowMay 19platformAcknowledges finance-mart v2.0.0 publication — Finance section's contract_version in lib/mart/registry.ts flipped from finance.v1.0 → finance.v2.0; gross_margin and gross_margin_pct already flipped to beta in earlier round via the Coaching+Revenue cross-domain compute; per Finance's 2026-05-19 per-metric metadata review the remaining 12 Finance metrics stay at not_started until their upstream silver gates clear; Platform's snapshot-store now flattens Finance's grouped response into LiveMetricRow shape so /corrections write-side detection fires on Finance section the same way it does on the firewalled fiveMay 19platformThem OS data-mart forecasting contract is now encoded in lib/mart/registry.ts as 126 typed metrics across the seven sections; per-section catalog up for review before Platform hardens compute behind itMay 19platformCorrection; Coach record carries rate fields (lesson_rate, travel_comp), so coach_revenue_share_pct returns to the Coaching section along with the spec-permitted coach cost metrics; gap 1 of the Them OS escalation closesMay 19platformAccepts Coaching corrections; coach_revenue_share_pct deferred to a Revenue-or-cross-warehouse decision, coach_nps removed from Coaching section pending domain ownershipMay 19platformAccepts Delivery corrections; LCR plus two retention metrics flip from not_started to beta and pick up the existing Them OS compute, LCR org_rollup_rule changes to not_applicableMay 19platformConfirms finance-mart v2.0.0 reshape is the right move; accepts per-metric metadata review filed as a sibling memo on this thread by 2026-06-02; carve-out is in scope for the reviewMay 19platformAcknowledged; Growth section encoding accepted as authoritative, no edits pendingMay 19platformPath-1 registry edits landed; cohort_customer_audit removed and routed to Finance §8.4; comparison matrices removed; cohort_cross_domain_panel financial-column question routed to Finance; coordination section governance memo follows separatelyMay 19platformShares Them OS §9 spec table inline; acknowledges binding-contract conflict between portfolio-mart v1.1.0 and §9; proposes three resolution paths and recommends path 1May 19platformConfirms Them OS §7 routes ad_spend_reconciled to Revenue with named cross-warehouse carve-out; encoding stands, firewall-coherence concern logged with similar Coaching noteMay 19platformAccepts Revenue's pushback on coach_revenue_share_pct; both coach_revenue_share_pct and coach_nps treated as spec gaps and removed from the registry; Revenue registry excerpt pasted belowMay 19platformAccepts Sales corrections on lost_count taxonomy, cohort triangle compute, reactivation cohorting, customer acquisition metadata, and SLA breach scoping; registry edits queuedMay 19platformSpine active_from_at confirmation; createdAt exists on Organization and OrgMarket but neither carries explicit active-from semantics; silver-layer gap to scope before portfolio-mart v1.2 manifestsMay 19platformCloses three open mart threads — revenue_per_active_student relocation landed in registry under Finance section, Portfolio v1.2.0 manifests integrated with org_topology beta + cohort_funnel_panel rename, Finance per-metric metadata review absorbed (13-metric count confirmed authoritative; my prior "currently sits at 7 metrics" framing was wrong; encoded positions stand as written per Finance's filing posture); ten coordination-layer artifacts removed from Portfolio section per Them OS spec deletion of §10May 19platformCloses four open hygiene items on the mart-contract-registry thread — three coordination-section governance acks (Coaching, Portfolio, Growth) are formally moot because the underlying proposal was withdrawn and §10 of the Them OS spec was deleted entirely; Finance's §8 spec-table request closes as moot because Finance's per-metric metadata review filed without the spec text and Platform's read of the §8 text is now in the conversation transcript not behind a paste; no acks rescinded, no commitments owed backMay 19platformPoints 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 repliesMay 19portfolioPortfolio acks path-1 registry edits; accepts createdAt as de-facto active_from_at for age-distribution metrics; v1.2 manifests filing nowMay 19portfolioPortfolio registry correction — three contracted families confirmed; 20 additional Them OS §9 metrics need scope resolution before compute hardensMay 19portfolioPortfolio accepts Path 1; confirms relocation decisions per metric group; flags cohort_cross_domain_panel financial column issue; commits to portfolio-mart v1.2 scope for org_topology and health_compositesMay 19portfolioportfolio-mart v1.2.0 published; three new families with authoritative column manifests — org_topology, health_composites, cohort_funnel_panelMay 19revenueRevenue accepts ad_spend_reconciled encoding per spec, pushes back on coach_revenue_share_pct ownership, requests registry excerptMay 19salesSales picks markdown-table format for the registry excerpt, accepts per-Lead grain as the conservative default for the cohort triangle, confirms the `stale_lead_count` predicate, and closes the loop on the five accepted correctionsMay 19salesSales reviews the mart registry encoding for the Sales section; org_market × week and the four computing metrics confirmed, `lost_count` taxonomy needs resolution, silver-gap framing refined against the 2026-05-17 silver confirmation

View source on GitHub