Owner / operator side / Operator-side prototype

Final stock check

The system can do one last local stock check before the next order step continues.

For a pizzeria

Helps stop the flow before the kitchen commits to something the shop no longer has.

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 touches

Order items and local stock state.

What it does not own

It does not replace the menu or the kitchen workflow.

Current state

Operator-side prototype

available in the pilot node when enabled

Current declared data-access summary: Order items and local stock state.

Read next

Do not stop at one module page.

See the queue this protects

The stock check only matters because the restaurant is already running an active order queue.

See the menu control beside it

Stock checks make more sense when you read them next to the menu-control surface.

Keep the live boundary small

This extra operator check still sits inside a deliberately small first live payment edge.

Technical identity

p4p.stock.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.

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/.