Solutions

Compose the lane that fits your network

Read how a location becomes a configuration — the inputs, the rule set, and five worked examples — then pick your vertical and shape the composition below. Guidance for a briefing, not a commitment.

Request access All solutions

Kit configuration

Four inputs shape every configuration

Vertical, location profile, offline criticality, and what is already on the wall. The same dimensions the deployment team reads in a briefing — laid out here so the conversation starts with a shared vocabulary.

Vertical

The operating world the location lives in. Kit coverage exists for the physical verticals — fitness, restaurant, realty, and build; agent-only verticals compose without a hardware kit.

FIT
REST
REALTY
BUILD
GENERAL

Location profile

The shape of the site — footprint, traffic, and risk class. Profile drives coverage density and which vertical kit variant applies.

small
standard
high_volume
high_risk
unmanned
mixed_use

Offline criticality

How much of the operation must keep running when the uplink drops. Criticality sets the resilience tier of the Core Edge node and which loops are held sacred offline.

standard
high
extreme

Existing systems

What is already on the wall — POS, access control, cameras, BMS. Existing systems can offset components, but they never remove the Mesh-native requirements.

replace
partial reuse
integrate via gateway
greenfield

The rule set

The rules the configuration logic applies

No snowflakes: every location composes from standard, conformance-gated kits under a fixed rule set — and the first rule never bends.

Rule 01

Core Edge, always

Every configuration starts with a Core Edge kit — local compute, local policy, and the edge runtime that keeps critical loops alive. There is no kit composition without it.

Rule 02

FIT high-performance or 24/7

Fitness locations running high-performance or around the clock add Vision Intelligence plus strengthened access — form and activity sensing inferred on the edge.

Rule 03

REST full-service

Full-service restaurants add the Commerce kit, kitchen display systems, and service vision — ticket flow and payment capture held to the strictest tier of the offline contract.

Rule 04

REALTY high-sensitivity

High-sensitivity properties add environmental and leak sensing plus higher camera density — privacy-zoned, with access decisions held local while offline.

Rule 05

BUILD high-risk

High-risk job sites add the High-Risk kit, wearables, and enhanced offline — ruggedized edge and safety loops that are never shed from the local buffer.

Rule 06

Existing systems offset, never remove

Existing systems can offset components but never remove Mesh-native requirements — discovery, identity, policy, and the event schema are not optional.

Rule 07

Agents ship with the kits

Final output always includes the minimum agent set required for that vertical — the orchestrator, the vertical specialist, and the shared department agents.

Worked examples

Five configurations, end to end

Real input profiles and the recommendations they produce — kits, install complexity, and the agent activation set. These are reference patterns for a briefing, not quotes.

Ember Restaurant

REST

Full-service restaurant — urban, high volume, with patio and strong allergy control.

Inputs

Vertical: REST
Location profile: High Volume
Offline criticality: High
Existing systems: Legacy POS (replace) · Basic cameras (partial reuse)
Special requirements: Full table service · Patio coverage · Strong allergy control

Key components

Rugged edge node + hot standby
Counter POS (2) + mobile POS (4)
KDS (expo + 3 prep stations)
EMV/NFC payment terminals with offline store-and-forward
Cameras: entrance, dining zones, pass, key kitchen stations, patio
Occupancy sensors + environmental basics
UPS sized for 60 min critical load
Allergen / label printer support

Recommended kits

Ember Full Service
Vision Intelligence
Core Edge — always installed

Install complexity: High
Edge capacity: Dual-node resilient
Certification target: Production

Agent activation set

Aria (Orchestrator)
Ember Service (primary)
Atlas
Nexus
Sentinel
Ledger
ForgeMaster

Legacy POS is fully replaced to keep commerce native to the organism.
Patio coverage added for tempo and experience signals.
Offline contract prioritizes ticket flow, KDS, and payments.

Helix Unmanned 24/7

FIT

Around-the-clock unmanned fitness club — form intelligence and member safety, no staff on site.

Inputs

Vertical: FIT
Location profile: Unmanned
Offline criticality: Extreme
Existing systems: Basic access control (upgrade) · Mixed equipment brands
Special requirements: Strong form intelligence · Member safety

Key components

High-resilience edge node + failover connectivity
Smart access control with mobile credential + backup readers
Dense camera coverage on free-weight floor, platforms, and key machine banks
On-edge pose / form models
Equipment telematics gateways (multi-brand)
Emergency / safety alerting path
UPS + extended autonomy
Member-facing feedback displays (selective)

Recommended kits

Helix 24/7 Unmanned
Vision Intelligence
Core Edge — always installed

