TOKENIZED EQUITIES / RIGHTS INFRASTRUCTURE

What do you
actually own?

A familiar ticker tells you the exposure. The wrapper’s terms tell you what you can do with it.

Start with the fine print ↓
READ THE TERMS.RECORD THE CONDITIONS.EXPLAIN THE DECISION.
01 / THE PRACTICAL PROBLEM

The price can be the same.
The permission can change.

Before a treasury lends a token, it needs more than a price feed. It needs to know whether that holder, in that jurisdiction, can take that action under the current terms.

RightsGraph proposes a common way to record those conditions—and return a decision with the reason attached.

$100,000

Illustrative position value

TRANSFERAllowed in the exampleVerified wallet. Eligible jurisdiction.
LENDPermission not establishedSame value. Different action. Missing evidence.
02 / READ IT BEFORE YOU USE IT

Three decisions worth checking.

Before a transfer

Who may receive it?

Record wallet verification, jurisdiction restrictions and any transfer conditions. A token being technically movable does not establish permission.

Before lending

What does the wrapper permit?

Separate the holder’s rights from the receiving protocol’s rules. Keep unknown terms visible instead of quietly treating them as permission.

Before redemption

When can you get out?

Capture eligible redeemers, windows, minimums and the asset delivered. A quoted stock price is not a promise of immediate redemption.

03 / A DECISION YOU CAN TRACE

Keep the source
next to the answer.

The proposed record connects each rule to its document, effective date and scope. When the terms change, the decision must be checked again.

  1. Source documentWhere did the condition come from?
  2. Effective date & jurisdictionWhen and where does it apply?
  3. Allowed, blocked or unknownWhat is established for this action?
  4. Reason & policy versionCan another reviewer follow the answer?

Understand the idea. Change the inputs. See the dollars.

Read the guide & try the simulation →
04 / THE FORMAL RULE
THE MATHEMATICAL FOUNDATION

Terms become executable predicates.

Eligible(w, a) = ∧ₖ₌₁ᵐ Pₖ(w, a)

RiskWeightᵢ = min(1, g(redemption, transfer, jurisdiction, lending))

w
Wallet attributes and verification state
a
Requested transfer, lending or redemption
Pₖ
A required rights predicate
g
A specified rights-to-risk mapping

Every required predicate must pass. The educational example uses fictional rules; it does not interpret a real issuer’s legal terms.

Try the simple simulation ↗

Rights travel with the wrapper.

Planned chain support. Each wrapper still needs its own terms and eligibility record.