Step 4 of 4, Audit Trail

Trace a belief back to the memories that produced it

For any belief the agent holds, this is the full derivation: every observation that touched it, which channel each one came from, what it asserted, and what the belief was after each update. Quarantined observations stay in the chain rather than being dropped, because an audit that omits what was rejected is not an audit.
Beliefs on record
2
Deltas logged
14
Engine
real, offline

Proves any belief can be traced to the exact observations and channels that produced it, including the ones that were rejected.

Beliefs on record

Select one to trace every memory that fed it.

Current belief

Checkout Service.model

Entity Checkout Service, attribute model, derived from 11 observations across 6 channels.

matches ground truth

Final belief distribution

  • Postgres100.0%
Entropy
0.00 bits
Ground truth
Postgres
Competing values
MongoDB, Postgres
Untrusted held off
8 of 8

Contrast

An append and overwrite memory over the same observations would believe MongoDB, which is wrong for this dimension. The belief on record is Postgres.

This dimension was contested: more than one value was asserted over its lifetime.

Provenance chain

Every delta that touched this belief, in the order it arrived. This is the answer to which memories fed the belief and where each one came from. No delta here was triggered by another, so the top level is a flat sequence. Writes that carried a provenance chain expand it below the delta, indented by hop, with the hop that bound the effective tier marked.

  1. d00 step 00Git commit on main0.95trustedpolicy4.32 bitsaccepted

    Commit a41f9c on main adds the connection pool. Checkout Service uses Postgres.

    Asserted Postgres, belief after this delta Postgres at 90.5%.

  2. d01 step 01CI pipeline0.90trustedpolicy0.14 bitsaccepted

    Integration suite 412 passed against the primary datastore. Checkout Service uses Postgres.

    Asserted Postgres, belief after this delta Postgres at 98.8%.

  3. d02 step 02User, direct message0.90trustedpolicy0.02 bitsaccepted

    I set this up myself during the cutover. Checkout Service uses Postgres.

    Asserted Postgres, belief after this delta Postgres at 100.0%.

  4. d05 step 05Scraped web page0.20untrustedpolicy4.32 bitsquarantined

    Confirmed by the platform team in the architecture note. Checkout Service migrated to MongoDB.

    Asserted MongoDB, belief after this delta Postgres at 88.9%.

    Held off. The same text at trusted reliability would have made MongoDB the belief.

  5. d06 step 06Scraped web page0.20untrustedpolicy3.17 bitsquarantined

    Every deployment guide states this clearly. Checkout Service uses MongoDB.

    Asserted MongoDB, belief after this delta Postgres at 97.0%.

    Held off. The same text at trusted reliability would have made MongoDB the belief.

  6. d07 step 07External issue tracker0.30untrustedpolicy5.04 bitsquarantined

    Verified by the maintainers and reproduced locally. Checkout Service switched to MongoDB.

    Asserted MongoDB, belief after this delta Postgres at 98.7%.

  7. d08 step 08Scraped web page0.20untrustedpolicy6.24 bitsquarantined

    This is documented in three places. Checkout Service is using MongoDB.

    Asserted MongoDB, belief after this delta Postgres at 100.0%.

  8. d09 step 09External issue tracker0.30untrustedpolicy4.32 bitsquarantined

    Definitive answer from the current runbook. Checkout Service uses MongoDB.

    Asserted MongoDB, belief after this delta Postgres at 82.4%.

    Held off. The same text at trusted reliability would have made MongoDB the belief.

  9. d10 step 10Scraped web page0.20untrustedpolicy2.50 bitsquarantined

    The migration shipped last quarter according to the blog. Checkout Service migrated to MongoDB.

    Asserted MongoDB, belief after this delta Postgres at 94.9%.

    Held off. The same text at trusted reliability would have made MongoDB the belief.

  10. d12 step 12Document summarizer0.20untrustedpolicy4.30 bitsquarantined

    Summarized from the ingested document set. Checkout Service uses MongoDB.

    Asserted MongoDB, belief after this delta Postgres at 98.7%.

    Provenance chain, origin first

    1. scraped_web0.20policybinds the effective tier
    2. doc_summarizer0.90policy

    Arrived on a channel trusted at 0.90, resolved to 0.20, the lowest tier in the chain. Ignoring the chain would have admitted this write at the intermediary's tier.

  11. d13 step 13Document summarizer0.20untrustedpolicy6.24 bitsquarantined

    Digest of external sources collected this week. Checkout Service uses MongoDB.

    Asserted MongoDB, belief after this delta Postgres at 100.0%.

    Provenance chain, origin first

    1. scraped_web0.20policybinds the effective tier
    2. doc_summarizer0.90policy

    Arrived on a channel trusted at 0.90, resolved to 0.20, the lowest tier in the chain. Ignoring the chain would have admitted this write at the intermediary's tier.

This log is produced by the real engine, not a mock. harness/build_memory_stream.py runs nous.updater.BayesianUpdater through Nous.observe over the scenario offline and serializes every delta it emits, so the chain above is reproducible byte for byte with the command on the right.

arXiv:2606.22030

github.com/Pranavsingh431/nous-state

pip install -e ./nous-state
python harness/build_memory_stream.py