MCV.REST — powered by Ember
Floor management, waitlists, kitchen prioritization, and payout splits for multi-unit hospitality — the same rails as every other vertical, tuned to the dining room, with Ember Service as the primary agent for service tempo.
Use the chapter track buttons, number keys 1 through 9, arrow keys, J and K keys, Page Up, or Page Down to move between chapters.
Loading scene
01 / 04 · Act I · Service thrash
Every location invents its own back office.
Multi-unit hospitality without a shared record is permanent reconciling.
Swipe to explore
Continue into the platform.
Running on the shared substrate today.
A service night
Reservations and expected parties balance against the floor map before doors — hosts start with the room, not a guess.
Before doors
Aria covers the phone — inquiries answered, parties confirmed, the waitlist managed in the location’s profile.
First seating
Tickets prioritize by entry time and firing sequence across one kitchen queue, and turn-times rebalance against the live floor.
Rush
Tip pools and payout splits compute from POS data — servers see the same math the back office does.
After last seating
A night on the module
Three moments from a service night — each runs on the shared rails underneath this vertical.
The phone
Aria picks up inquiries, confirms reservations, and manages the waitlist while the team runs service — no missed covers from a ringing phone.
The pass
Tickets route and prioritize by entry time and firing sequence — the kitchen sees one queue, not five tablets.
The payout
Tip pools and payout splits compute from POS data at close — servers see the same math the back office does.
MCV.REST · hospitality & dining
Table turn-times and reservation queues balance dynamically against the live floor — hosts see the room, not a guess.
Phone inquiries, party confirmations, and waitlist adds are handled by Aria in the location’s profile — staff stay on the floor.
POS data imports into proportional pool distributions by hours, sales, or role weights — calculated, not argued.
Display screens prioritize by entry time and course timing automatically — expo runs on signal, not memory.
MCV Ember
Positioning
Ember is the adaptive operating system for multi-location restaurants and hospitality. Every location becomes a living organism that senses the floor, connects every device, fires real-time intelligence, and forges better service, staff capability, and margins under the pressure of every shift.
Problem
Restaurant technology is transactional and fragmented. POS processes but does not understand the floor. KDS pushes tickets without intelligent sequencing — crews stay chained to the screen, with no path to hands-free operation. Inventory is reactive. Cameras only record. Training is generic. Multi-location visibility is dashboards, not living systems.
Substrate
Ember is a specialized orchestration on the MCV substrate: Pulse senses · Mesh connects · Synapse fires · Cortex thinks · Aria acts · Forge transforms. Substrate docks stay on /platform/* — Mesh, Synapse, and Forge carry the floor loops Ember orchestrates.
Feature domains
Domain 01
AI-prioritized routing sends every ticket to the right station. The KDS is designed for hands-free operation — voice, gesture, and plate-ready computer vision — with adaptive prep sequencing, automatic bump, and plating alerts in staged rollout on the line. Ember Service, the primary agent for service tempo and kitchen flow, tracks every ticket from creation and triggers ticket recovery the moment tempo breaks.
Domain 02
Scales, RFID, smart shelves, fridge telematics, and computer-vision waste detection keep counts honest. Demand and waste forecasting drives automatic purchase suggestions and real-time specials engineering.
Domain 03
Real performance data forges personalized micro-training from actual bottlenecks. Skill graphs, adaptive certification, and Synapse coaching nudges grow capability inside the shift, not in a classroom.
Domain 04
Cameras stop being security-only. Queue length, table turnover, hygiene, theft, and bottlenecks become live operational signals.
Domain 05
Live topology across every site, cross-site benchmarking, and best-practice extraction with propagation that adapts to local conditions.
Domain 06
Preference and recovery loops keep every guest relationship warm — Ember Service owns the guest experience loops, catching issues and recovering them before they reach a review.
Hardware posture
Commerce kit class
Ember locations run the Commerce kit class: POS, payments, KDS, and receipt systems as one unified commercial surface — counter and handheld POS, EMV + NFC payment terminals with offline store-and-forward, and kitchen display systems at expo and prep stations.
Offline contract
Ticket flow, KDS, and payment capture are sacred offline: POS is designed to keep taking orders and payments on store-and-forward, the KDS keeps displaying and advancing tickets, and the local edge holds ticket state and station timers — so no ticket is lost and no payment is double-charged.
Standard kits
Standardized kits over custom snowflakes — from a core kit for small formats through full-service, high-volume, and cloud-kitchen configurations, every Ember kit is Mesh-native and arrives pre-configured for Ember Service agent activation.
Journeys
Mesh registers the station, Synapse sequences the tickets, and the hands-free bump flow — in staged rollout — keeps both hands on the line. Performance streams into Cortex, and Forge delivers a 90-second micro-training in the next quiet window.
Table and preference signals arrive in context, upsells surface at the right moment, and Ember Service triggers guest recovery automatically when something slips.
Sees live Mesh health and anomalies, investigates with one click, pushes a Forge-refined prep workflow, and acts on suggested staffing.
Gets the portfolio organism view, traces high-waste root causes, and propagates winning playbooks across the network.
Experiences a seamless, intelligent flow — preferences remembered, recovery automatic, no friction visible.
Roadmap
Mesh connects POS, KDS, and cameras; Synapse runs order flow; Cortex gives demand visibility; hands-free KDS enters staged pilot on the line.
Inventory IoT, camera intelligence, staff loops, and Forge micro-training come online.
Cross-site propagation, advanced playbooks, and continuous optimization across the network.
Category-level differentiation
Transactional POS/KDS process orders; Ember continuously senses the physical floor, fires real-time intelligent loops, and forges better people and processes every shift. Hands-free KDS (designed for hands-free operation, in staged rollout), camera-driven ops intelligence, and continuous micro-training are designed into the organism, not bolted on.
Sister site & substrate
Ember and Ember Service depth live on this tech silo. The MCV.REST sister site is the vertical brand surface — link out for the Rest marketing experience; keep kits and BOM on MCV.STORE.
MCV.REST
One secure sign-on across every brand and vertical. State your role — access routes to the right desk, never a sales queue.