Install complexity: High
Edge capacity: High-resilience edge node with cellular failover
Certification target: Institutional (recommended for unmanned)

Agent activation set

Aria
Helix Coach (primary)
Sentinel (elevated)
Atlas
Nexus
Vanguard
ForgeMaster

Access and safety loops are treated as sacred offline.
Form intelligence remains available locally even during uplink loss.
Unmanned profile triggers stricter conformance and monitoring requirements.

Domain Multifamily

REALTY

Institutional multifamily mid-rise — predictive maintenance and tenant experience under one record.

Inputs

Vertical: REALTY
Location profile: Standard
Offline criticality: High
Existing systems: Legacy access control (partial) · Basic BMS
Special requirements: Predictive maintenance · Strong tenant experience · Institutional owner (high-sensitivity)

Key components

Building edge node
Smart access control (units, amenities, back-of-house)
Cameras: entries, corridors, elevators, amenities, plant rooms (privacy zoned)
HVAC and metering gateways
Leak detection + environmental sensors on critical risers and plant
Package room and amenity access hardware
UPS for access + edge + critical sensing

Recommended kits

Domain Full Building
Domain High-Sensitivity Additions
Core Edge — always installed

Install complexity: Medium–High
Edge capacity: Building edge node
Certification target: Production → Institutional

Agent activation set

Aria
Domain Steward (primary)
Sentinel
Atlas
Ledger
Nexus
ForgeMaster

Existing BMS is integrated via gateway rather than ripped out.
Privacy zones are mandatory on residential corridors and units.
Predictive maintenance signals are prioritized for plant and water systems.

Scaffold Job Site

BUILD

High-risk active job site — rapid deploy, heavy equipment, and strict PPE enforcement.

Inputs

Vertical: BUILD
Location profile: High Risk
Offline criticality: Extreme
Existing systems: Minimal
Special requirements: Rapid deploy · Heavy equipment · Strong PPE enforcement

Key components

Rugged edge node (wide temp, shock rated) + cellular/satellite failover
Site access control + zone presence (high-risk zones)
Dense rugged camera coverage on entry, high-risk work areas, and equipment zones
PPE and fall-risk vision models (on-edge)
Wearable panic / man-down devices for selected trades
Equipment telematics + utilization + geofencing
Rugged supervisor tablets
High-endurance power solution

Recommended kits

Scaffold High-Risk
Scaffold Heavy Equipment
Core Edge — always installed

Install complexity: High (but designed for rapid deploy)
Edge capacity: Rugged edge node (wide temp, shock rated) + cellular/satellite failover
Certification target: Production + High-Risk profile

Agent activation set

Aria
Scaffold Field (primary)
Sentinel (elevated)
Atlas
Nexus
ForgeMaster
Ledger

Offline contract is the strictest of all verticals.
Safety events are never shed from the local buffer.
Kit is designed for repeated demobilization and redeployment across projects.

Mixed Portfolio

GENERAL

Small institutional cohort — two restaurants, two clubs, one multifamily — proving coherence across verticals.

Inputs

Vertical: GENERAL
Location profile: Mixed Use
Offline criticality: High
Existing systems: Varies per site
Special requirements: 2 restaurants, 2 clubs, 1 multifamily · Prove organism coherence across verticals

Key components

Core Edge standard at every site
Ember Full Service at the restaurants
Helix Full Club at the clubs
Domain Full Building at the multifamily property

Recommended kits

Core Edge — always installed
Ember Full Service
Helix Full Club
Domain Full Building

Install complexity: Medium
Edge capacity: Shared Core Edge standard across all sites
Certification target: Pilot cohort

Agent activation set

Aria
Common agent team
Vertical specialists (Ember Service, Helix Coach, Domain Steward)

Shared Core Edge standard across all sites, with vertical-specific kits layered on top.
Common agent team plus vertical specialists; unified conformance and evidence requirements.
Franchise OS activated from day one for cross-location visibility.

Read this before the briefing

Guidance for a briefing, not a quote

What you have just read is the configuration logic and five worked examples — a way to arrive at the briefing with a shared vocabulary. It is not an interactive quoting tool, and nothing on this page is a scope or a commitment.

Two rules never bend: every configuration starts with a Core Edge kit, and existing systems can offset components but never remove Mesh-native requirements. Final configurations are set with the deployment team during the briefing.

Request a briefing Browse the standard kits

Solutions configurator

Compose your solution

Three steps: pick the vertical you operate in, mark the capabilities that matter, and review the composition. The result is a starting brief for a conversation — not a commitment.

Your world
Shape
Composition

Pick your world

Every module below runs on the same shared substrate. Three are live today; the rest are on the roadmap or in design, and say so on the card.

