The engine, graded by its own instruments

Proof.

Most analytics platforms ask you to trust the platform. OMNIA publishes the instrument's own graded results — validation against reference signals, forecasters scored by their misses, confidence that goes down, refusals on the record, and tamper-evident receipts for every claim.

Measurement-first: the stance

The dominant architecture in data platforms begins at ingestion — integrate everyone else's sensors, build an ontology above them, own the decisions. It is powerful, and it has a structural blind spot: it owns no ground truth. No calibration chain, no native consent, no provenance below the point of arrival.

OMNIA inverts the stance. Measurement is the foundation the engine owns: canonical records with calibration references, consent that travels inside every record, an append-only ledger where confidence is earned — volume × diversity × recency — and every score opens to its exact evidence. The fusion, forecasting, and decision layers are grown natively on top of that foundation, not bolted over someone else's.

The question this page exists to answer is the one ingestion-first platforms cannot: not "what did you receive?" but "what was measured, on which instrument, under which calibration, with whose consent — and how has the instrument scored so far?"

232/232
Engine tests passing
Every principle below is enforced in code and covered by tests — a principle that isn't executable is a slogan.
925
Hash-chained ledger entries
Each entry commits to everything before it; altering any historical byte breaks every subsequent hash.
+0.84
Best forecaster skill vs base rate
And the worst sits at −2.24, published on the same leaderboard. Predicting the base rate earns exactly zero.
6/6
Scientific validation references
440 Hz, 1 kHz, known sine RMS levels, digital silence, 120 BPM — measured vs expected with tolerances, pass/fail published.

The ten principles — engine law, not brochure copy

Each is enforced in code in the OMNIA engine and covered by its test suite.

01Measurement first, meaning attached, never overwritten. The evidence hierarchy — measured → calculated → reported → inferred → predicted — is immutable.
02Every number opens to its receipts. Influence weights, forecasts, and conviction blends are explainable to exact evidence node IDs.
03Confidence is earned three ways — volume × diversity × recency. Monotype or stale evidence caps confidence no matter the count. Confidence can go down; that is what makes it believable when it is up.
04Every outcome traceable to a measured moment wherever source material exists — outcomes rest on canonical measurement, not bare metadata.
05Declining is a valid output. Forecasters refuse below their evidence thresholds and say why. No number is fabricated to fill a cell.
06Forecasters earn trust like subjects earn influence — Brier scores, skill against the base rate, honest small-sample intervals, on an append-only ledger.
07Identity is never influence; wealth is never influence. Demographics are not inputs and never will be. Financial connections contribute existence and freshness only.
08Metadata over content. Cross-system syncs carry ids, timestamps, categories, slugs — never names, emails, message content, or amounts.
09Provider facts stay provider facts — weather, geomagnetic, geocoding, and event data preserved as attributed reported observations, never relabeled as measurement.
10Consent travels with every record, and leaving is always free. Deletion, export, and withdrawal are permanent non-paywalled rights. No score directly authorizes currency.

Receipts — tamper-evident certificates for every claim

Every record ever appended to the evidence ledger is hashed (SHA-256 over canonical sorted-key JSON) and chained: each entry commits to everything before it. Any influence score, forecast, or outcome can ship with a certificate a third party verifies without trusting OMNIA — recompute the record hash, recompute the chain, compare the head. Altered content is named as altered; superseded versions as superseded.

Honest scope, stated on the certificate itself: this is hash-chaining — tamper evidence — not asymmetric signature. Signatures arrive with identity keys, and the certificates will say so when they do.

GET /v1/receipts?recordId=omnia.outcome/v1:billchat:conversion:…
→ { record, verification: { recordHash, chainPosition: 132, chainHeadHash, chainLength: 925 }, howToVerify: [3 steps any auditor can run] }