The outcome you are walking toward
A diligence briefing you can give without collapsing Ember into "another POS." You leave able to name what Ember owns as the rest vertical orchestrator, how it sits on Business OS, which public docks carry the substrate hops, and what remains designed-for / staged — without inventing ticket times, margin lifts, or shipped hands-free coverage.
Ember is an orchestration, not a transactional stack
Ember is the adaptive operating system for multi-location restaurants and hospitality. The public silo is MCV.REST — Ember. Category-level posture only: transactional POS and KDS process orders; Ember is designed to sense the physical floor, fire real-time intelligent loops, and forge better people and processes every shift. Hands-free KDS is designed for hands-free operation and sits in staged rollout — never claim it as generally shipped on every line.
If a briefing treats Ember as a checkout SKU beside Business OS, ask how ticket priority, station recovery, inventory honesty, and guest recovery cross sensing, interconnect, events, judgment, action, and forging without a second project per hop. The signal-order walkthrough is Walk the six-system substrate chain.
What Ember specializes (honest domains)
Public depth on the rest silo organizes around feature domains — diligence vocabulary, not a weighted scorecard:
- Order and kitchen flow — AI-prioritized routing, adaptive prep sequencing, automatic bump and plating alerts in staged rollout. Ember Service tracks tickets from creation and triggers recovery when tempo breaks. Floor service orientation: rest floor service ops.
- Inventory and cost control — scales, RFID, smart shelves, fridge telematics, computer-vision waste detection; demand and waste forecasting into purchase suggestions and specials engineering.
- Staff capability — performance-forged micro-training from real bottlenecks; skill graphs; Synapse coaching nudges inside the shift.
- Cameras as ops intelligence — queue length, table turnover, hygiene, theft, and bottlenecks as live operational signals — not security-only recording.
- Multi-location — live topology, cross-site benchmarking, best-practice extraction with propagation that adapts to local conditions. Network learning is Franchise OS — Tell Business OS from Franchise OS.
- Guest experience — preference and recovery loops; Ember Service owns guest recovery before issues become public reviews.
Named-vendor battle cards stay internal. Public differentiation stays category-level.
Ember Service — primary agent for tempo and recovery
Ember Service is the named primary agent of the rest vertical. Mandate: service tempo, kitchen flow, ticket recovery, and guest loops. It is designed to act inside the shift — catching tempo breaks and recovering tickets and guest moments — not as a next-day dashboard.
Authority still sits on the shared floor: irreversible classes stay gated; brand scope fails closed; reconstructability lives in the audit trail. Counsel walks that story through Verify what an agent is allowed to do and governed agent boundaries.
Substrate docks Ember depends on
Ember is a specialized orchestration on the MCV substrate. Public docks you can open in a briefing:
- Mesh — devices, stations, and assets as a living interconnect fabric. Interconnect fabric is not data fabric.
- Synapse — real-time ticket and station loops.
- Forge — outcomes that turn shift experience into better playbooks and skills under governance.
- Pulse / Cortex / Aria complete the chain narratively; product docks for Mesh, Synapse, and Forge are the ones to name aloud first.
Composition of kits, agents, verticals, and Franchise OS is Name what the organism is made of.
Hardware and offline — sacred loops
The Commerce kit class (POS, payments, KDS, receipts as one commercial surface) is specified in Spec the hardware for an Ember dining room. 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; the local edge holds ticket state and station timers so tickets are not lost and payments are not double-charged. The careful public contract is Read the offline contract your locations run on.
How to use this leaf in a briefing
- Open the silo first: MCV.REST — Ember.
- Name Ember as vertical orchestrator on Business OS, not as a POS replacement alone.
- Hedge hands-free KDS explicitly: designed for hands-free operation, staged rollout.
- Walk Mesh → Synapse → Forge docks before any "AI kitchen" demo.
- Push autonomy claims back to gates and evidence — never to a slide metric.
- Separate location runtime from network learning (Business OS vs Franchise OS).
- Pair with the fitness sibling when the portfolio spans clubs: Brief Helix without mistaking it for a membership stack.
Non-goals for this leaf
- No ticket-time or margin percentages, uptime guarantees, or invented customer logos.
- No named-vendor battle cards or certification badge theater.
- No present-tense claim that hands-free KDS is generally shipped on every line.
When Ember is clear, continue composition via organism composition and counsel review via diligence resources.