I want the concrete proof
Start with the live public reading path for the restaurant case.
Umbrella direction / public protocol family
A shop, venue, or local service should be able to keep direct contact with people.
Protocols4People is the broader direction behind Pizza4People. It asks what the smallest shared protocol layer should be before companies start adding payments, delivery, ticketing, hosting, trust, or other services on top.
In plain terms
- People can find a real operator through a public directory.
- The actual menu, listing, or request surface stays with that operator.
- Orders or requests can go direct instead of through one mandatory platform.
- Companies can still sell services on top without owning the basic connection.
Current public implementation: Pizza4People, an open protocol proof for direct restaurant discovery, direct menu access, direct ordering, node-owned identity, and registry failover. If you want the concrete proof today, start there. GitHub keeps the exact protocol language.
Start here
Three clean ways into the project.
I want the exact protocol language
Go straight to the public repo, proof note, spec, and architecture.
I want the broader frame first
Stay on this umbrella page and read the general model before diving into one vertical proof.
Plain terms
The umbrella idea in ordinary examples.
Restaurant
A customer discovers a restaurant publicly, opens that restaurant's own menu surface, and sends the order directly to the restaurant node.
Venue
A future profile could let a person discover an event source publicly, then read the listing, ticket rules, or attendance flow directly from the venue side.
Local service
A future profile could let a person discover a service provider publicly and send a booking request without one lead-marketplace owning the whole exchange.
Supplier or local trade
A future profile could let buyers discover a supplier, read current catalog data directly, and send a request without forcing the whole relation into one private gate.
Boundary
What this site is, and what it is not.
This site is
- A human umbrella overview
- A bridge into the first concrete proof
- A framing layer for the broader protocol family
This site is not
- Not the exact protocol source of truth
- Not the live restaurant proof itself
- Not a product marketplace or app store
So where does truth live?
- Pizza4People for the concrete public proof surface
- GitHub for precise protocol language and repo truth
- This page for the broader family explanation
Why
The goal is not to remove companies. It is to lower the mandatory layer.
Marketplaces can be useful. Delivery companies, payment providers, loyalty systems, hosting layers, and support businesses can all still exist. The question is which part becomes mandatory before two real parties can even talk to each other.
Protocols4People asks whether the basic discovery and direct contact layer can stay open first, with companies competing above that instead of owning the whole boundary.
Model
Keep the base small. Let sectors differ above it.
Shared base
Identity, announce, discovery, current state, manifests or snapshots, and direct endpoint-to-endpoint contact.
Vertical profiles
Restaurant ordering is first. Later profiles may cover ticketing, retail goods, local services, or supplier/procurement flows.
Scoped registries
Umbrella, vertical, country, local, and backup registries can carry discovery without becoming identity owners.
Optional modules
Payments, delivery, verification, loyalty, accounting, inventory, or other add-ons must not be required for baseline interoperability.
GitHub keeps the exact protocol language. This umbrella page is the human reading layer above it.
Status
What is real now, what comes next, and what is not claimed.
Public now
- Pizza4People public GitHub repository
- Readable spec, architecture, schemas, and examples
- Reference registry, client, and node code
- Independent node interop checker
Next proof
- Several independently built nodes passing the same checker
- Shared registry discovery across those nodes
- Controlled real restaurant pickup-order pilot
- Primary registry plus backup registry deployment
Not claimed yet
- No production trust network
- No CVR/company verification claim yet
- No broad restaurant rollout yet
- No claim that this replaces existing delivery platforms today
First proof
If you want the concrete proof, start with Pizza4People.
Pizza is not the ceiling. It is the first vertical where the broader idea can be tested against a visible market problem: direct restaurant-customer discovery and ordering after a platform exit.
The public proof lives at pizza4people.com. The source and protocol work live at github.com/DennisHedegreen/p4p. This umbrella page stays high-level on purpose so the GitHub repo can remain the exact protocol source.
Contact
For press, technical review, or umbrella questions.
Email: hedegreen.research@gmail.com
Public proof repository: github.com/DennisHedegreen/p4p
Protocols4People is the umbrella direction. Pizza4People is the first concrete vertical proof. GitHub remains the protocol-language source.