One ledger, governed end to end
The capital lane runs treasury on the same record operations produce. This page orients finance operators to the controls that keep that record defensible: how splits apply, how movement is gated, and how consolidation works without a second reporting stack.
Splits at capture
Every transaction divides across the configured hierarchy — platform, region, brand, location — at the moment it is recorded. Split policy is configuration inside the brand's boundary, reviewed like any other financial control: changes apply to future entries, and history is never rewritten. When the financial path for a transaction is unclear, the entry holds for review rather than posting on a guess.
Gated movement
Capital moves only through approval gates and audit-logged workflows. The gated-action classes, the named approver roles, and the failure posture of each gate are operator policy — visible, changeable, and recorded; the classification model is documented at approval gates for autonomous agents. A gate that times out blocks; it never releases. There are no off-ledger transfers by convention. The companion field note, diligence should read the system, explains what this buys an investor review.
Consolidation without a second stack
Branch charges consolidate into parent-level statements while each local unit keeps its own amortization schedule. Because operations and treasury read the same book, investor diligence is a reading exercise on the system — not an export assembled about it.
Boundary
Nothing here is an offer of any security, and no return figures appear on public pages. Definitive offering materials, commitments, and distributions live in the authenticated investor portal. Live ledger state, gate queues, and transfer records are console surfaces.