ORDR-DESK uses precise terms for how its records are made, and precise terms are worth very little to a reader who has not been told what they mean. Each entry keeps the phrase the site publishes, gives the plain reading, and says how the figure behind it was produced — because the provenance is usually the whole explanation.
Canonical snapshot
A performance figure we publish only after it has been recomputed from each call's recorded status, prices and events and stored with a SHA-256 digest of the source fields it is computed from. Nothing here comes from a spreadsheet or a backtest, which is why a period with too few closed calls shows nothing at all rather than showing an encouraging number.
Topological structuring
The price levels an analyst marks out before a trade is taken: where the idea is working, where it is invalidated, and where it is finished. Each published version is written into a record the database refuses to update or delete; a later revision through the revision workflow is saved as a new version, and the first is kept.
Platform access protocol
The list of what a given plan lets you see and do — which research, which watchlists, which history — enforced in the database rather than by hiding buttons. A control you cannot see is a control the server would refuse anyway.
Versioned topological structures
The site's phrase for a plan written into a record the database rejects updates and deletes to. Read it that way and no further: nothing here is signed with a private key you could verify, and no record is linked to the one before it. Which guarantees are enforced, and which are not, is enumerated on the evidence integrity page.
Append-only event ledger
The running log of the lifecycle events the monitor and the publishing workflow record for a call — published, revised, triggered, a target hit, stopped, closed — written once and never edited. Performance figures are computed from this log together with each call's own status and price fields, which are not append-only; the evidence integrity page explains the difference.
Methodology version
The numbered set of rules in force when a figure was computed. When the rules change, older figures keep the version they were produced under instead of being silently recalculated, so a comparison across periods says which rules each side was using.
Several of these entries describe records we say cannot be changed. Which of those guarantees the database actually enforces, and which ones it does not, is set out term by term on the evidence integrity page — including the ones the marketing language overstates.
Read what “database-enforced” means here