What it touches
Declared CVR identifiers and public node identity data.
Trust layer / Trust direction
A later trust layer can connect a node identity claim to a Danish CVR lookup or trust claim.
For a pizzeria
This is meant to make a restaurant identity more reviewable later without turning the registry into the authority.
Where it fits
This is where payment stays intentionally simple and where identity or business verification can later become reviewable.
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
Declared CVR identifiers and public node identity data.
What it does not own
It is not part of the live ordering loop today.
Current state
not enabled
Current declared data-access summary: Declared CVR/company identifiers and node public identity data.
Read next
This trust direction sits after the basic ordering flow, not before it.
The current real-world payment boundary is still much smaller than the later trust direction.
The provider page explains what the current shared stack is and what it does not claim yet.
Technical identity
p4p.trust.cvr-basicIf 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
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/.