Memory Manipulation
- Category
- Memory Poisoning
- Confidence
- 80% confidence
- Finding
Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
- Content
md ### Upgrade from 2.0.0 Stop **all** 2.0.0 processes first: old writers do not enforce these reservations and must not share the database with 2.0.1. Make a private backup that retains every event, nonce and ingestion digest. Choose reservations for every tenant already present in the database and every tenant allowed to write. On first startup, 2.0.1 verifies existing row counts and UTF-8 body sizes against these budgets before recording the policy. Over-quota or unconfigured historical tenants cause startup to fail without deleting their records. Do not delete history or reset the database to bypass the check; use a reviewed migration that retains replay-protection evidence. These reservations isolate retained audit data, not CPU, I/O bandwidth or total disk consumption. The byte budget counts stored event bodies, including signatures; SQLite pages, indexes, journals, backups and other programs use additional space. Provision filesystem headroom/quotas and operator monitoring separately. Enforce per-tenant request rates and timeouts at a trusted gateway for shared deployments. No automatic archival, eviction or replay-history pruning is supplied.
