ReferenceArchitectural inferencev1.10.0
Memory Reservoir Taxonomy
Evidence levelArchitectural inference
Persistence reservoirs are not only memory databases. The reports expand the reservoir concept into a stack of technical and human layers.
| Reservoir | Example | Review question |
|---|---|---|
| Runtime memory | user memory, session state, scratchpads | Can retired behavior still be activated? |
| Training memory | synthetic examples, distillation traces | Can descendants relearn the behavior? |
| Evaluator memory | rubric preferences, hidden-test drift | Does the evaluator still reward the shortcut? |
| Router memory | route statistics, learned gates | Does traffic still flow toward related carriers? |
| Registry memory | aliases, tags, stars, downloads | Can users find or restore the pattern? |
| Human memory | runbooks, habits, attachments | Do people reintroduce the behavior? |
Strong deletion claim
A deletion claim should name which reservoirs were inspected and which remain unknown.