08 · Devices, KDS, seating & signage

Theater / restaurant venue path — what integrates today vs roadmap.

Venue integration (truth)

flowchart LR
  SL[Seating layout admin
seatId tableId] --> POS[POS cart metadata]
  POS --> KT[kitchen_tickets]
  KT --> KDS[KitchenDisplay polling ~3s]
  KT -.->|NOT YET| SIG[Signage player]
  ADS[Admin ad playlists] --> SIG
  BR[Bridge LAN] --> KDS
  BR --> PR[Printers]
  POS --> BR
Works today Seat/table identity can flow POS → kitchen ticket → KDS chips (“Table 5 / Seat 12”). kitchen_tickets is auto-created if missing (critical fix).
Not built yet Customer-facing “order ready” board or seat-highlighted auditorium map on signage. Signage is folder/ad/display playlists (URL/image/video/HTML). Documented as roadmap in OAO 26.

Bridge

ComponentRole
bridge/ NodeCloud ↔ LAN middleware, WebSocket actions
bridge-win-csharp/Windows client (print, KDS fire, etc.)
Device manager UIPairing, secrets, locations, posModules

Movie theater mental model

  1. Admin draws auditorium in seating layouts (cinema templates).
  2. Concession POS attaches seat to cart metadata.
  3. Finalize creates kitchen ticket with seat fields.
  4. Kitchen / expo sees seat on KDS.
  5. Future: lobby signage pulls ready tickets or seat highlight.
Full KDS + signage inventory Lanes, APIs, tables, bridge, theater truth: 15 · Floor · KDS · GPE Signage