glossary
UsePolicy
Programmable rules built into an asset that govern who can do what, where, when, and how often.
The programmable rules that govern what can happen to an asset. Every action that affects a Genome is controlled by a UsePolicy.
Think of it like terms and conditions built directly into the asset itself — except they're enforced automatically by the system, not by lawyers after the fact. A UsePolicy defines the boundaries of what's possible.
How it works
A UsePolicy controls four dimensions:
| Axis | What it controls | Example |
|---|---|---|
| Who | Which people or systems can act | "Only verified US residents" |
| Where | Geographic or network restrictions | "Only within these jurisdictions" |
| When | Time-based constraints | "Valid from March 1 to December 31" |
| How Often | Frequency and quantity limits | "Maximum 3 per customer per month" |
UsePolicies use IF-THEN-ELSE-GOTO logic, so they can be as simple as "anyone can do this, anytime" or as sophisticated as multi-condition rules with external data checks.
When someone tries to do something with an asset, the Enforcement Vescel evaluates the UsePolicy. If the conditions are met, the action proceeds. If not, it's denied. No discretion. No exceptions. The rules are the rules.
Key property: UsePolicies are programmable at configuration time. Once set, they're enforced automatically by the system. This means asset behavior is predictable and auditable.
Related terms
- Genome — the asset governed by UsePolicies
- Enforcement Vescel — the environment that executes UsePolicies
- Appliance — apps that operate within UsePolicy boundaries
- Onli Cloud — where UsePolicies are configured