What it touches
Order summary, configured alert target, and urgency state.
Counter / hardware side / Operator-side prototype
Bell or light alert
A local box can ring, beep, or flash when a new order or hardware problem needs attention.
For a pizzeria
Lets the hardware give an audible or visible cue without turning the alert layer into the actual order queue.
Where it fits
What the shop uses behind the counter
These are the restaurant-side tools for menu control, kitchen flow, stock, printing, and fallback alerts.
This page is the readable P4P explanation for one module. It is meant to be understandable before you open the raw manifest.
What it does not own
It does not accept orders, replace the kitchen queue, or settle payment.
Current state
Operator-side prototype
builtin operator self-test lane when enabled and configured
Current declared data-access summary: Order summary and configured alert target.
Read next
Do not stop at one module page.
See the main kitchen flow first
A bell or light alert only helps because there is still a real kitchen queue behind it.
Then compare it to the print lane
This alert lane becomes more concrete when you read it next to the primary print/POS handoff.
Keep the phone fallback nearby
If a local bell or light path disappears, the next useful fallback is a phone notification lane.
Technical identity
p4p.order.alert.basic
If you need the developer-facing version, open the GitHub module reference or the raw manifest. The public P4P page stays focused on what the module means operationally.
Open provider page / Open GitHub module reference / Open GitHub provider reference / Open raw manifest
Contact
This module page is still part of the same narrow proof story.
Questions about this module, the provider layer, or the live-pilot boundary: hedegreen.research@gmail.com.
Public proof front door: https://pizza4people.com/.
Broader protocol-family direction: https://protocols4people.com/.