What it touches
Item ids, names, descriptions, prices, categories, and active/inactive state.
Owner / operator side / Operator-side prototype
Edit menu and prices
The restaurant can change names, prices, categories, and whether an item is active.
For a pizzeria
This is the control surface that lets the shop own its own menu instead of waiting for a platform back office.
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 not a customer-facing menu page.
Current state
Operator-side prototype
available in the pilot-node operator dashboard when enabled
Current declared data-access summary: Item ids, names, descriptions, prices, categories, and active/inactive availability. Operator-only; not a customer presentation module.
Read next
Do not stop at one module page.
See the public result
After the restaurant edits the menu, the simplest customer-facing result is the plain online menu.
Then see the paper-menu helper
If the shop starts from a printed flyer, the OCR helper is the separate optional import surface beside the editor.
See who currently provides this stack
The provider page explains the shared reference layer behind the current public tools.
Technical identity
p4p.catalog.editor
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/.