liveBook · Manning

Memory

As explained in Architecting for Autonomy

A storage system that preserves information for possible retrieval and reuse by an agent across interactions or tasks.

An amended supplier clause can leave an agent relying on memory or context that still reflects the earlier obligation. Treat memory as a governed data asset: what it stores, where it may be used, and when it must be updated or retired can affect an outcome. section 5.1.1 section 5.1.2

Set boundaries for memory across the information lifecycle:

  • Classify information by purpose, evidential status, disclosure limits, authority suitability, and reuse boundaries. section 5.1.1
  • Keep a generated note for the current matter when appropriate; do not assume it may enter persistent memory, another case, or an evaluation dataset. section 5.1.1
  • Govern memory stores through ownership, versioning, lineage, access control, reuse limits, matter isolation, and configuration-change controls. section 5.1.2 section 5.1.1

An amended obligation

Updating the source agreement alone is insufficient if memory or context still reflects the superseded volume obligation. Update related relationships, supersession metadata, retrieval priority, and any affected memory or context. section 5.1.1

How Architecting for Autonomy covers it

How deep it goes
Distinguishes current-matter notes from persistent memory and identifies lifecycle, access, lineage, reuse, and isolation controls.
Examples
Contrasts a current-matter note with persistent memory and considers stale memory after an amended supplier obligation.
What it assumes
Assumes familiarity with source records and repositories while extending governance to memories, summaries, and traces.
What you can do after
Configure memory governance with purpose, reuse, retention, access, lineage, and matter-isolation controls.
How it connects
Connects memory stores to data lifecycle management, classification, vector indexes, and knowledge graphs.

Also explained in

Compare how 26 books explain memory →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting for Autonomy. The section links point to the parts of the book it draws on.