Platform · Under the hood

How the box is built.

For technical buyers: the six MCV layers behind every build, the shared building blocks they run on, and how a new build plugs into each layer instead of re-implementing it.

In the middle: your site, portal and app.

Shared building blocks

Built once, used by every build.

tenancy-runtime

Resolves the right client and location for every request.

request-scope

Carries who is acting and where through every call.

gates

Permissions and feature checks at every door.

metering

Usage counted per client, per engine.

console-views

The operator screens: orders, customers, inbox, leads.

marketing-shell

Brand-forward front end for each industry.

integrations-sdk

The contract for wiring third-party tools in.

@mcv-web/ui

The shared UI library and the standard CORTEX console layout.

MCV.ONE · Auth + Commerce + Payments

MCV.ONE

MCV.ONE runs sign-in, checkout and payments for every MCV build, so your customers get one account and one checkout on your site, your portal and your app. What it does for you →

Auth: building blocks

@mcv-digital/auth-bridge

Thin adapter. Talks only to MCV.ONE contracts.

@mcv-digital/shell

Auth slot in the app shell.

Build rule

No hard-coded auth logic in a build.

Need	MCV.ONE provides	How a build uses it
Customer login	`MCV.ONE session`	Signs in through auth-bridge
Staff access	`Roles + gates`	Checks them through the shared contract
Guest orders	`Claim desk`	Claims them through auth-bridge

Commerce: building blocks

@mcv-digital/commerce

Cart → checkout → order lifecycle.

@mcv-digital/catalog

Products, variants and collections.

OneCommerceAdapter

Contract to the MCV.ONE engine.

Need	MCV.ONE provides	How a build uses it
Storefront cart	`commerce package`	Uses the shared version
Order desk	`admin-desk orders`	Uses the shared version
Catalog	`catalog package`	Configured per build

Payments: building blocks

Build rule

No hard-coded payment logic in a build.

Order link

Every payment belongs to an order.

Need	MCV.ONE provides	How a build uses it
Take payment	`MCV.ONE payments`	Uses the shared version
Refund	`Order lifecycle`	Uses the shared version
Reporting	`Admin desk`	Uses the shared version

MCV.TECH · Business-in-a-Box + Business OS

MCV.TECH

MCV.TECH is the console your team runs the business from: orders, customers, leads and every location in one place. A new business starts from a proven setup, not a blank codebase. What it does for you →

CORTEX Console: building blocks

It runs on the shared building blocks above.

Need	MCV.TECH provides	How a build uses it
Admin screens	`@mcv-web/ui + CORTEX layout`	Uses the shared screens, not its own
Tenancy / multi-location	`tenancy_template + ScopeChain`	Connects through an adapter and shared types
Branding / theming	`ThemePack`	Reads the same design tokens
Feature switches	`enabledEngines`	Mirrors them in its features.json
New client	`Config on a tested core`	Configured, not rebuilt

Business OS: building blocks

Same layout

Admin desks sit inside a CORTEX-style shell.

Industry vocabulary

Each build declares an industry that maps to tenancy_template.

Authoritative layer

TECH stays the Business OS under every build.

Tenancy template: building blocks

tenancy_template

Industry, branding, enabled engines.

ScopeChain

Client → location → request.

ThemePack

Branding as tokens.

enabledEngines

Feature switches per client.

MCV.CX · Sales + Support

MCV.CX

MCV.CX puts sales and support in one inbox, so every conversation with a customer lives next to their orders. What it does for you →

Inbox + leads: building blocks

CxInboxAdapter

Build → CX contract.

admin-desk: inbox + leads

Ops surface every client needs.

Need	MCV.CX provides	How a build uses it
Contact forms	`CX inbox`	Connects through an adapter
Lead pipeline	`CX sales`	Connects through an adapter
Ops view	`admin-desk`	Uses the shared version

Support: building blocks

Returns desk

admin-desk returns.

Visits

admin-desk visits.

Need	MCV.CX provides	How a build uses it
Return request	`Order lifecycle`	Uses the shared version
Booking	`Visits module`	Configured per build
FAQ	`STUDIO content`	Filled from STUDIO content

MCV.AD · Ads + Performance

MCV.AD

MCV.AD runs your campaigns and measures them against the orders and leads your own system records, not estimates. What it does for you →

Performance: building blocks

AdCampaignAdapter

Build → AD contract.

Commerce events

From the commerce package.

Lead events

From CX.

Need	MCV.AD provides	How a build uses it
Order conversion	`commerce events`	Connects through an adapter
Lead conversion	`CX leads`	Connects through an adapter
Spend	`AD engine`	Uses the shared version

Campaigns: building blocks

Placeholder accounts

Wired at scaffold time by DEV.

Creative distribution

STUDIO → AD.

Need	MCV.AD provides	How a build uses it
New client	`DEV scaffold`	Gets a placeholder ad account at setup
Creative	`STUDIO`	Receives creative pushed from STUDIO
Landing	`Campaign links to your pages`	Configured per build

MCV.DEV · Engineering + Automation

MCV.DEV

MCV.DEV is the engineering and automation layer that lets us stand up the next client faster every time. What it does for you →

Scaffolding: building blocks

mcv create kit

--industry --name --slug

_template kit

The clean starting point every new build begins from.

Placeholder accounts

STUDIO / CX / AD wired.

Need	MCV.DEV provides	How a build uses it
New client	`mcv create kit`	Created by one command
Console entry	`tenancy_template`	Created in the same run
Brand	`STUDIO injection`	Later phase

Automation: building blocks

Same connection points

DEV's generators connect to MCV.TECH the same way every build does.

Continuous upgrades

No build left behind.

Need	MCV.DEV provides	How a build uses it
Automation	`MCV.DEV generators`	Set up by the same generators as every other build
Upgrades	`Shared packages`	Gets fixes as they ship
Metering	`metering package`	Reports usage through hooks

MCV.STUDIO · Creatives + Brand System

MCV.STUDIO

MCV.STUDIO makes your brand system, photos, video and content, and builds them into your site and app from day one. What it does for you →

Brand system: building blocks

brand/ in every build

Each build keeps its identity in data.

Compatible tokens

One token contract with TECH.

Injection

One-click into a new build.

Need	MCV.STUDIO provides	How a build uses it
Branding	`ThemePack`	Reads the same design tokens
Build brand	`brand/ folder`	Configured per build
Console brand	`CORTEX console theme`	Uses the shared version

Creative: building blocks

@mcv-digital/media

Media handling in every build.

Asset library

One approved home.

To AD

Creative distribution.

Need	MCV.STUDIO provides	How a build uses it
Product photos	`media package`	Pulls the photos in
Ads creative	`AD distribution`	Pushed to campaigns
Site hero	`Site content`	Configured per build

Want to go deeper?

Tell us what you need to integrate, and we will walk it through with you.

Build your box → Contact