The outcome you are walking toward
A diligence briefing you can give without collapsing MCV.CAPITAL into "another fund admin or treasury app." You leave able to name what this lane owns as an agent-authority vertical — not a product storefront — how it sits on Business OS, which public docks carry the substrate hops, and what Catalyst Capital is allowed to ask of every movement — without inventing AUM, IRR, settlement rates, or kit inventory you have not seen.
Read this first: agent-only, not a storefront
MCV.CAPITAL is an agent-only lane. There are no hardware kits, no physical organism, and nothing to install on site. This page is not a catalog of sellable kits, POS devices, cameras, or edge nodes. The public silo is MCV.CAPITAL — an authority surface for capital & treasury workflows on the shared substrate. If a briefing treats Capital as a shopping cart or a plug-in appliance beside Business OS, stop and reframe: the product on this lane is the agent mandate, not a bill of materials.
Meet the broader agent team on Agents. Authority still sits on the shared floor: irreversible classes stay gated; brand scope fails closed; reconstructability lives in the audit trail. Counsel walks that story through Verify what an agent is allowed to do and governed agent boundaries.
Catalyst Capital — the agent on the lane
Catalyst Capital is the named primary agent of the capital vertical. Mandate: settlement integrity, treasury signals, risk flags, and capital allocation support. Signature question of every movement: is the capital path clean, authorized, and fully evidenced?
It is designed to live inside settlement and treasury loops — hierarchical splits at capture, policy-gated transfers, LP intake on the same record operators run — not as a month-end spreadsheet the finance team rebuilds after the fact. Shared teammates enrich context; Catalyst Capital owns the capital-lane mandate.
What the capital lane specializes (honest domains)
Public posture on the capital silo organizes around operating domains — diligence vocabulary, not a weighted scorecard:
- Hierarchical splits — multi-tier splits (platform · region · brand · location) designed to calculate at capture, not reconcile after.
- One governed record — operations and treasury read the same book; diligence is designed to read the system, not a data-room export.
- LP capital intake — investor onboarding, allocations, and distributions on the same record as operations.
- Policy-gated movement — capital moves only through approval gates and audit-logged workflows — no off-ledger transfers by convention.
- Consolidated reporting — branch charges consolidate into parent-level statements while local units keep their own schedules.
Named-vendor battle cards stay internal. Public differentiation stays category-level. Metering and fee posture for operators is Stand up royalty and fee metering across brands — still not a kit SKU list.
Substrate docks Capital depends on
Capital is a specialized orchestration on the MCV substrate. Public docks you can open in a briefing:
- Mesh — the interconnect fabric that keeps locations and treasury surfaces on one living network. Interconnect fabric is not data fabric.
- Synapse — real-time settlement and risk-signal loops between nodes.
- Cortex — judgment with policy gates on capital movement and allocation support.
- Forge — outcomes that turn treasury experience into better methods under governance.
Pulse / Aria complete the chain narratively; Mesh, Synapse, Cortex, and Forge are the docks to name aloud first when the question is "where does capital authority live?" The signal-order walkthrough is Walk the six-system substrate chain. Composition of agents, verticals, and Franchise OS is Name what the organism is made of.
What this lane deliberately does not sell
- No hardware kits, no STORE kit tiers, no POS / camera / edge-node product claims.
- No "buy the capital appliance" framing — this is an agent-authority lane on Business OS, not a standalone product shelf.
- No present-tense claim that every LP workflow or split hierarchy ships at equal maturity on day one without a governed rollout.
If someone asks for a physical kit path, point them at the physical verticals (Fit / Rest / Realty / Build) and keep Capital on the agent story.
How to use this leaf in a briefing
- Open the silo first: MCV.CAPITAL.
- Name Catalyst Capital and the four mandate phrases before any demo narrative.
- Say the honesty line aloud: agent-only — no hardware kits, no physical organism, nothing to install on site.
- Walk Mesh → Synapse → Cortex → Forge before any "AI treasury" slide.
- Push autonomy claims back to approval gates and evidence — never to invented AUM or IRR theater.
- Pair with the counsel sibling when the deal spans practice workflows: Brief Codex Counsel without mistaking it for a practice-management storefront.
Non-goals for this leaf
- No AUM, IRR, yield, or settlement-rate claims; no invented customer logos.
- No kit sales theater, hardware SKUs, or STORE inventory language for this lane.
- No named-vendor battle cards.
- No claim that Capital is a purchasable appliance independent of Business OS.
When Catalyst Capital is clear, continue composition via organism composition and counsel review via diligence resources.