What it touches
Order summary and the operator phone destination.
Owner / operator side / Planned next
Operator SMS alert
The system can send a short phone alert when an order or printer problem needs fast attention.
For a pizzeria
Useful if the test hardware is noisy or partially unattended and the operator still needs a direct phone fallback.
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 is a fallback notification, not the main order surface.
Current state
Planned next
not enabled; candidate phone fallback lane for a five-place hardware trial
Current declared data-access summary: Order summary and configured operator destination.
Read next
Do not stop at one module page.
See the email fallback beside it
SMS is easiest to judge when you compare it to the simpler email fallback lane already in the stack.
Then see the queue it protects
Phone fallback only matters because the restaurant still has a real operator queue behind the alert.
See who currently provides the tools
The provider page keeps the current pilot-feedback modules inside one clearly labeled reference stack.
Technical identity
p4p.notify.sms
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/.