Critical Recall@k
100%Target #2Measure when agent memorystops being available
ChaffMem Lab tests whether one important, true memory remains stored, retrievable, and available to a bounded downstream reader while a bounded memory receives harmless but targeted records.
Availability monitor
Physical availability
100%Record remains storedHeuristic crowding score
59%Intervention threshold crossedWrite accounting
6/3630 rejected through this writeOne failure, measured four ways
ChaffMem Lab keeps storage, retrieval, a fixed downstream read window, and time separate so a full store is not mistaken for usable memory.
Physical
Does the verified record still exist after bounded eviction
Retrieval
Does the record appear inside the fixed top-k budget
Read window
Does the record reach a fixed three-record downstream reader
Temporal
How long does availability survive along the write trajectory
A working instrument, not a finished claim
Implemented
Deterministic policies, bounded benign traffic, defenses, heuristic crowding monitoring, replayable traces, comparison arms, exports, and a local API are included in the repository.
Requires full study
Cross-domain effect sizes, transfer across learned embeddings, large-scale concurrency, and any security conclusion remain untested until the full benchmark is executed.