Occasion Operating System
Library workshopTangled Thistle ↗
A dark walnut table being set at dusk, braise in an enamel pot under warm raking light
Host planning instrument · v2

Plan the night
you can actually
host.

Guest count, seating, real equipment, and dietary categories go in. A controlled route comes out — shopping, prep clock, service sequence, and an honest reading of where the evening is tight. Nothing is invented. When a plan cannot fit, it stops and tells you why.

Boundary

Educational planning only. Fixture menus, not tested recipes. Dietary categories are planning filters and carry no allergen safety guarantee. Capacity, equipment, and time constraints fail closed rather than guess.

Starting conditions

Real situations, ready to load

Load one, then move a single input to see what it costs you. Your own conditions can be saved, pinned, renamed and carried between devices.

Tune the library →
Table
Crowd
Constrained
Outdoor
Your saved conditions

Nothing saved yet. Build a route, name it, and it lands here.

Section 01

Operating conditions

Declare what is true. The engine will not assume equipment, seats, or time you have not stated.

Occasion shape
Service styledrives portioning and choreography
Guestscounted, not estimated
8
against 8 declared seats
Seats at the real table
8
Service time & day-of window
5 h free
Kitchen realityfail-closed inputs

Ovens

Usable burners

Cold storage

Counter & landing space

Hands available
Ambitioncourse count and hands-on tolerance
Seasondrives which fixtures read correctly
Budget tierper-head ceiling, indicative only
Leftovers goalsets batch volume honestly
Room conditions
Dietary categoriesplanning filters — not allergy guarantees

These filters remove conflicting fixture dishes from the route. They do not verify labels, cross-contact, or supplier changes. Confirm every ingredient yourself.

Culinary traditionsattribution, not an authenticity claim

No selection means no restriction. Selecting traditions narrows the library the engine may draw from; it does not make a dish regionally authoritative.

Section 01b

Declared limits

Open a group and state what is actually true. Each one tightens the model before the route is built.

Section 02

Controlled route

Hands prepping herbs and citrus beside labelled cold-hold containers and a timing note

Empty on purpose

Nothing is generated until conditions are declared. Set guests, seats, equipment and hands on the left, then build. If the route cannot fit what you have, the system blocks with a correction path rather than guessing.

  1. 01

    Declare

    Guests, seats, ovens, burners, cold storage, hands, time.

  2. 02

    Build

    A route scored against your real constraints.

  3. 03

    Refine

    Adjust one input, compare variations, then print the packet.

03 · Run control

Build run

Computing a route is a run with four stages. Each stage does the real work and reports what it produced. Step through it, or let it go.

  1. 01Waiting

    Menu selection

    Not run yet

  2. 02Waiting

    Resource load

    Not run yet

  3. 03Waiting

    Schedule

    Not run yet

  4. 04Waiting

    Cost and balance

    Not run yet

Run history

No completed runs on this device yet.