The claim
Version 2. What the title of the manuscript names is the threshold at which a structure persists and becomes an anchor (CLAIM-185). Recurrence is the trigger this record is built around, and this claim is about why it is a good one for drift. Other triggers (a choice, a source, a request) make things persist too, without its throttle.
ADR-032: “The drift the exchange shows is exactly the set of things that recurred. When an agent does the filing, the risk is no longer that capture stops but that it floods, and this rule is the throttle.”
The rule does two jobs. Something said once cannot be redefined silently or re-derived as though new. Every failure CLAIM-177 lists needs a second occurrence, so coding at the second occurrence catches each failure the first time it could happen. It also leaves alone the many things that are said once and never come back.
The code is the nucleation site. Once a thing is coded, later turns can
point at it rather than restate it. Restating is where redefinition creeps
in. Structure then forms on the code: rests_on, objects_to,
supersedes. The chains render that structure, so that “the thesis moved”
becomes something visible, CLAIM-017 to CLAIM-115, and no longer something a
reader has to notice.
Luria arrived at the same threshold separately, more than once:
- its design-principles layer has the test “have we re-derived this reasoning more than once?” (LU-ADR-001);
- its working agreement says “One catch is the net working; the same catch twice means the hazard is upstream”;
- LU-DP-015 was written after a premise “had been re-derived four times without once being written down”.
That convergence is itself an instance of the claim. The idea reached its second occurrence across separate sessions, and this filing gives it a code.
What it does not say
- It does not say a second occurrence is always enough. Some first occurrences are worth coding at once: a decision, or a source.
- It does not say the record should capture everything that recurs, for ever. Luria is named for a mnemonist whose total recall crowded out meaning (LU-ADR-011). Codes are retired by status, and a principle stands in for every instance of its argument.
- Whether “second” is the right number, or only a convenient one, has not been tested.
Note of 2026-10-11: what the readings say about the threshold
Two works the claim’s analogy draws on were read the same day, and neither supports a threshold that is a count. In Ostwald 1897 (NOTE-709) the thresholds are a degree of supersaturation, past which the new phase forms without a seed, and a minimum seed size. In Vekilov 2010 (NOTE-708) the critical nucleus is a size, n* = 64Ω²α³/Δμ³, that falls as the driving force rises and reaches one molecule at a solution–crystal spinodal. If the analogy is kept, the number of occurrences that earns a code should depend on how far the exchange is from settling, and at the fast end (CLAIM-186) a first occurrence may be enough. A nucleus is also only a point of even odds of growth and decay, so a code at the threshold gives a thing an even chance of persisting, no more. None of this tests the filing rule itself. It narrows what the physics can be cited for.
The owner’s reframing the same day (CLAIM-185) answers this by moving the threshold from the count to persistence, which is how the physics defines it. This claim was narrowed to match.
Connections
- Ashby (LIT-787, Ch. 10; THEORY-307, read in NOTE-851): the benefit of a recurrent situation is that the second response can be immediate, and that needs a separate store for the situation, selected by the situation itself; interference between stores grows with the similarity of the situations. Ashby does not say recurrence should trigger capture. He says what a system must have for recurrence to be exploited. Analogy only.
Note of 2026-10-27: a second premise
The status review of this date (ADR-057) split CLAIM-177. Its observed half stays CLAIM-177, which is now Active. Its comparative half, CLAIM-483, is Proposed. This claim’s “exactly the drift that defeats an argument” needs the comparative half, that identity drift and not missing structure is what defeats such an argument, so it now rests on both.
Note of 2026-10-30: what holds it back
Two premises are Proposed: CLAIM-185, which waits on CASE-183’s inbound references per code, and CLAIM-483, whose comparison was counted in one exchange. The comparison its defeat condition names has not been made: no record that codes on first occurrence or only on request has had its drift and filing cost set beside this one’s, so whether “second” is the right number is untested. CLAIM-181’s objection, that the grammar a coded thing is filed in shapes it, is unanswered.