An agent can remember a fact. Can it explain why it knows it? This page replays one real session — Nemotron answering, the field deciding what to keep — and re-verifies every seal in your browser, no server, no trust required.
Retrieval answers "what is similar to this question." It does not answer why a memory was available, what decision depended on it, or whether the answer it gave last month would still hold today. For an agent that runs for months and accumulates memory, that gap is where trust quietly erodes — the agent's behavior drifts, and nobody can point to which historical event caused it.
This system keeps both: the operational state the agent needs
to behave right now, and the forensic trajectory — a hash-linked,
signed custody chain per memory — that explains exactly why it
behaves that way, with a counterfactual replay that can answer
"what if that one event had never happened?" as a sealed,
reproducible report instead of a guess.
| typical retrieval memory | returns similar documents |
| this system | serves memories and seals the receipt |
| "trust the embedding" | the model may declare; only corroboration changes the field |
| "it felt related" | do(T_i=∅) excises one
transition, replays production recall, seals the delta |
Two models, both served by Nebius Token Factory, do real work
in the loop you're about to watch: nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B
reads the retrieved memories and answers; Qwen/Qwen3-Embedding-8B
produces the vectors retrieval ranks on. Neither touches sealed state.
Nemotron's answer carries a declaration — which memory ids it says it
used — and that declaration is recorded as a claim. A
deterministic engine then checks whether the answer text actually
overlaps the content of each declared memory; only the memories that
pass that check get reinforced. A model that declares a memory it
was never served, or that a hostile memory tries to steer, gets
caught here — its declaration lands on the custody chain as evidence
against it, never as authority over the field.
Everything above came from one JSON file,
session.recording.json. Its narration sits beside a
sealed, signed evidence bundle (the same mneme-cf-bundle/v1
DSSE envelope this product's offline and clean-room Go verifiers
already accept — nothing about its format changed to make this page).
The checks below run in this browser, over the bytes you're looking
at: they recompute every hash and signature from scratch and either
confirm the claim or say exactly where it breaks.