Platform
Sync
Nothing to decide
Every terminal is caught up. Most disagreements never reach this screen — money appends rather than merges, stock is a signed ledger, and a table takes whichever state is less available. What lands here is what no rule could settle.
This browser
Terminal
This browser is not acting as a terminal, so nothing is queued locally and the indicator reports the connection and nothing more. Bind it to a registered terminal and it will keep working through an outage.
Terminals
Where each one is
How disagreements are settled
Mostly, by rule
Money appends, never merges
Two terminals taking payment on one bill is two payments, not a conflict. The same payment pushed twice is caught by its key. This is why payments is append-only — it makes the hardest case disappear rather than be solved.
A table takes the less available state
If one terminal says available and another says payment due, it stays payment due. A table wrongly held is an annoyance; a table wrongly released while money is owed is the failure this platform exists to prevent.
Stock is a signed ledger
Consumption from two terminals sums correctly with no coordination at all.
Menu and settings: the server wins
A terminal that took an order at a stale price keeps its snapshot on the line, so the guest is charged what they were shown.
A gap halts the stream
If operation 4472 is missing, 4473 is not attempted — it may depend on it. Skipping ahead is how a payment lands on an order that was never created.