Glossary
Canonical term definitions used across user, merchant, developer, tokenomics, and security documentation to keep operational meaning consistent.
#
Use these definitions whenever a term appears in more than one audience track so readers do not have to guess whether the meaning changed.
#Mandate
The scoped authority record that defines what a principal, operator, or governed runtime is allowed to request or approve.
#Capability
The product or workflow surface that a caller may access when the rest of the authority checks are also satisfied.
#Policy version
The named ruleset or revision that explains how a workflow was evaluated at a specific moment in time.
#Risk assessment
The independent evaluation that decides whether a valid request should proceed, be blocked, or be routed for review.
#Authorization
The governed decision that a specific request may advance toward execution under the documented identity, mandate, policy, and risk context.
#Financial intent
The structured request describing the financial outcome being asked for, together with the references and constraints needed to judge it safely.
#Provenance
The evidence chain that links an original request to its approvals, execution steps, final state, and any later intervention.
#Reservation
A temporary hold or protected allocation of capacity, balance, or workflow state before a terminal outcome is recorded.
#Settlement
The stage where the workflow reaches a final recorded financial outcome that downstream systems can reconcile against.
#Confidentiality and private execution
Protected processing for sensitive financial state that preserves the same governance, risk, and finality expectations used in the rest of Ryvra.