What it touches
Active items, prices, descriptions, and categories.
Customer side / Shown in proof
Clickable photo-style menu
A customer taps a paper-menu style surface instead of a plain item list.
For a pizzeria
Useful if you want the customer surface to feel closer to a printed flyer or visual takeaway menu.
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 OCR, payment, stock, or operator workflow.
Current state
Shown in proof
available as the pilot-node photo map menu route when enabled
Current declared data-access summary: Active item ids, names, descriptions, prices, and categories only. It does not own photos, OCR, prices, inventory, payment, or operator data.
Read next
Do not stop at one module page.
See the plain menu baseline
This visual menu is easier to understand when you compare it to the simpler list version.
Then see the customer follow-up
After the order is sent, the next customer-facing step is the status page.
Keep the boundary in view
The visual menu still sits inside the same small payment boundary as the rest of the proof.
Technical identity
p4p.menu.photo-map
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/.