Rights need more than an asset name.
A useful rights discussion asks who is involved, what action is intended, which conditions apply, and what evidence supports the position.
UREWPS is developing TWPRR as foundational rights infrastructure within the Rights Economy™. Its federated, API-first design is intended to connect relevant information across sources and systems while preserving the role of authoritative sources.
For individuals and businesses
Begin with one asset and one intended use. Identify the rights question, relevant parties, conditions, and supporting records.
Begin with Rights Discovery →For institutions and partners
Begin with the source or system you maintain. Consider which relationships could be made more useful and what authority, access, and disclosure conditions apply.
Explore the federated approach →Understand TWPRR.
TWPRR Overview
Understand the infrastructure role and its place in the Rights Economy™.
Explore TWPRR Overview →Why TWPRR
Explore why rights-related information needs relationships, evidence, and source context.
Explore Why TWPRR →How It Works
Learn the intended approach and the staged development direction.
Explore How It Works →Explore the architecture.
These explanations introduce the design concepts. Specific integrations and operational capabilities depend on the scope actually released.
Federated Architecture
Connect across participating systems while preserving authoritative sources.
Explore Federated Architecture →Rights Object™
A structured representation of a rights-related object within the architecture.
Explore Rights Object™ →RightsDNA™
A structured rights-related profile within the Rights Economy architecture.
Explore RightsDNA™ →Rights Graph™
The relationship structure connecting rights-related objects, parties, evidence, and other relevant elements.
Explore Rights Graph™ →Trusted Evidence Chain™
The evidence and provenance concept connecting and supporting rights-related proof.
Explore Trusted Evidence Chain™ →Interoperability
Exchange and interpret information with its source and meaning in context.
Explore Interoperability →APIs
Defined interfaces for systems to request and exchange information.
Explore APIs →Security & Privacy
Consider information needs, permitted access, and appropriate use.
Explore Security & Privacy →Governance
Understand decision authority, responsibilities, and accountability.
Explore Governance →Rights Nexus™ is also referenced as a connective construct in the architecture. Read the introductory explanation; its expanded definition remains under validation.
See where the connections matter.
Who may use a creator’s image in an advertisement? What does a membership permit? Which publishing rights are available for a particular use?
The use-case collection explores ten initial audience offerings, from membership and creator permissions to publishing, software licenses, voice use, and event participation. These are educational illustrations of intended applications.
EXPLORE THE TEN USE CASESDevelopment proceeds in stages.
The planned direction begins with ownership search for some asset types, expands coverage, and later supports recording assets in the database and subsequently blockchain recording where appropriate.
Use the released scope as your guide.
Available sources, coverage, integrations, and access conditions must be stated for each released capability. Educational coverage of the 14 Asset Categories does not establish operational coverage of every category. A missing search result does not establish that an asset has no owner or that a right does not exist.
Common questions
Does TWPRR replace authoritative registries?
The federated design preserves the role of authoritative systems. Connecting a record does not automatically change its source’s authority.
Does a connected record prove ownership or permission?
Evidence and relationships support assessment. Verification requires an applicable standard and process; legal adjudication is separate.
Are all the capabilities described here available now?
This page describes the design and development direction. Operational availability must be confirmed against the scope, sources, and conditions of released capabilities.
How does CuBit fit?
TWPRR has the rights infrastructure role. CuBit™ has a separate economic and settlement role in the broader design. Explore CuBitRevolution.com.
Begin with the rights question.
Choose the relationship you need to understand, then examine the relevant sources, conditions, and evidence.