UREWPS — Site Header
UREWPSTM
PEOPLE • RIGHTS • EVIDENCE • OPPORTUNITY

Rights information needs context.

Rights-related information often sits in separate records, agreements, registries, and organizational systems. Understanding a right requires connecting that information to the asset, the parties, the intended action, and the applicable conditions. TWPRR™, the Worldwide Property Rights Registry, is being developed by UREWPS to provide foundational infrastructure for those connections within the Rights Economy™.

The problem is more than finding a record

A person may have a document and still need to understand what it supports. An organization may maintain reliable records while related permissions or authority sit elsewhere. A proposed action can require several sources to be examined together.

Consider a photograph used in an advertisement. The image file, a license, and records of permission may answer different questions. Finding the file does not establish whether the intended advertising use is permitted. The useful task is connecting the proposed use to the relevant right, holder, evidence, and conditions.

Why connected information matters

When those connections are difficult to see, people may repeat searches, request the same information again, or overlook a condition that matters to the decision. Clearer connections can help identify relevant sources, explain what is supported, and reveal what still needs review.

TWPRR addresses this infrastructure need. Its purpose is to connect rights-related information and context across sources and systems so people and institutions can examine a position more clearly. Specific benefits depend on the participating sources, data quality, permissions, and capabilities available.

Preserve the role of authoritative sources.

A source has a particular role and scope. A registry, agreement, or organizational system may support one part of a rights question without answering every part. That role remains important when information is connected.

TWPRR’s federated design preserves the role of authoritative systems while connecting relevant information. Federation means working across participating sources and systems. Understanding who maintains a record, its history, and the conditions for access helps users assess its relevance. Connecting records does not automatically resolve differences between them.

One house. Different rights questions.

Imagine a house with an ownership record, mortgage records, an access easement, and a rental agreement. These records describe different relationships to the same property. The owner, lender, party with specified access, and tenant may each hold a different right or interest.

The relevant evidence depends on the intended action. A question about occupancy differs from a question about ownership or specified access. Connecting the property, parties, records, and conditions makes those differences easier to examine.

This hypothetical example illustrates the need for infrastructure. It does not determine rights for a particular property or imply that these records or integrations are currently available through TWPRR.

Connect relationships, evidence, and systems.

Why relationships and evidence belong together

The Rights Graph™ represents relationships among rights-related objects, parties, evidence, and other relevant elements. Those relationships help explain which information concerns which right and action.

The Trusted Evidence Chain™ is the evidence and provenance concept used to connect and support rights-related proof. Provenance means the source and history of information. Together, relationships and evidence provide context for understanding what a record supports and what remains uncertain.

A claim states a position; evidence may support it. Verification requires an applicable standard and checking process. Connecting or recording information does not itself establish verified ownership, authority, or a legal determination.

Why design connections around APIs

An application programming interface, or API, provides a defined way for software systems to communicate. TWPRR’s API-first approach is intended to support connections across systems through these interfaces.

That approach supports the infrastructure direction for interoperability: systems exchanging and making use of information meaningfully. Each integration still requires clarity about its purpose, source responsibilities, authority, access, and information boundaries. API-first is a design approach, not a promise that every system is already connected.

Support clearer questions and responsible action.

For an individual, a clearer information picture can help identify a permission to confirm, a condition to respect, or an interest to protect. It can also show when a relevant professional or authorized party needs to review the situation.

For an institution, the starting question is which relationship its authoritative information could help explain. Connecting that information requires attention to governance, privacy, confidentiality, jurisdiction, and permitted disclosure. Identity alone does not establish authority to act or release records.

These connections can support responsible use and participation in the Rights Economy. Where permitted, a right may support licensing, leasing, or another economic activity. The opportunity depends on the right, conditions, law, jurisdiction, and available capability.

Understand the scope of each released capability.

UREWPS is developing TWPRR and related operational capabilities 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 as appropriate.

Each released capability needs a clear explanation of its scope, sources, coverage, access conditions, and limitations. Educational coverage of the 14 Asset Categories does not mean operational coverage of all categories. A missing search result does not establish that an asset has no owner or that a right does not exist.

Begin with one rights question.

For individuals

Choose one asset and an intended action. Identify the relevant right, holder, conditions, evidence, and sources. Note what needs clarification.

START RIGHTS DISCOVERY

For organizations

Identify the authoritative source or system you maintain and the rights-related relationship you want to explain. Define intended use, authority, access, and information boundaries.

Explore the federated approach

Common questions

Why connect rights information?

A proposed action can involve information held in several records and systems. Connections help explain which source, relationship, evidence, and condition matters to the question.

Does TWPRR replace source systems?

Its federated design preserves the role of authoritative systems while connecting relevant information and relationships.

Does a connection prove ownership or permission?

A connection helps put information in context. Verification requires an applicable standard and process; legal determinations remain separate.

Are all capabilities available now?

TWPRR and related operational capabilities are being developed in stages. Each released capability needs its own stated scope, coverage, sources, and access conditions.

Explore the wider rights journey.

Understanding the information is a starting point for protecting rights, respecting conditions, and participating responsibly. Where permitted, use may create economic value or opportunity.