LoadingPage content is loading
Diligence
Diligence resources
A curated reading path for counsel and security reviewers — the public docs that describe isolation, sign-on, approval gates, and audit evidence, in review order. Nothing to download: formal attestations are shared through a briefing when they exist, never badged here first.
What this page is
A curated link set — not a downloadable pack
- Contents
- Public docs
- Isolation, Triangle sign-on, gates, audit trail, multi-tenant model, pilot checklist
- Attestations
- On request
- Shared through a briefing when they exist — never badged on this page before they do
- Uptime / SLAs
- Not published
- No percentage availability claims on public pages; support states one honest line — response within 1 business day during pilot phase
Trust stack
Controls that ship with the platform
01
One secure sign-on
IdentityPasskeys and secure sessions, built in from the start. The public site and every operator console share one sign-on system — your teams never juggle a separate login per app.
02
Per-brand data isolation
Data IsolationEvery brand and location gets its own data boundary on one shared platform. If a boundary is not explicitly set, access is blocked by default — isolation is enforced, never assumed.
03
Database-level enforcement
DataData boundaries between brands are enforced at the database level, not just in the application — data cannot leak across brands or locations you are not authorized for.
04
Approval gates
PolicyHuman and policy checkpoints sit in front of any action that cannot be undone. Automation works inside those limits — it never gets to skip them.
05
Full audit trail
AuditWho acted, under which brand or location, through which approval step — a complete history your counsel can reconstruct during due diligence.
06
Automated royalty & fee tracking
Royalty & FeesUsage and fees are tracked automatically across every brand and location — part of the platform ledger, not a bolt-on billing script.
Review path
How diligence usually proceeds
Read the public materials
Start with the isolation, sign-on, gates, and audit docs linked below — they are the same architecture the product enforces.
Cross-check Trust
The Trust center states the same control domains as product features, not as a PDF annex.
Request access or a briefing
Counsel and security reviewers state their role on Request Access — institutional briefings are role-shaped (executive, ops, finance, security, IT), not one generic deck. Open Evidence Package categories and stakeholder briefing outlines when preparing the room — structure only, no filled packs on this site.
Verify in the product
During review, ask to reconstruct a specific action from the audit trail and confirm brand isolation fails closed.
Reading path
The public materials, in review order
Curated docs counsel and security reviewers open first. Nothing to download — formal attestations stay on request.
- IsolationHow per-brand data isolation worksDatabase-enforced brand boundaries, deny-by-default grants, and how isolation fails closed.
- IdentityTriangle: secure sign-onOne credential across public and operator surfaces, with role-aware routing and brand-scoped grants.
- PolicyApproval gates for autonomous agentsHow irreversible actions are classified, who may release a gate, and how gate decisions are recorded.
- AuditAudit trail & evidence modelWhat is captured at the moment of action so counsel can reconstruct who did what, under which brand.
- PlatformMulti-tenant architectureSeven levels of organizational scope, one hard isolation boundary at the brand, and what is shared versus isolated.
- RolloutPilot rollout checklistBounded-pilot shape: one workflow, named owners, explicit proof criteria, expansion only on evidence.
After the docs lane
Evidence and briefing leave-behinds
Structure-only public guides for Phase 1 exit categories and role-shaped briefings — not filled packages or invented ROI.
Pilot Evidence Package
Category map for Phase 1 exit — Charter through Go/No-Go. Filled instruments stay engagement / NDA.
Stakeholder briefings
Exec / Ops / Finance / Security / IT outline shapes — printable skeletons, not talk tracks with invented dollars.
Institutional deployment
Delivery phases, exit criteria, and artifacts — the path that produces the Evidence Package.
Schedule a briefing
Role-shaped desk routing. Not a cart, not a public rate card, not a pack download.
Enablement contract
What diligence leave-behinds promise — and what they do not
Keep counsel honest: docs first, categories second, filled instruments only in engagement.
Rule 01
Docs lane first
Isolation, Triangle sign-on, approval gates, and audit trail docs above remain the counsel reading path. Enablement guides do not replace them.
Rule 02
Evidence categories, not samples
The Evidence Package leaf lists what must appear at Phase 1 exit. Empty cells mean not yet collected — never invent theater for a public page.
Rule 03
Briefings by role
Multi-stakeholder deals get persona-shaped outlines (Exec through IT). One generic deck is not the product.
Rule 04
What stays off this site
Filled Evidence Packages, public SKU dollars, vanity uptime badges, and certification theater. Those move through a live briefing when they exist.
Keep exploring
When the docs lane is not the only job
Also open these
Trust
Trust center
Security as product — sign-on, isolation, gates, and audit framed for institutional review.
Access
Request Access
Role-aware onboarding for operators, partners, and counsel — the start of a secured review path.
Guides
Guides
Long-form rollout, multi-tenant decisions, agent policy, and royalty orientation.
Related
GuidesRun a security review of the platformFor counsel and security reviewers: work through isolation, sign-on, gates, and audit evidence in review order, and finish knowing exactly what to verify live in the product.GuidesVerify the audit trail hands-onFor counsel: go from reading the evidence model to reconstructing a real action — actor, brand context, gate decision, and outcome — during a live review session.GuidesKnow what a Phase 1 Evidence Package must containFor operators and counsel: the category map of a Foundation Pilot exit package — what must appear before a go/no-go, what stays briefing-only, and what this page deliberately does not publish.GuidesKnow who we brief before a multi-stakeholder dealFor operators: the role-shaped briefing map — which stakeholder jobs we prepare for, what each conversation is for, and what stays internal rather than published as a generic deck.GuidesMap the integration patterns the platform already documentsFor integrators: actionable outlines for identity, Mesh–Synapse events, edge offline, agent authority, data fabric, and STORE kits — each linked to real docs and guides, not a fake coverage library.GuidesTell Business OS from Franchise OS without a deckFor operators: the durable distinction between the location-level organism runtime and the network learning layer — what each owns, what neither pretends to own, and how they compose under one authority floor.GuidesWalk the six-system substrate chainFor operators: the organism runtime in signal order — Pulse senses, Mesh connects, Synapse fires, Cortex thinks, Aria acts, Forge transforms — with honest links to the public docks and the docs that govern judgment and evidence.GuidesName what the organism is made ofFor operators: the composition checklist for a living location and network — certified kit posture, edge offline contract, policy-bound agents, Business OS, Franchise OS, vertical intelligence, and the shared authority floor — with honest links to the public leaves that own each part.GuidesBrief Helix without mistaking it for a membership stackFor operators: how Helix specializes Business OS for multi-location fitness — member progression, floor intelligence, Helix Coach, and Axon as Mesh specialization — with honest links to the fit silo and the public substrate docks.GuidesBrief Ember without mistaking it for a POS stackFor operators: how Ember specializes Business OS for multi-location hospitality — kitchen flow, inventory honesty, Ember Service, and sacred offline ticket/payment loops — with honest links to the rest silo and the public substrate docks.GuidesBrief Scaffold without mistaking it for a job-site app stackFor operators: how Scaffold specializes Business OS for construction networks — field progress vs plan, safety observations, Scaffold Field, and harsh-environment offline loops — with honest links to the build silo and the public substrate docks.GuidesBrief Domain without mistaking it for a PMS stackFor operators: how Domain specializes Business OS for multi-property portfolios — tenant experience, predictive maintenance, Domain Steward, and access/safety offline loops — with honest links to the realty silo and the public substrate docks.GuidesBrief Catalyst Capital without mistaking it for a fund admin stackFor operators: how the capital lane stays agent-authority only — settlement integrity, treasury signals, risk flags, and capital allocation support on one governed record — with honest links to the capital silo and the public substrate docks, and no kit sales theater.GuidesBrief Codex Counsel without mistaking it for a practice-management storefrontFor counsel: how the law lane stays agent-authority only and in design — intake quality, matter progression, trust-aware workflows, and deadline and obligation tracking — with honest links to the law silo and the public substrate docks, and no kit sales theater.GuidesBrief MCV.STORE as a Solution without inventing a cartFor operators: how MCV.STORE stays a Solution — physical organism kits and lines on one Mesh-native surface — with honest waitlist and labeled pre-sale paths, and no fake inventory counts or public unit prices.SupportTrust & securitySign-on, isolation, approval gates, and audit trails framed as product controls.SupportContact & escalationRoute a question to the right desk — operations, partnerships, capital, or trust.
Get in touch
No public inbox is published for MCV.TECH yet; operators already on the platform use the support path inside their console.
Open ConsoleWhere this goes
Your inquiry is routed to the right desk — operations, partnerships, capital, or trust — based on what you tell us. No anonymous ticket queue.
Already running on the platform? Live deployment issues move faster through the support channel inside your operator console.
Console Access
Login to Open Console
Next step
Schedule a briefing
Corporate buyers, multi-unit operators, and investors start with a briefing — then a vertical path that fits the portfolio. Pilot one workflow, expand on evidence.