The Order Production Orchestrator. It paces which orders reach the kitchen screens and when, so that a rush arrives at the crew at a rate they can actually work through rather than all at once.
What the gate is doing right now: whether it is pacing releases or standing aside, how full each screen is, and which orders are being held back and why. Also where the mode is switched between automatic and forced.
/uiThe rule set currently loaded and fired against every eligible order — name, priority, condition and actions, in the order they actually run, plus any lints raised when it was loaded.
/rulesThe two things that can be changed while the Orchestrator runs: what the rules read when they score an order, and the dials the gate itself paces by. Both are kept in files on disk and take effect on the next pass.
/settingsHow the kitchen actually performed, over a service or a date range: screen occupancy, how long orders waited, where the bottlenecks were, and the same figures with the Orchestrator on versus off.
/metricsWhether the kitchen is coping or queueing, and whether the parts of an order finish together — the two curves the Orchestrator's own aims are judged against, gated versus ungated.
/efficiencyTime on screen by channel and by time of day, the slowest orders in a range, and the kitchen's in/out congestion — the same shape as the standalone prep-time dashboard, built from what this collector already records.
/prep-time