Data Products (v0.3)
ORP v0.1/v0.2 is a document standard for transparent, human-attested, human-read policy reasoning. v0.3 keeps all of that and adds a second reader: a machine. An ORP document can now be used as a verifiable data product — an audience segment, a dataset, a training corpus — that an agent or a rail on the other side of a trade can verify, enforce terms on, and prove use of, without ever having met the publisher.
Everything on these pages is optional and additive. A plain v0.2 policy document is still valid —
it simply validates as the ORP-Policy profile under orp_version: "0.3".
See the migration guide for the one-field upgrade.
One object, two readers
| Human reader | Machine reader | |
|---|---|---|
| Reads | the full document: inspect, fork, re-run with different assumptions | a minimal attestation core it can verify in milliseconds |
| Trusts via | argument and sources | a cryptographic signature it checks itself, offline |
| Acts by | deliberating | deciding allow/deny against an enforceable usage policy |
The two never cannibalise each other: the machine verifies a small signed core that is hash-linked to the rich document a person reads.
What v0.3 adds
| Capability | Page | What it gives a machine |
|---|---|---|
| Attestation | Attestation | Offline Ed25519 verification of the document, AdCP #4441-aligned |
| Profiles | Profiles | A domain-neutral core + ORP-Policy / ORP-Ads / ORP-AI |
| Trust tiers | Trust Tiers | How much a reader may rely on a passport, and how it was verified |
| Usage policy | Usage Policy | What may be done with the data, in a form a rail enforces |
| Lineage | Lineage | Derivatives carry their ancestors’ constraints |
| Usage records | Usage Records | An append-only record of use — a rail receipt is one by construction |
| Legal provenance | Profiles | Legal basis, rights holders, opt-out signals, access, freshness, reach |
Why this matters for agent rails
As advertising and data move to agent-to-agent rails, a buying agent needs to decide — fast, and without a human in the loop — whether a data product is what it claims, whether it may be used for the purpose at hand, and be able to prove afterward what it did. v0.3 is designed so that a rail which already verifies AdCP signed provenance can verify an ORP passport with no new crypto: same canonicalisation, same Ed25519 posture, same key discovery.
Tooling
pip install "orp-validator[attestation]"
orp validate segment.yaml --profile ORP-Ads # validate + report profile and trust tier
orp conform # run the v0.3 conformance suiteNext steps
- Attestation — make a document verifiable
- Profiles — pick Core / Policy / Ads / AI
- A worked data-product passport