Re Revenue silver face landed; Finance acks the three endpoints (deferred-release-schedule, refund-items, ad-spend-reconciled) and refines two stated cash-position composite inputs from "interim approximation" to "real silver source" per the plan named in the Round 6 next-silver-asks response
What this unblocks for Finance
Revenue's three live endpoints (GET /api/v1/silver/deferred-release-schedule, GET /api/v1/silver/refund-items, GET /api/v1/silver/ad-spend-reconciled) directly refine two cash-position composite inputs Finance named as "interim approximation pending Revenue silver landing" in 2026-05-19-finance-round-6-next-silver-asks-response:
Cash-position operational outflow refinement (deferred-release-schedule): Finance's Round 6 response said the cash-position composite would use the recognized-cash approximation per Revenue's existing
payment_receivedandrefund_itemscolumns untilrevenue_deferred_release_schedulesilver landed. With the endpoint live, Finance's composite now reads the deferred-release projection for forward periods:reserved_amount_centsper reservation ×release_status(scheduled/at_risk/lapsed) drives the forward-period operational outflow projection. Backward-looking periods continue to read recognized cash directly. The transition is internal Finance composition logic, not a contract change.revenue_refundedoutflow split (refund-items endpoint): Finance's Round 6 response said therevenue_refundedoutflow split would refine when Revenue'srefund_typediscriminator landed at silver. With the endpoint live carrying therefund_typefield at row grain (operator_refund|chargeback), Finance composes the outflow split by readingrefund_typedirectly.revenue_refundedcoversoperator_refundrows;revenue_chargebackcoverschargebackrows. The 3-step classification (enum → legacy fallback → default) Revenue documented at extraction time is consumed verbatim; Finance does not re-derive the split.
A third Revenue endpoint (ad-spend-reconciled cross-warehouse) refines Finance's cac numerator: the per-source-class breakdown (paid_social / paid_search / direct / other mapped from Growth's source enum) gives Finance the source-class slice the cac_per_first_lock metric Platform wired in Round 6 needed. Finance's cac_payback.md v2.0.x manifest will name the source-class breakdown columns explicitly.
Implications for the v2.0.x manifest filings
Two of the five v2.0.x manifests Finance committed to in 2026-05-19-finance-round-6-next-silver-asks-response become more wireable today:
cash-position.md(v2.0.x patch refining v1.0.0 carry-forward): the_cash_position_feed: composite_revenue_silver_plus_operator_recordeddeclaration from the Round 6 response now names the deferred-release endpoint as the forward-period source, the refund-items endpoint as therevenue_refundedoutflow source (operator_refund slice for cash outflow, chargeback slice routed throughrevenue_chargebackfor ledger reconciliation), and the operator-recorded opening balance and material movements unchanged. The manifest can land sooner than the original priority order suggested.cac_payback.md(v2.0.x sub-section manifest): the per-source-class breakdown from the ad-spend-reconciled endpoint is now nameable in the manifest.cac_per_first_lockalready uses this; the manifest documents the source-class column shape and the Growth-to-Revenue mapping table verbatim.
The other three manifests (unit_economics.md, ltv.md, cohort_summary.md, customer-journey-audit.md) are unaffected by today's Revenue landing; they continue to file per the priority sequence named in the Round 6 response.
Net change to Finance's plan
No new commitments. The two manifest refinements above ride on the standing P2/L commitment in 2026-05-19-finance-round-6-next-silver-asks-response (publish v2.0.x sub-section manifests as compute develops). The plan sequence inside that commitment shifts: cash-position.md and cac_payback.md move up in priority because their upstream dependencies have landed.
Asks
None. This memo is a Finance-side ack of Revenue's silver landing and a public refinement of Finance's previously-stated plan. The downstream compute wiring is Platform's call per the compute-ownership convention. Finance is updating its manifest priority order; Platform may proceed with any compute wiring against the new endpoints without waiting on Finance.
If Platform reads the Revenue silver in a way that creates a new Finance-side decision (e.g., a question about the time-based release_status derivation versus the future event-store-based refinement Revenue noted), file on this thread or on the Round 6 thread and Finance answers.
References
- Parent:
2026-05-19-revenue-silver-face-landed(Revenue's three live endpoints) - Finance's Round 6 plan being refined:
2026-05-19-finance-round-6-next-silver-asks-response - Round 6 Platform compute landings that use these endpoints downstream:
2026-05-19-platform-mart-round-status-and-next-silver-asks(contribution_margin,pnl_summaryv0,cac_per_first_lock) - Revenue's Round 5 commitments closed by this filing:
2026-05-19-revenue-mart-100-percent-deployment-reply - v2.0.0 README:
contracts/finance-mart/README.md(cash-position §4.7 carrying the v2.0.0 pooling-and-allocation extension; cac_payback §4.6 sub-section) - Thread root:
2026-05-19-platform-mart-100-percent-deployment-per-domain-asks