Salty Desk

Explicit handoffs only

Nothing movesuntil you move it.

Each tool owns its own state. A handoff is a packet you choose to send. Every row below states the field, the reason it travels or is withheld, and what the receiving tool can and cannot conclude from it.

If you have answered the triage console, each packet is also written out against your own constraints.

Filters the three contracts below · ⌘K searches the whole desk.

PrimaryContract 1.1.0
Menu BuilderSC-MB-001Occasion Operating SystemSC-OOS-001

Why the packet existsSo the night can be sequenced against a menu that has already been stress-tested — not against a wish list. Primary path can run in-app (Architecture → Plan) or cross-origin from standalone Menu Builder.

Moves forward

  • Menu architecture (roles, dishes, pairing mode)

    Because: The prep route is built per dish role; without roles there is no sequence to build.

  • Stress summary across five axes

    Because: Occasion OS needs the pressure profile to know which step to protect first.

  • Locked anchor and its re-scoring effect

    Because: An anchor fixes one dish's timing; the route has to respect it, not re-litigate it.

Stays behind

  • Draft menus you discarded

    Withheld because: A rejected draft is not a decision. Sending it would let it be re-proposed.

  • Simplification history and budget pressure inputs

    Withheld because: These are reasoning, not output. Occasion OS has no job that needs them.

  • Anything you did not explicitly send

    Withheld because: There is no background sync. Silence is withholding, not consent.

The receiver can conclude

  • Which dishes need heat, hands, or the pass at the same moment
  • Where the plan is already at capacity before guests arrive

It cannot conclude

  • Why you chose this menu over another
  • That any dietary category is an allergy-safe claim

If drafts and simplification history travelled too, Occasion OS would route a menu you already rejected.

Answer the triage console on the desk to see this packet written against your own constraints.

OptionalReader-initiated
Occasion Operating SystemSC-OOS-001Restaurant IntelligenceSC-RI-001

Why the packet existsSo a room can be ranked against the same occasion you were planning — when hosting is no longer the right outcome.

Moves forward

  • Occasion type, party size, and date window

    Because: Capacity and booking fit cannot be ranked without these three.

  • Planning-filter dietary categories (never allergy claims)

    Because: Used to filter rooms worth calling — the confirm still happens live, with the kitchen.

Stays behind

  • Full host plan, prep route, and shopping state

    Withheld because: None of it has a reader job on the dine-out side.

  • Guest names and private notes

    Withheld because: Packets are public-safe. Guest identity never leaves the tool it was typed into.

  • Any inference about why you switched to dining out

    Withheld because: The desk does not build a motive record. The switch is a choice, not a signal.

The receiver can conclude

  • Which rooms can physically seat the party in the window
  • Which rooms are worth the confirm call for your filters

It cannot conclude

  • That a room is allergy-safe for anyone at the table
  • That hosting failed, or why

If the host plan travelled, a restaurant surface would hold your kitchen state for a night that is not happening.

Answer the triage console on the desk to see this packet written against your own constraints.

OptionalPublic-safe packet
Restaurant IntelligenceSC-RI-001Salt Notes recordsEditorial

Why the packet existsSo a night you actually had becomes a first-party record with its unknowns still visible.

Moves forward

  • First-party case file

    Because: What was observed at the source, dated, with the observer's position stated.

  • Evidence trail with confidence labels and open unknowns

    Because: A record without its unknowns reads as certainty it never had.

Stays behind

  • Your shortlists and rejections

    Withheld because: A rejection is private judgment, not evidence about the room.

  • Booking attempts and confirm burden notes

    Withheld because: Operational friction on your side says nothing durable about the venue.

The receiver can conclude

  • What was true at that room, on that date, from the source
  • Which questions were left open

It cannot conclude

  • A star rating or a 'best restaurant' ordering
  • Anything about rooms you considered but never visited

If shortlists and rejections travelled, the record would read as a ranking you never published.

Answer the triage console on the desk to see this packet written against your own constraints.

Rules of transfer

  • Handoffs are reader-initiated. There is no background sync.
  • Packets are public-safe: no private notes, no guest identities.
  • Dietary categories travel as planning filters, never as allergy guarantees.
  • A refused hard stop does not travel as an approval.
  • A field with no job downstream does not travel, even when it is harmless.
  • Reasoning stays with the tool that did it; only conclusions move.
Read the shared boundary