/usr/local/bin/lunch.day
root@kitchen:~$ █
service status serving

lunch.day

an authoritative system for orchestrating the midday meal

12:42 local lunch hour
P99 < 12 min plate-out
99.97% kitchen uptime
scroll ↓
// 02 — RESERVATIONS

queue.status

FIFO with kindness

time party table state
12:00 Okafor / 2 T-04 SEATED
12:15 Tanaka / 4 T-11 SEATED
12:30 Mikkelsen / 3 T-07 PLATING
12:45 Reyes / 2 T-02 QUEUED
13:00 Park / 5 T-09 QUEUED
13:15 Bianchi / 2 T-12 QUEUED
queue depth: 3
// 03 — KITCHEN UPTIME

slo.dashboard

last 24 hours

availability 99.97%
SLO 99.5% — within budget
p99 plate-out 11.4m
SLO 12.0m — passing
covers / hour 42x
target 50 — on pace
return guests 68%
trend +4 wk/wk
incident log (last 24h)
  • OK 09:14 — pickle restock complete
  • WARN 11:02 — sourdough proof slow, mitigated
  • OK 11:48 — service window opened
  • OK 12:02 — first cover seated
  • INFO 12:30 — special added: SLO-cooked brisket
// 04 — COMMANDS

man lunch

the operator's reference

NAME
       lunch.day — orchestrate the midday meal with authority.

SYNOPSIS
       lunch.day [--start] [--seat party]
                 [--queue] [--metrics] [--shutdown]

DESCRIPTION
       Long-running daemon. Prepares, plates, and serves dishes
       under defined Service Level Objectives. Front-of-house
       and back-of-house communicate over a single warm channel.

EXAMPLES
       $ lunch.day --start
       $ lunch.day --seat 'Reyes/2' --table T-02
       $ lunch.day --metrics --since=09:00
       $ lunch.day --shutdown --grace=15m

EXIT STATUS
       0   plates delivered, glasses cleared
       1   sauce broke
       2   service exceeded SLO budget