Enforcement Vescel

The execution environment that runs UsePolicy rules. It evaluates conditions, checks authorization, and executes exactly one permitted action — no discretion, no exceptions.

Think of it like a vending machine. Put in the right inputs, get exactly the right output. There's no negotiation, no judgment calls, no bending the rules. The Enforcement Vescel does exactly what the policy says, nothing more and nothing less.

How it works

When someone tries to do something with a Genome, the Enforcement Vescel:

1. Evaluates Conditions — Checks whether the UsePolicy's requirements are met
2. Validates authorization — Confirms the person has the right to act
3. Executes one action — Carries out exactly one permitted operation (like ChangeOwner or ChangeValue)

Key constraints:

• No discretionary logic — It can't make judgment calls
• No arbitrary computation — It only does what UsePolicies define
• Stateless — It doesn't remember previous transactions

This determinism is a feature, not a limitation. It means asset behavior is completely predictable and auditable. The rules are the rules, enforced by hardware, not by human operators.

Related terms

• UsePolicy — the rules that Enforcement Vescels execute
• Vescel — the broader container architecture
• Genome — the asset whose rules are enforced