Business team
A shared process language: talking about “listing for sale” means the same to everyone because it points at one record.
v0.1.0
Open standard · two readers: human and agent
One description of a retail process, read by both people and AI systems.
ORPR is an open, versioned vocabulary of retail processes. Each process has a single definition: the same source describes it for a person, for an integrator and for an agent — with no room for interpretations to drift apart.
- 22
- 74
- 74
map content version v0.1.0 · 1.0
6 full · release v0.1.0 · 68 digests of reviewed cards
03 / Commercial offerORPR-CAT-02
full card · released 1.0
From price to till
- Purpose
- The price charged at the till is exactly the approved one — in this location, at this moment, for this item.
- Inputs
- approved item price
- Outputs
- price in force at the till
- Gates
- price approval, validity in the location
- Owner / consumer
- Offer (owner), Till (consumer)
- Obligation
- PL-PRICE-030 · Reference price when announcing a reduction
Human layer · System layer · Agent layer1 = 1 = 1
01The gap
The same process gets described in as many ways as it has readers.
An analyst, a software vendor and a language model each receive a different account of the same thing. The differences only surface at implementation — expensively.
- 01
Interpretations drift
With no shared reference, “goods receipt” means something slightly different to everyone. Integration pays for that gap.
- 02
Knowledge trapped in heads
The rule that decides correctness lives in an email, a config file and one person’s memory — not in a description you can point to.
- 03
Agents with nothing to anchor to
A model gets a prompt instead of a definition. Answers drift between runs because there is no stable source.
ORPR closes the gap with one description per process — legible to all three readers.
02How it works · process CAT-02
Follow one process from its name to a legal rule.
Take “From price to till”. The same source yields a short human definition, a structured card for systems, and an explicit binding to a statutory obligation.
Purpose
The price charged at the till is exactly the approved one — in this location, at this moment, for this item.
- Inputs
- approved item price
- Outputs
- price in force at the till
03What it is for
One source, three readers.
Integrator and vendor
A process card with inputs, outputs and gates replaces interpretation. Implementation scope is written in identifiers, not stories.
AI team
Stable context for an agent: the same versioned record as input yields reproducible output across models and runs.
04Proof, not promise
What is already confirmed.
The standard grows by cards, not declarations. Every figure below has a named object and comes from the same data file that feeds the map.
- 74
- processes have a card — 6 full cards in release v0.1.0, 68 independently reviewed and published as digests
- 16
- handoffs and calls confirmed by the author in cards (solid line on the map)
- 66
- of 74 processes have a confirmed regulatory binding — 160 unique requirements, one shown public and in full: CAT-02 → reference price
- 6
- retail business models — from independent store to owned chain — with a profile for each of the 74 processes
Minimal-sufficiency experiment (25 Aug 2026)
One task, one process area. Giving the model an ORPR record instead of a hand-written description narrowed the spread of answers across model families.
- answer spread
- 5×0.5×
- context share of task cost
- 28%
05Author and invitation
A standard run in the open, built to be contributed to.
ORPR is the work of one person, run in an open repository. Content is licensed CC BY-SA 4.0, code under Apache-2.0. Cards, relations and regulatory bindings are accepted through a public review process.