Home  /  Product tour

From observation to verified receipt.

Five stages, one honest chain. Everything below uses the published, sanitised conformance fixtures — demonstration data with public test keys, never presented as live. The live signed feeds are one click away throughout.

The chain.

Stage 1 · Observation

Something happens in the world

A satellite reads space weather. An agency publishes an exploited-vulnerability entry. A severe-weather alert goes out. Dynamic Feed's sanitised gold fixtures preserve three such observations exactly as envelopes carry them: NOAA space weather, CISA KEV, NWS severe weather.

Sanitised demonstration fixtures — not current live observations

Stage 2 · Provenance and freshness

The observation carries its own paperwork

Every envelope records the source, its URL and licence, the observation time, and a freshness state: live, stale, or unavailable — never a fabricated reading. Cross-source concordance says whether independent witnesses agree, diverge, or only one responded.

"provenance": { "source": "…", "licence": "…", "observed_at": "…" },
"freshness": { "state": "live | stale | unavailable", "age_seconds": … }
Stage 3 · Machine decision

An automated system consumes it and acts

An agent approves, escalates, defers or routes, using those observations at a specific moment. The decision inherits everything above: which sources, how fresh, what agreed and what did not.

Stage 4 · Decision Receipt

What it relied on is preserved

The inputs, their provenance and freshness, the checks that ran, and the verdict are sealed into a signed, timestamped record. Any later change to a single byte breaks the signature — tamper-evident, and honest about what it does not prove: a valid signature never claims objective truth, completeness or safety.

See a live Decision Receipt demo.

Stage 5 · Independent verification

Anyone re-checks it, without trusting us

The receipt verifies in your own browser: schema, canonical bytes, digest, signature, key lifecycle, evidence linkage — each check shown separately, never collapsed into one green tick. Try it now: load a fixture on /verify, then change one value in the tamper laboratory and watch exactly which check breaks.

Conformance verification uses public test keys — no production trust implied

Follow the chain yourself.

Explore a Decision Evidence Graph · verify a receipt · agent decisions · vulnerability decisions · vendor due diligence · weather-dependent operations · bring us one AI decision.