'Oracle' means provenance, not omniscience
The metaphor earns its keep — consultable, shows its work, never infallible.
An oracle, in the ancient sense, was consultable: you asked, it answered, and the answer came with a record of how it was reached. The modern AI version dropped the record and kept the certainty. We kept the record and dropped the certainty. That is the whole difference, and it is the difference between a category and a feature.
There is a word in our category that we use carefully, because it is borrowed from a tradition that claimed to know the future. "Oracle" now gets attached to any system that outputs a number with confidence. We use it for the opposite reason. The oracle in our architecture is consultable — you ask, it shows its work — and it is never infallible. The word earns its keep by the first property, not the second.
Provenance, not omniscience
An oracle that shows its work is a provenance machine. The output is a forecast; the artifact is a per-output, hash-chained manifest (BR-842) that records which NodeVersions the query read, which model version ran, which of the 23 A2A agents participated, and a replay anchor that lets a third party reproduce the computation bit-for-bit. The manifest attests that the output is reconstructable. It refuses to attest that the output is correct. Certified ≠ True is the line the manifest does not cross — and crossing it is what would make the rest of what it attests worthless.
Why consultable is the load-bearing word
A consultable system is one you can interrogate after the fact. You do not need to trust the oracle; you need to be able to check it. That is the property a regulator reaches for when asking "show me how you decided," and it is the property a board reaches for when asking "what if you are wrong." Both questions are answered by the same artifact: the manifest, the distribution, the replay hash. The oracle is not the answer; the oracle is the record that lets you verify the answer.
The oracle is not the answer. The oracle is the record that lets you verify the answer — and the refusal to claim more is what makes the record credible.
- Consultable: you ask, it shows its work — provenance and replay, not authority.
- Never infallible: the manifest attests reproducibility, not truth (Certified ≠ True).
- The record is the product: the manifest, the distribution, the replay hash are the deliverable, not the number.
What the word does not mean
"Oracle" does not mean the system knows what will happen. It means the system can show, exactly, how it arrived at what it says — and that you can rerun that computation and get the identical bytes. We are pre-revenue, building the POC; the provenance substrate is built, and the calibration that would earn the word "probability" for the outputs is gated (Gate 1b, a shadow run beating a disclosed baseline on one series). The metaphor is honest only if both halves hold: consultable, and never infallible. Drop either and you have a different product — one that fails procurement the moment it is asked the question it cannot honestly answer.
The oracle does not tell you what is true. It tells you how it got there, in a way you can replay. That is the only honest version of consultable, and it is the one the category actually needs.
— category note