Restaurant archetype / Order Up
A restaurant,
working together.
One conversation can reach the table, kitchen, and service team. Explore the layers that understand the request, apply your rules, and return an honest result.
01 / A request in motion
From a guest’s words
to the right action.
Choose an example, then run the flow or explore one step at a time. Watch what changes when a request passes—or fails—the scope check.
A guest request moves through Core Intelligence, a typed capability, policy checks, and the business executor. A scoped event updates the relevant service screen, and a receipt returns the outcome. Enable JavaScript to explore the interactive walkthrough.
02 / Open up the operating model
Each layer has a job.
Each scope has a boundary.
Explore the eight restaurant layers beneath the experience. Select a layer to see the information it works with and the change it can request.
Eight layers support party sessions, menu guidance, carts and budgets, kitchen orders, staff assistance, zone music, shared events, and administration. Enable JavaScript to inspect each layer.
03 / One archetype. Different restaurants.
Swap the venue.
Keep the shared foundation.
Choose an example restaurant. Its brand, menu knowledge, and music profile change together while the reusable Order Up stack stays in place.
The shared Order Up archetype combines with a venue’s public bundle to create a separately scoped DOL instance. Enable JavaScript to compare the example venues.
The venue bundle supplies public knowledge and configuration. Private records, credentials, and operational authority belong inside the business-controlled runtime.
The underlying definition
Built from declared components.
Order Up brings together 15 standard components. The instance selects compatible amenities and binds the services it needs.
Inspect all 15 standard components
Core IntelligenceRequired
Composes conversation from permitted DOL state and proposes typed capability requests.
core-intelligenceCore VoiceSelectable
Shared speech input, speech output, turn state, and text fallback through a replaceable binding.
core-voiceVirtual receptionistSelectable
Remote text and voice answers from public venue knowledge under a non-operational policy profile.
virtual-receptionistMenu RAG / knowledge layerRequired
A schema and retrieval contract for company-provided menu, ingredient, price, station, and availability data. The template contains no venue menu.
restaurant-menu-catalogSafety and budget guidanceSelectable
Listed-allergen checks, alcohol gating, uncertainty wording, and meal-budget estimates.
restaurant-dining-policyPrice and budget guidanceSelectable
Deterministic totals and budget comparisons grounded in the venue menu.
restaurant-meal-quoteTable and partySelectable
Stable guest identities, name synchronization, and independent table sessions.
party-session-serviceOrdering and kitchenSelectable
Shared cart, demo order submission, venue kitchen tickets, and status transitions.
restaurant-order-serviceKitchen operationsSelectable
Venue-wide kitchen tickets and controlled preparation, ready, and delivered transitions.
restaurant-kitchen-serviceServer assistanceSelectable
Table-scoped help requests projected into a venue-wide server queue.
staff-request-serviceZone JukeBoxSelectable
Independent music request queues for a venue's main room, reception, patio, or other zones.
music-queue-serviceLive state and projectionsRequired
Synchronizes customer and operator projections around typed venue events.
lwf-event-serviceLocal demo executorRequired
Validates typed requests, enforces selected amenities, and emits allow or deny receipts.
local-demo-executorVenue data ingestionSelectable
Produces reviewable menu candidates before publication into owner-approved venue knowledge.
restaurant-menu-importDOL administrationRequired
Resolved instance, amenity selection, receipts, and scoped reset controls.
dol-adminDefinition: restaurant.orderup@0.1.0-local.
Try the service surfaces
Meet Order Up Evergreen.
Explore the configured table, kitchen, service, and venue tools in the working sandbox.
Sandbox actions do not fulfill live venue requests or process payments.