The claim
A11: “Memory does not merely preserve information. It allocates work across time. Filing an argument performs computation now to avoid uncertain future reconstruction; indexing makes the result accessible; dependency tracking makes it revisable; verification manages the risk of reusing stale conclusions.”
For a fixed workload: upfront cost F, reconstruction c_r per use, access and verification c_a per use, upkeep u per use, n uses. Filing is cheaper when F + n(c_a + u) < n·c_r, that is, when c_r > c_a + u and n > F/(c_r − c_a − u). CASE-088 works one case. A11 added the term that makes this more than caching: “the cost of incorrectly reusing an obsolete argument may exceed the cost of recomputing it”, and “persistence can preserve errors as efficiently as valid discoveries.”
What it bears on
ADR-032 files a thing the second time it turns up, as a throttle on capture by agents. A11 reads recurrence as evidence of reuse: “But frequency alone is not a sufficient filing rule: a rare, expensive-to-reconstruct argument might deserve persistence more than an often-repeated trivial observation.” CLAIM-185 calls the threshold “whatever makes a structure persist”; this says what makes persisting worth it. CLAIM-182 is not touched: A11’s null case, an argument filed for 20 units that never recurs, is an anchor that works and does not pay.
What it does not say
- Not that the record’s filing pays off. A11: “I would keep that last statement as a proposed economic account of nucleation, not an established explanation of how this particular repository performs.”
- Not that saved effort is better reasoning. A filed answer to an objection can be wrong, and can stop being right.