MCV.FITLivefitness & wellnessThe flagship fitness operating system.MCV.CAPITALLivecapital & treasuryInstitutional capital on one settlement spine.MCV.RESTLivehospitality & diningService tempo, engineered.MCV.REALTYLiveproperty managementThe tenant lifecycle on one record.MCV.BUILDLiveconstruction & contractingField logs, synchronized to the back office.MCV.LAWIn designlegal practiceTrust-aware practice workflows.

Ready to brief your network?

Schedule a briefing Open Console

Solutions

Compose the lane that fits your network

Request access All solutions

Kit configuration

Four inputs shape every configuration

Vertical

The operating world the location lives in. Kit coverage exists for the physical verticals — fitness, restaurant, realty, and build; agent-only verticals compose without a hardware kit.

FIT
REST
REALTY
BUILD
GENERAL

Location profile

The shape of the site — footprint, traffic, and risk class. Profile drives coverage density and which vertical kit variant applies.

small
standard
high_volume
high_risk
unmanned
mixed_use

Offline criticality

How much of the operation must keep running when the uplink drops. Criticality sets the resilience tier of the Core Edge node and which loops are held sacred offline.

standard
high
extreme

Existing systems

What is already on the wall — POS, access control, cameras, BMS. Existing systems can offset components, but they never remove the Mesh-native requirements.

replace
partial reuse
integrate via gateway
greenfield

The rule set

The rules the configuration logic applies

No snowflakes: every location composes from standard, conformance-gated kits under a fixed rule set — and the first rule never bends.

Rule 01

Core Edge, always

Every configuration starts with a Core Edge kit — local compute, local policy, and the edge runtime that keeps critical loops alive. There is no kit composition without it.

Rule 02

FIT high-performance or 24/7

Fitness locations running high-performance or around the clock add Vision Intelligence plus strengthened access — form and activity sensing inferred on the edge.

Rule 03

REST full-service

Full-service restaurants add the Commerce kit, kitchen display systems, and service vision — ticket flow and payment capture held to the strictest tier of the offline contract.

Rule 04

REALTY high-sensitivity

High-sensitivity properties add environmental and leak sensing plus higher camera density — privacy-zoned, with access decisions held local while offline.

Rule 05

BUILD high-risk

High-risk job sites add the High-Risk kit, wearables, and enhanced offline — ruggedized edge and safety loops that are never shed from the local buffer.

Rule 06

Existing systems offset, never remove

Existing systems can offset components but never remove Mesh-native requirements — discovery, identity, policy, and the event schema are not optional.

Rule 07

Agents ship with the kits

Final output always includes the minimum agent set required for that vertical — the orchestrator, the vertical specialist, and the shared department agents.

Worked examples

Five configurations, end to end

Real input profiles and the recommendations they produce — kits, install complexity, and the agent activation set. These are reference patterns for a briefing, not quotes.

Ember Restaurant

REST

Full-service restaurant — urban, high volume, with patio and strong allergy control.

Inputs

Vertical: REST
Location profile: High Volume
Offline criticality: High
Existing systems: Legacy POS (replace) · Basic cameras (partial reuse)
Special requirements: Full table service · Patio coverage · Strong allergy control

Key components

Rugged edge node + hot standby
Counter POS (2) + mobile POS (4)
KDS (expo + 3 prep stations)
EMV/NFC payment terminals with offline store-and-forward
Cameras: entrance, dining zones, pass, key kitchen stations, patio
Occupancy sensors + environmental basics
UPS sized for 60 min critical load
Allergen / label printer support

Recommended kits

Ember Full Service
Vision Intelligence
Core Edge — always installed

Install complexity: High
Edge capacity: Dual-node resilient
Certification target: Production

Agent activation set

Aria (Orchestrator)
Ember Service (primary)
Atlas
Nexus
Sentinel
Ledger
ForgeMaster

Legacy POS is fully replaced to keep commerce native to the organism.
Patio coverage added for tempo and experience signals.
Offline contract prioritizes ticket flow, KDS, and payments.

Helix Unmanned 24/7

FIT

Around-the-clock unmanned fitness club — form intelligence and member safety, no staff on site.

Inputs

Vertical: FIT
Location profile: Unmanned
Offline criticality: Extreme
Existing systems: Basic access control (upgrade) · Mixed equipment brands
Special requirements: Strong form intelligence · Member safety

Key components

High-resilience edge node + failover connectivity
Smart access control with mobile credential + backup readers
Dense camera coverage on free-weight floor, platforms, and key machine banks
On-edge pose / form models
Equipment telematics gateways (multi-brand)
Emergency / safety alerting path
UPS + extended autonomy
Member-facing feedback displays (selective)

