LoadingPage content is loading
Solutions
In motion
The physical layer of the organism.
Hardware, edge compute, POS, inventory, vision, and smart devices — all native to the same Mesh and Synapse fabric. Without STORE, the organism is software. With STORE, the organism has a body. Browse the labeled pre-sale demo for kits and lines — not a public cart.
Core Thesis
Software alone is insufficient at institutional scale
Multi-location and franchise performance requires a unified physical layer — one designed to survive connectivity loss, feed high-fidelity, low-latency signals into the agents, and close the loop between digital intent and physical reality.
MCV.STORE is that layer: a single commercial and operational surface for every device a location runs, deployed as standardized, conformance-gated kits instead of per-vendor silos. Without STORE, the organism is software. With STORE, the organism has a body.
Hardware Taxonomy
Eight categories, one record
Edge
The nervous system of every location — rugged, offline-first gateways with local Mesh runtime, local inference, and a secure enclave for policy and agent execution.
Vision
Cameras, occupancy and people-counting, form and activity sensing, and environmental sensors — with on-edge inference for privacy and latency.
POS
Counter, mobile, and self-checkout terminals with integrated payments and kitchen display systems — every transaction a first-class event on the same record the agents see.
Inventory
RFID portals and handhelds, smart shelves, industrial scanners, and equipment tags — material state stays live and actionable in the Mesh.
Access
Smart locks, credential readers, visitor systems, and zone control — physical access and digital identity share the same policy plane.
Displays
Menu boards, wayfinding, crew and production boards, and locker systems — the expressive surface of the location, driven by the live record.
Vertical
Back-of-house and vertical-specific hardware — expo screens, rugged field tablets, member access, package rooms — composed for real operating environments.
Future
Robotics, elevated sensing, and energy edge controllers land on the same bus and record when they arrive — a new category, not a new silo.
Standard Kits
Pre-integrated, Mesh-native kits
We do not sell random devices. Every kit is a standard, conformance-gated configuration with discovery, health, event schema, policy surface, and offline behavior defined up front — and the Core Edge kit is always installed. Includes are reference configurations from the kit BOM tables — component classes and quantity bands, finalized per site survey.
Always installed
Core Edge
The minimum viable physical organism. Every location starts here — local compute, local policy, and the edge runtime that keeps critical loops alive.
- Industrial fanless edge gateway (8–16 core, 32GB+ RAM, TPM 2.0, dual NIC, 4G/5G failover option) — one per site, plus an optional hot-standby node of the same class
- Hardware secure element / HSM for device identity and policy keys
- Managed PoE switch (8–24 port, industrial temperature rating) with UPS power conditioning sized for 30–60 minutes of autonomy
- Primary + failover uplink module (fiber / cellular); environmental enclosure rated to the site
- Edge runtime: local Mesh, local Synapse subset, policy engine, store-and-forward buffer
FIT · BUILD · REALTY · REST
Vision Intelligence
High-fidelity eyes and closed-loop visual intelligence, inferred on the edge for privacy and speed.
- GPU/NPU-accelerated edge vision appliance — one or more nodes, can share the Core Edge node
- 4–16 fixed 4K / low-light cameras (PoE, IR, indoor/outdoor rated); up to 4 PTZ cameras for large spaces and job sites
- Optional multi-sensor units for occupancy, people counting, and environmental sensing
- Encrypted edge video storage with policy-enforced retention; PoE++ switch for camera power
- Standardized calibration and mounting kit with aiming tools
REST · FIT · Retail
Commerce
A unified commercial surface native to the operating record — every transaction a first-class event with offline resilience.
- Counter POS terminals with receipt/ticket printers and customer displays — one or more per counter
- Rugged mobile / handheld POS with barcode and RFID scanning — one or more per floor
- EMV + NFC payment terminals with offline store-and-forward — one per point of sale
- Kitchen Display System (expo + prep screens) and order routing for restaurant configurations
- Optional smart cash drawers, standalone scanners, and self-checkout kiosks
Vertical kit · REST
Ember
Restaurant and hospitality configuration built on the Commerce kit, tuned for service tempo.
- Commerce kit as the base configuration — POS, payments, and printers per its reference BOM
- KDS expo and prep screens with order routing hardware — one or more per station
- Ticket flow and payment capture held to the strictest tier of the offline contract
Vertical kit · FIT
Helix
Fitness configuration pairing member access with form and activity intelligence.
- Member check-in, access readers, and locker hardware — sized to entrances and locker rooms
- Form, activity, and posture sensing with on-edge inference (Vision Intelligence kit)
- Local inference and member-facing feedback designed to continue offline
Vertical kit · REALTY
Domain
Property configuration where access control and safety signaling are the highest-priority offline loops.
- Smart locks, credential readers, and zone control — per door and zone count from the site survey
- Visitor management and package room hardware
- Access decisions against cached credentials and local policy while offline
Vertical kit · BUILD
Scaffold
Harsh-environment field configuration for job sites — rugged where the work is.
- Rugged tablets and wearable computers — one per field crew member
- Equipment and tool tracking tags per asset class
- Harsh-environment edge and enclosure options
Cross-Kit Standards
Eight standards every kit conforms to
Mandatory for every kit, regardless of type — checked at the conformance gate before a device joins a production organism.
Mesh-native discovery
Automatic registration and continuous health reporting into the Mesh from first boot.
Identity & attestation
Hardware-backed device identity with attestation — unauthenticated devices are never admitted.
Policy inheritance
The Layer 0 policy floor applies at the edge; local execution never weakens global policy.
Event schema compliance
Every event carries tenant, location, purpose, consent class, and digest.
Offline contract
Defined offline behavior per capability, with declared replay semantics — in-order replay with deduplication on reconnect.
Secure update path
Signed, staged, rollback-capable updates for firmware and the edge runtime.
Agent accessibility
Critical agents can run or be invoked locally, inside pre-approved authority envelopes.
Observability
Device health, queue depth, inference latency, and error budgets visible in the global plane.
The Fuse Loop
How hardware fuses with the organism
Physical Event
A door opens, a queue forms, a sale closes, a fault trips — something happens on the floor.
Edge
The edge node captures it with local inference and buffering — online or not.
Mesh
The interconnect fabric handles discovery, health, and routing for every endpoint.
Synapse
The priority event bus fires the signal to every subscriber in real time.
Agents
Cortex and the agent team apply judgment — inside policy and pre-approved authority envelopes.
Forge
Measured outcomes feed the learning loops that sharpen the next response.
Action
A human or automated action closes the loop, with physical actuation when required.
Offline & Conformance
Conformance is a gate, not a brochure claim
Designed to continue
The offline contract
Critical loops are designed to continue while offline: access control against cached credentials and local policy, safety signaling and local alerting, POS and order capture, and local agent execution inside pre-approved authority envelopes. What keeps working is declared per capability — never implied.
- May degrade: global optimization, non-critical analytics, heavy model updates
- Forbidden offline: weakening policy, expanding agent authority, deleting evidence, admitting unauthenticated devices
Standard, conformance-gated
Conformance before production
Every kit ships Mesh-native discovery, hardware-backed identity and attestation, policy inheritance, event-schema compliance, a defined offline contract, and a signed, rollback-capable update path. Devices and kits are designed to pass the conformance gate before joining a production organism.
- Certification levels are stated publicly only where issued — never badged before they exist
Explicit gap detection
Reconciliation without amnesia
The edge holds the operating record locally. On reconnect it replays events in order with digests; the global plane validates, deduplicates, and acknowledges; and any gap is recorded explicitly as a reconciliation case — surfaced, never smoothed over.
Deployment Methodology
From site survey to network expansion
Site Survey
Power, network, mounting, and environmental conditions are surveyed before any configuration is finalized.
Kit Selection
Core Edge always; capability and vertical kits are selected per the location profile and the survey.
Provisioning
Zero-touch or technician-assisted provisioning, with hardware-backed identity from first boot.
Mesh Join
The node joins the Mesh, downloads its policy floor, and activates its local agent set.
Calibration
Vision, inventory, and access systems are calibrated against the physical space.
Pilot Validation
The location is validated against acceptance cases — including offline behavior — before go-live.
Network Expansion
The same kit standards roll out across the portfolio; each new location repeats the methodology.
Pre-sale · Phase S2
Labeled pre-sale demo — not purchasable yet
MCV.STORE is the Solution front door for hardware kits and lines. This page does not sell from a public cart: there are no unit prices, no stock counts, and no order flow here.
Open the labeled pre-sale demo to browse kits and upcoming lines with hedged availability (pilot preview · waitlist · upcoming). Register interest there — or stay on the STORE waitlist for notify-only capture. Kit BOM sections above and the Solution Configurator remain the reference spine; briefing and site survey finalize any real configuration.
Hardware lines
Named kit lines — briefing / pre-order interest only
Browse the labeled pre-sale demo per line. Cards marked upcoming or briefing-only are not orderable or purchasable. No invented SKUs, prices, or warehouse inventory.
Kits · pilot preview / waitlist
Standard kits (Core Edge → vertical)
Core Edge, Vision Intelligence, Commerce, and the Ember / Helix / Domain / Scaffold vertical kits — reference BOMs above. Pre-order interest in the demo; configuration stays survey-finalized.
- Not purchasable yet
- No public unit prices
Upcoming · briefing-only
Robotics & elevated sensing
Future taxonomy lines that land on the same Mesh bus when they arrive. Pre-sale demo + waitlist only — not a current catalog SKU with stock.
- No availability claim
- No public unit dollars
Upcoming · briefing-only
Energy edge controllers
Energy and elevated edge control as a future category on the same record — not a siloed vendor stack. Labeled pre-order interest only until Tony GO opens real commerce.
- Placeholder line
- Demo before commerce
Next step
Labeled pre-sale demo — browse kits; register demo interest. Not purchasable yet.
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.