What it touches
Active items, prices, descriptions, and categories.
Customer side / Shown in proof
Simple online menu
A customer opens a normal menu list and sends the order directly to the restaurant.
For a pizzeria
You keep the menu basics on your own node instead of relying on a marketplace-owned list.
Where it fits
What the customer sees
These are the public surfaces a customer can actually open during discovery and ordering.
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 own payment, stock, or staff workflow.
Current state
Shown in proof
available as the pilot-node customer menu list route when enabled
Current declared data-access summary: Active item ids, names, descriptions, prices, and categories only. It does not own prices, inventory, payment, or operator data.
Read next
Do not stop at one module page.
See what happens after the order
After the customer sends the order, the next useful public page is the status screen.
Then look behind the counter
If you want the shop-side counterpart, open the menu-control page the restaurant uses.
Keep the payment edge small
The first live payment shape stays intentionally simple: order online, pay at pickup.
Technical identity
p4p.menu.list
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/.