Recommended kits

Helix 24/7 Unmanned
Vision Intelligence
Core Edge — always installed

Install complexity: High
Edge capacity: High-resilience edge node with cellular failover
Certification target: Institutional (recommended for unmanned)

Agent activation set

Aria
Helix Coach (primary)
Sentinel (elevated)
Atlas
Nexus
Vanguard
ForgeMaster

Access and safety loops are treated as sacred offline.
Form intelligence remains available locally even during uplink loss.
Unmanned profile triggers stricter conformance and monitoring requirements.

Domain Multifamily

REALTY

Institutional multifamily mid-rise — predictive maintenance and tenant experience under one record.

Inputs

Vertical: REALTY
Location profile: Standard
Offline criticality: High
Existing systems: Legacy access control (partial) · Basic BMS
Special requirements: Predictive maintenance · Strong tenant experience · Institutional owner (high-sensitivity)

Key components

Building edge node
Smart access control (units, amenities, back-of-house)
Cameras: entries, corridors, elevators, amenities, plant rooms (privacy zoned)
HVAC and metering gateways
Leak detection + environmental sensors on critical risers and plant
Package room and amenity access hardware
UPS for access + edge + critical sensing

Recommended kits

Domain Full Building
Domain High-Sensitivity Additions
Core Edge — always installed

Install complexity: Medium–High
Edge capacity: Building edge node
Certification target: Production → Institutional

Agent activation set

Aria
Domain Steward (primary)
Sentinel
Atlas
Ledger
Nexus
ForgeMaster

Existing BMS is integrated via gateway rather than ripped out.
Privacy zones are mandatory on residential corridors and units.
Predictive maintenance signals are prioritized for plant and water systems.

Scaffold Job Site

BUILD

High-risk active job site — rapid deploy, heavy equipment, and strict PPE enforcement.

Inputs

Vertical: BUILD
Location profile: High Risk
Offline criticality: Extreme
Existing systems: Minimal
Special requirements: Rapid deploy · Heavy equipment · Strong PPE enforcement

Key components

Rugged edge node (wide temp, shock rated) + cellular/satellite failover
Site access control + zone presence (high-risk zones)
Dense rugged camera coverage on entry, high-risk work areas, and equipment zones
PPE and fall-risk vision models (on-edge)
Wearable panic / man-down devices for selected trades
Equipment telematics + utilization + geofencing
Rugged supervisor tablets
High-endurance power solution

Recommended kits

Scaffold High-Risk
Scaffold Heavy Equipment
Core Edge — always installed

Install complexity: High (but designed for rapid deploy)
Edge capacity: Rugged edge node (wide temp, shock rated) + cellular/satellite failover
Certification target: Production + High-Risk profile

Agent activation set

Aria
Scaffold Field (primary)
Sentinel (elevated)
Atlas
Nexus
ForgeMaster
Ledger

Offline contract is the strictest of all verticals.
Safety events are never shed from the local buffer.
Kit is designed for repeated demobilization and redeployment across projects.

Mixed Portfolio

GENERAL

Small institutional cohort — two restaurants, two clubs, one multifamily — proving coherence across verticals.

Inputs

Vertical: GENERAL
Location profile: Mixed Use
Offline criticality: High
Existing systems: Varies per site
Special requirements: 2 restaurants, 2 clubs, 1 multifamily · Prove organism coherence across verticals

Key components

Core Edge standard at every site
Ember Full Service at the restaurants
Helix Full Club at the clubs
Domain Full Building at the multifamily property

Recommended kits

Core Edge — always installed
Ember Full Service
Helix Full Club
Domain Full Building

Install complexity: Medium
Edge capacity: Shared Core Edge standard across all sites
Certification target: Pilot cohort

Agent activation set

Aria
Common agent team
Vertical specialists (Ember Service, Helix Coach, Domain Steward)

Shared Core Edge standard across all sites, with vertical-specific kits layered on top.
Common agent team plus vertical specialists; unified conformance and evidence requirements.
Franchise OS activated from day one for cross-location visibility.

Read this before the briefing

Guidance for a briefing, not a quote

Request a briefing Browse the standard kits

Solutions configurator

Compose your solution

Three steps: pick the vertical you operate in, mark the capabilities that matter, and review the composition. The result is a starting brief for a conversation — not a commitment.

Your world
Shape
Composition

Pick your world

Every module below runs on the same shared substrate. Three are live today; the rest are on the roadmap or in design, and say so on the card.

Ready to brief your network?

Schedule a briefing Open Console