Oracle system
A design guide for making external observations identifiable, reviewable, and reproducible before they enter an OpenForex calculation.
Publication status
Published by the OpenForex Society, the standard-setting core of the OpenForex Foundation, as part of its established standards service to the open standards community.
Version
0.2.0
Last Updated
2026-09-24
Role of an oracle
An oracle boundary supplies observations to a computation. It does not establish that a price is fair, executable, or backed by available liquidity. This package contains no active oracle feed or approved provider list.
The architecture keeps observation capture separate from kernel execution. Once captured, a snapshot can be validated and replayed even if the original source changes or becomes unavailable.
Describe every observation
| Attribute | Purpose |
|---|---|
| Instrument and unit | Distinguish an asset identifier, amount, and quoted price |
| Quote direction | State which unit is the numerator and denominator |
| Source identifier | Identify origin and collection method |
| Observation time | Record when the source says the value applies |
| Retrieval time | Record when the collector received it |
| Snapshot reference | Connect the input to a retained record |
| Quality flags | Preserve missing, corrected, stale, or restricted observations |
Use explicit timestamps and time zones. Observation time and retrieval time answer different questions and should not replace one another.
Selection and validation
A methodology should state which observations qualify, how conflicting values are treated, and what happens when too few qualified inputs remain. Freshness thresholds, outlier rules, and aggregation weights require a versioned decision; this guide does not assign universal values.
Do not silently reverse a quotation or interpolate a missing market. If a documented policy permits either, record the transformation and retain the original observation.
Failure and correction behavior
On source unavailability, distinguish an archived research run from a current-value request. A historical snapshot can support replay while being unsuitable for a new live decision. Corrected data should receive a new revision rather than overwrite evidence used by an earlier result.
Review evidence
A proposed collection pipeline should include sample snapshots, timing behavior, source-use permissions, outage behavior, and a reproducibility demonstration. Test missing fields, duplicate observations, mismatched units, stale data, and contradictory sources.
Continue with the kernel boundary, simulation protocol, and audit guide.
Sources & citation
- Material type
- Project reference
- Publisher
- OpenForex Society
- Source version
- 0.2.0
- Source-stated update
OpenForex Society. “Oracle system.” Version 0.2.0. https://openforex.io/?page=seed-content%2Foracle-system%2Findex. Include your access date when citing.
Download the exact published MarkdownText fingerprint (SHA-256)
7c05e3c4a01acb0bb5c1b742c208296129aa70a0d94dd4650817b593d63748f8This identifies the downloadable text, not an independent approval or a permanent archived edition.
Referenced material (3)
- kernel boundaryProject reference
- simulation protocolProject reference
- audit guideProject reference
Standards, implementation references and worked calculations identify their sources and publication status. Read our sourcing and corrections policy.
Reviewing a value calculation or implementation
Step 2 of 4 in this reading path.
Continue View the complete path