Redbo

Choose an experience

Two takes on the same one-line mission — an operating system glove-tailored to a specific restaurant concept. Switch between them anytime from the bar above.

Original prototype

Redbo Service

A pooled service-dispatch OS

The guided host→server scenario plus the full multi-surface operations console.

  • Visit → obligation → pooled dispatch → evidence
  • Network, store, floor, server & kitchen surfaces
  • “One prompt, whole floor” service thesis
Opus 4.8’s take

redbo-opus

A perishable-commitment yield OS

A deliberately different bet: the binding constraint isn’t service timing, it’s scarce, non-replenishable supply.

  • One dense instrument board on a scrubbable clock
  • Every decision priced as a dollar trade-off
  • Live constrained sim — nothing hand-authored
Bottom layer

Kitchen food model

The recipe graph, visualized

The substrate under everything: every dish as a graph of ingredients, each with a prep → hold → spoil life and a just-in-time finish clock.

  • Every menu item, raw → held → finished → plate
  • Two clocks: slow spoilage + fast JIT finish
  • Quantity-agnostic — pure structure
Open food model
Prototype · switch freely · resets on reload