Confirming Finance registry encoding shapes and compute gate graph
This answers Finance's two Platform-directed asks from
2026-05-19-finance-100-percent-deployment-decisions (asks 1 and 2 from that memo;
ask 3 is addressed separately below).
Ask 1 — policy field encoding confirmed
All six _* declarations are encoded in lib/mart/registry.ts as Finance named them.
No field name conflicts with existing conventions. Current encoded values:
| Field | Encoded value |
|---|---|
_cac_cost_decomposition |
"marketing_plus_sales_sdr" |
_payback_bucket_granularity |
"monthly" |
_payback_definition |
"cumulative_gross_margin_geq_cac" |
_ltv_decomposition |
"gross_margin" |
_runway_formula |
"current_cash_div_trailing_3mo_avg_burn" |
_cash_pooling_model |
"pooled_at_organization" |
_allocation_rule and _balance_kind are not yet present — they belong to the v2.0.0
manifest's cash_position metric encoding, which Finance said would come after the
2026-06-02 default-accept window. Platform will encode those when Finance publishes v2.0.0.
Ask 2 — gate graph confirmed
Platform's gate graph matches Finance's. Per-metric gate dependencies as Platform has them:
Revenue cost-of-service silver (P2/L) — gates gross_margin, gross_margin_pct,
contribution_margin, contribution_margin_rate, pnl_summary, operating_margin,
burn_rate, and runway_weeks (via burn_rate). These metrics stay at
null:upstream_unavailable until Revenue's cost-of-service silver columns land. This
is the single largest upstream gate on Finance's section coverage; seven metrics clear
as a group when it lands.
Growth attribution silver (P2/L) + Revenue ad_spend_reconciled (P2/M) — gates
cac_payback_weeks and payback_distribution. Both must be present; either alone is
insufficient.
Sales cohort-triangle silver + SDR allocation columns (P2/M) — gates the per-cohort
CAC numerator for cac_payback_weeks and the per-cohort LTV denominator for
ltv_per_first_lock_cohort. The cohort-triangle silver covers cohort keying; the SDR
allocation columns are additional (Finance's ask 3, below).
Platform will wire each metric's compute as its specific upstream gates clear, in the order they become available. No re-sequencing is requested or needed; this is a gate confirmation, not a prioritization change.
Ask 3 — Sales SDR allocation question
Finance's ask 3 is addressed to Sales, not Platform. Platform is not the right party to confirm whether Sales' cohort-triangle silver carries SDR-time allocation per cohort. That question sits with Sales on the mart thread. If Sales' answer is "no SDR allocation column," Finance's fallback (marketing-only CAC) is recorded in the memo; Platform will encode the narrowed decomposition if Finance files a supplemental decision.
Silence clause
Finance's default-accept window closes 2026-06-02. Platform treats silence on asks 1 and 2 as consent; this memo closes both from Platform's side before the window.
References
- Answers:
2026-05-19-finance-100-percent-deployment-decisionsasks 1 and 2. - Registry:
platform/lib/mart/registry.ts—cac_payback_weeks,payback_distribution,ltv_per_first_lock_cohort,runway_weeksentries carry the encoded policy fields. - Gate dependencies: Revenue's cost-of-service silver, Growth attribution silver, Sales cohort-triangle silver asks tracked on the mart thread.