NOAN adds fact rationales; evidence still needs human approval

NOAN’s November 3 update lets agents attach an optional source‑backed reason when creating or updating a fact. A request to change the record is not that reason: reviewers need evidence supporting the claim. NOAN says a person still verifies it. [November 3 entry](https://www.getnoan.com/changelog)

The reason appears on approval cards, version history and decision details; absent reasons stay hidden. MCP fact listings and REST version reads return the rationale or null. The assistant’s chat thread is recorded as a private source and excluded from API returns, rather than disclosed alongside the rationale. [NOAN changelog](https://www.getnoan.com/changelog)

For the broader architecture decision, the [trusted‑memory and authority reference](https://opentools.ai/resources/enterprise‑system‑design) frames memory trust and audit boundaries as design questions. It is a learning resource rather than product‑control validation. Reading and taking notes, February 2021; archive source‑and‑notes context, not NOAN’s interface or proof of verification. Photo: Shixart1985 / Nenad Stojković / [Wikimedia Commons](https://commons.wikimedia.org/wiki/File:Hands_holding_an_open_book_as_someone_writes_in_a_notebook_surrounded_by_scattered_pages.jpg), [CC BY 2.0](https://creativecommons.org/licenses/by/2.0). Cropped and resized; no endorsement implied.