Rights Passport API
A Rights Passport is a signed, immutable-version envelope for machine-verifiable rights, restrictions, authority references, provenance, disclosure, custody and economic context around an existing ENTITY object.
Implemented rule model
The reference registry normalizes right rules with ALLOW, REQUIRE and PROHIBIT effects. Each rule carries explicit actions, conditions, obligations and right references. The passport can also bind authority references, jurisdiction/profile references, semantic references, provenance/disclosure references, provider-neutral custody locators, a privacy profile, economic terms and deployment-specific legal classification.
Rights are not possession
Hosting bytes, possessing a file, running a node or controlling a database does not automatically confer a RIGHT. Provider custody is explicitly separated from authority, and the passport must not embed provider credentials.
Non-rival data
ENTITY models scarce economic objects primarily as rights and entitlements rather than claiming the underlying information bytes themselves become scarce. Economic terms explicitly preserve the boundary that underlying information remains non-rival.
Lifecycle
Supersession does not rewrite the old passport. The historical signed version remains verifiable while the new passport becomes the operational successor.
Failure conditions
- Object/controller mismatch.
- Invalid right effect or missing action set.
- Custody locator that claims provider authority or embeds credentials.
- Legal classification that lets the protocol determine legal status.
- Economic terms that falsely declare information bytes economically scarce.
- Hash/signature mismatch.
- Unsupported or unresolved referenced semantics in a deployment that requires them.
Integration rule
Applications should verify the Rights Passport and separately evaluate the actual action, purpose, jurisdiction and authority context before acting. A valid passport is portable evidence of a signed rights description; it is not by itself proof of external payment, legal title or objective truth.
Version boundary
Use the v3.4.3 tagged implementation for current development. Historical v3.4.2 passports and qualification artifacts remain valid evidence under their original version labels and must not be silently relabeled.