Skip to content

Put a wrong belief right

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. CLI 0.3.1, checked 2026-10-15.

Can I correct what it believes?

See how a fact your agents hold changed over time, and undo a correction that was itself wrong.

What you get: a memory you can audit. Every fact an agent holds keeps its history, with the reason each change was made, and a bad correction can be reversed without losing anything.

Tell Quox a fact, then correct it, in your own words:

quox · talking to Quox

Remember this fact for me: the proof-9f9be6 test colour is teal. Then update that same memory (do not save a second one) so it says the colour is green.

▤ AOCL │ L1 identity complete · allowed · 0ms

▤ AOCL │ L3 policy gate complete · proceed · 3ms

◐ MEMORY │ save ✔ MEMORY │ save │ Saved fact: "The proof-9f9be6 test colour is teal...." · 1.7s

◐ MEMORY │ update ✔ MEMORY │ update │ Updated memory: "The proof-9f9be6 test colour is green...." · 1.2s

⛓ AEE │ envelope opened · stream_success

Done. I saved the fact that the proof-9f9be6 test colour is teal, then updated that same
memory entry to say the colour is green. No second memory was created.

24.7s · 2 tools · 0 approvals

A real turn on our own install (CLI 0.3.0, 15 Oct 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 15 Oct 2026 · test report mv8y0r

Quox saved the fact, then updated that same memory rather than saving a second one. The old version is kept in the memory’s history, which is what the steps below read.

memories
quox memory list --limit 3ID                            Type           Content                                              Tags01M4QKZ3ZPRAHV8YBK2YWJNZWK    observation    Chat widget audit finished; two fixes pending...     chat, audit01M4Q2F349682GE473RTN6T1NJ    observation    Weekly backup check passed on all hosts...           backups01M4NV5JHDQ16X55JMK2FMNWHE    decision       Release freeze lifted after the security review...   release
From a real run on our own install. Contents and tags changed.

Each memory has a type (an observation, a decision, and so on), its content, and tags.

history of one belief
quox memory history 01M4NV5JHDQ16X55JMK2FMNWHEID                            State      Created                Content                                            Replaced because01M4NV5JHDQ16X55JMK2FMNWHE    current    2026-10-11 16:01:39    Release freeze lifted after the security review...
From a real run on our own install. Content changed.

This one has never been corrected, so it is the only row. When a belief is corrected, the old version stays here as replaced, with the reason in Replaced because, and the new version becomes current.

To see every decision that changed over time, newest change first:

decisions that changed
quox memory timeline --limit 3No results.quox memory timeline "release"
From a real run on our own install, where no decision has changed yet.

If a correction was itself the mistake, make the replaced belief current again:

Terminal window
quox memory reinstate <id-of-the-belief-that-was-right>

Nothing was deleted at any step. A correction replaces a belief but keeps it in the history, and reinstating swaps them back. Agents read the current belief, and you can always see how it got there.

Run quox memory history <id> again after a reinstate: the belief that was right is current, and the correction is kept as replaced.

reinstate only changes which version is current; both stay in the history.