Clear explanations of operational questions
Three guides to concepts that matter in every institution that holds, trades or leases assets.
Why these guides
Many operational errors in institutions come from ambiguity around a few basic concepts: which asset a quantity belongs to, when a trade request becomes a trade, and what has to come back under a leasing contract.
Each guide explains one of these concepts in operational terms and closes by showing how HOLD OS works with it.
Guides
-
Which asset does each quantity belong to?
Why an asset’s identity and unit matter more than its name, and how they preserve historical records.
-
What changes between a request and a recorded trade?
The boundary between the intent to trade and its financial effect, and the role of an explicit price and authority.
-
Principal and rent are separate obligations
Why keeping principal and rent apart is the simplest way to avoid ambiguity in a contract.
Related capabilities
-
Gold, Silver and Custom asset management
A distinct identity, unit and precision for each asset.
-
Trade workflows
Manual trades with explicit quantity, price and authority.
-
Asset leasing
Principal and rent as two separate obligations.
See these concepts in the product
In a walkthrough we follow these same concepts through HOLD OS using your institution’s scenario.