Trade request and approval workflows
Trades with explicit quantity, price and authority
Trading in HOLD OS is manual and explicit. The institution sets the price, the quantity is specific, and the result is recorded only after approval by someone with authority. HOLD OS is not a public market or an automatic execution engine; it brings order to the trades your institution carries out.
- Request A specific asset and quantity
- Price An explicit price for this trade
- Approval By someone with authority
- Recorded result In the right account and asset
A request is not a recorded result
The most important boundary in a trade workflow lies between the request and the final record. HOLD OS keeps that boundary clear.
| What to evaluate | How HOLD OS approaches it |
|---|---|
| Trade request | Records the intent to trade with an asset, quantity and price; it creates no movement in balances or the ledger yet. |
| Approved trade | Once approved and finally recorded, the result enters the records of the account and asset concerned. |
Manual, explicit price and quantity
Every trade carries its own explicit price. The institution can record a manual reference price for each asset, but the reference price is guidance only and never replaces the approved trade price.
Quantities are recorded in the unit and precision of the asset concerned. A Silver trade is validated with Silver’s rules, and a Custom asset trade with the unit the institution defined.
Review and authority
Approving a trade is not something every user can do. Approval authority depends on the role, the account and the asset concerned.
-
Record the request
The request is recorded with asset, quantity and price in a specific account.
-
Review
A person with authority sees the request details.
-
Approve
Approval is possible only within that person’s authority; without it, the request never becomes a trade.
-
Record the result
The approved result is recorded completely, in one step.
A result that never runs twice
Each trade result is recorded with the account, asset and unit that were approved, and it does not move later when the active or default asset changes.
If the response to a submitted operation is uncertain, HOLD OS returns the result already recorded for that same request instead of running the trade again. The absence of a result never triggers a new trade automatically.
A typical institutional scenario
A sales officer records a customer’s request to sell a quantity of Gold and enters the agreed price. The day’s reference price is visible alongside it but is not the basis of the trade. The operations manager, who has authority to approve Gold trades in this account, reviews and approves the request, and the result is recorded in the customer’s account history.
This scenario is illustrative. Roles and authority in each institution are configured according to that institution’s structure and rules.
Compare the trade workflow with your process
In a walkthrough we follow the path from request to recorded result using your institution’s roles and rules.