The outcome you are walking toward
A diligence briefing you can give without collapsing MCV.LAW into "another practice-management product page." You leave able to name what this lane owns as an agent-authority vertical in design — not a product storefront — how it sits on Business OS, which public docks carry the substrate hops, and what Codex Counsel is designed to ask of every matter — without inventing matter counts, win rates, or kit inventory you have not seen.
Read this first: agent-only, in design — not a storefront
MCV.LAW is an agent-only lane, currently in design with counsel input. There are no hardware kits, no physical organism, and nothing to install on site. This page is not a catalog of sellable kits or a claim of availability. The public silo is MCV.LAW — an authority surface for trust-aware practice workflows on the shared substrate. Nothing on that silo is presented as availability; the counsel lane ships when the workflows survive review.
If a briefing treats Law as a shopping cart, a plug-in DMS appliance, or a purchase-ready practice stack beside Business OS, stop and reframe: the product on this lane is the agent mandate under design, not a bill of materials and not a generally shipped suite.
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 & evidence model. Counsel walks that story through Verify what an agent is allowed to do.
Codex Counsel — the agent in design
Codex Counsel is the named primary agent of the law vertical — in design. Mandate: intake quality, matter progression, trust-aware workflows, and deadline and obligation tracking. Signature question of every matter: is this matter moving correctly, and is every obligation visible?
It is designed to live inside intake, vault, and trust-ledger loops — conflict checks at the door, access-controlled matter vaults, programmatic three-way trust reconciliation — not as an annual spreadsheet the firm rebuilds after the fact. Shared teammates enrich context; Codex Counsel owns the law-lane mandate once the workflows survive counsel review.
What the law lane specializes (honest domains — direction, not availability)
Public posture on the law silo organizes around operating domains — diligence vocabulary for a lane still in design:
- Conflict-checked intake — new-matter intake designed to surface conflicts against the matter record before engagement.
- Secure document vaults — matter documents in access-controlled vaults with full audit history — every view and share logged.
- Trust reconciliation — the three-way trust check (bank statement, main ledger, client sub-ledgers) designed to verify programmatically on a cadence.
- Retainer and obligation workflows — retainer status, replenishment, deadlines, and required filings designed to track as workflow state — nothing living only in someone’s inbox.
- Matter progression — the matter moves under visible obligations, not under tribal knowledge.
Named-vendor battle cards stay internal. Public differentiation stays category-level. Prefer "designed to" and "in design" over present-tense availability claims.
Substrate docks Law depends on
Law is a specialized orchestration on the MCV substrate. Public docks you can open in a briefing:
- Mesh — the interconnect fabric that keeps practice surfaces coherent. Interconnect fabric is not data fabric.
- Synapse — real-time obligation and intake signal loops.
- Cortex — judgment with policy gates on matter actions and trust-aware workflows.
- Forge — outcomes that turn practice 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 counsel authority live?" The signal-order walkthrough is Walk the six-system substrate chain. Isolation posture for brand-scoped records is How per-brand data isolation works. Composition 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 law appliance" framing — this is an agent-authority lane on Business OS, not a standalone product shelf.
- No present-tense claim that intake, vault, or trust reconciliation ship as general availability.
- No fake availability date — the page will say so when counsel signs the workflow.
If someone asks for a physical kit path, point them at the physical verticals (Fit / Rest / Realty / Build) and keep Law on the agent-in-design story.
How to use this leaf in a briefing
- Open the silo first: MCV.LAW.
- Name Codex Counsel and the four mandate phrases before any demo narrative.
- Say the honesty lines aloud: agent-only — no hardware kits; in design — not availability.
- Walk Mesh → Synapse → Cortex → Forge before any "AI law firm" slide.
- Push autonomy claims back to gates and evidence — never to invented matter KPIs.
- Pair with the capital sibling when the deal spans treasury: Brief Catalyst Capital without mistaking it for a fund admin stack.
Non-goals for this leaf
- No matter-count, win-rate, billable-hour, or trust-balance metrics; 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 Law ships as general availability or as a purchasable appliance independent of Business OS.
When Codex Counsel is clear as direction, continue composition via organism composition and counsel review via diligence resources.