Topics — What a work is about. Nucleation holds whatever reading the owner files here, whether or not an Anthology of the SOTA topic could also hold it; instruction for ML practice belongs to the anthology (ADR-048). The words are seeded from the clusters the reading-time triage of 2026-09-25 found, and grow by decision.
Design rationale — recording the reasoning behind a design or decision as it is made — issues, positions and arguments, options and criteria (IBIS, gIBIS, QOC and their successors) — and why such capture systems are or are not used: who bears the cost of capture and who gets the benefit, premature formalization, cognitive overhead, and the groupware adoption problems behind them (ADR-030).
32 of 547 CLAIM documents. Back to the full index.
| # | Title | Summary | Status |
|---|---|---|---|
| CLAIM-176 v4 | Recurrence is the trigger of persistence this record is built around: coding a thing the second time it turns up captures exactly the drift that defeats an argument, and keeps capture from flooding the record | The filing rule of ADR-032 (“a thing gets a code the second time it turns up”), read as one trigger of persistence (CLAIM-185), and the one this record is built around. Narrowed to that on 2026-10-11, on the owner’s reframing. The same threshold appears in three places in luria and was found independently each time. Proposed: the rule has been applied, but no other threshold has been compared with it. | Proposed |
| CLAIM-177 v2 | In the record’s exchanges with collaborators who keep no memory, the argument repeatedly loses identity: concepts are redefined silently, objections and readings come back as though new, and the thesis changes without anyone arguing for the change | Stated as a finding in ADR-032, from seven readers coding the will exchange, and found again in the What Survives Translation? exchange by the workbench reconstructions of 2026-10-09 and 2026-10-10. Filed on 2026-10-11 as the first premise of the manuscript. Two exchanges with one owner and one assistant family, so Proposed. | Active |
| CLAIM-178 v2 | A manuscript should be a view over the argument and not its only copy: a draft written straight from an exchange drops commitments and changes its thesis without saying so, and both become visible only against a record where claims carry status and inclusion separately | Luria’s distinction between sources and generated views, carried over from files to argument. The evidence is the two “crystallized arguments” of the What Survives Translation? exchange and the manuscripts drafted from them (workbench 2026/10/09/025539, 2026/10/10/040457). Proposed: the record is kept beside the manuscript, and nothing generates a manuscript from it. | Proposed |
| CLAIM-179 v3 | When an agent does the filing, the cost of capturing argument falls on the party that would otherwise pay to re-derive it, which removes the disparity that design-rationale systems were abandoned over | The answer to the cautionary literature the owner filed before the argument schemes were built (ADR-030): design rationale goes uncaptured because whoever captures it is not whoever benefits. ADR-032 noted that agent filing changes the risk from capture stopping to capture flooding. This claim states why. Proposed: the record has run for one week. | Proposed |
| CLAIM-180 v4 | Drift is retrieval failure outside a critical distance: a restatement close enough to an idea retrieves it, one that has drifted too far is taken for new, and a code bypasses retrieval by content altogether | Proposed by the assistant on 2026-10-11, when the owner raised sparse distributed memory and Hebbian learning after CLAIM-182, and filed at the owner’s request. It reads the drift of CLAIM-177 through SDM’s critical distance (read in NOTE-242) and Hopfield’s basins of attraction (unread when filed; read 2026-10-14 in NOTE-819). The analogy is the claim; whether restatement distance predicts re-derivation has not been measured. | Proposed |
| CLAIM-181 v4 | The record fixes the grammar an argument is expressed in, though not its shape: its closed vocabulary of schemes, roles and relations formalizes early, and a move that fits no CLAIM, TERM, ARG or declared relation is forced into one or lost until the misfit is noticed and the grammar amended to hold it | Shipman and Marshall’s objection to formal representation (LIT-756), turned on this record, and narrowed on the owner’s correction of 2026-10-11. As the assistant first put it (“a crystal takes the shape of its seed”), it was wrong about crystals. A seed templates the lattice, but the habit is set by growth conditions. The objection therefore reaches the grammar of the argument, and not which claims it comes to hold. Some evidence for it is already in the record: the flourishes it declined to code, and the literature roles that “recurred” but stay in prose (ADR-032). | Proposed |
| CLAIM-182 v2 | Storage is not anchoring, addressability is: a structure that is kept but cannot be pointed at part by part does not stop re-derivation, and the same content becomes an anchor once its parts get addresses | An answer to QUESTION-038, proposed by the assistant on 2026-10-11 and filed at the owner’s request. The evidence is in the record already: the two shared transcripts persisted throughout, and ideas were re-derived inside them anyway. Their moves became citable only when the workbench reconstructions gave each turn a label. Two exchanges, and the comparison is not controlled, so Proposed. | Proposed |
| CLAIM-183 v2 | Generated views of the record, fed back into the exchange, become instruments of the argument: they show where its terms evolved faster than its formalism | From U40 of the translation exchange, the first time a generated view went back into the conversation (workbench 2026/10/10/040455). The assistant read the term-revisions chain as evidence about the manuscript, and made five moves in reply. One of them was “Nucleation itself is a case study”. One instance, so Proposed. | Proposed |
| CLAIM-184 v3 | Anchors entrench: a structure that persists early can lock in its framing, so that later structure grows on it and alternatives become hard to reach, and retirement by status is the record’s remedy only if superseded anchors stop attracting new structure | The cost side of the owner’s reframing (CLAIM-185), proposed by the assistant on 2026-10-11 and filed at the owner’s request. If persistence is what lets structure grow, it also lets early framings grow structure that is costly to undo. Grounded on Dunitz & Bernstein (unread) and Ostwald (read). The test: do Superseded entries keep drawing new citations? | Proposed |
| CLAIM-185 v3 | The nucleation threshold of an argument is whatever makes a structure persist: a persistent structure is available as an anchor, and more complex structure can evolve only on anchors | The owner’s reframing of 2026-10-11, after two readings showed that no physical nucleation threshold is a count. The threshold is not recurrence as such but whatever triggers persistence. Recurrence is the trigger this record is built around (CLAIM-176), and there are others. The readings fit the reframing: a physical nucleus is defined by persistence, and seeds that do not persist lose their power. Proposed: the generalization is stated, not tested. | Proposed |
| CLAIM-186 v4 | How fast an argument grows sets how it grows: drift tracks how fast new material arrives relative to how fast it is anchored, so a fast, prolific exchange branches, as a crystal grown far from equilibrium does, and a project memory stabilizes an argument by keeping anchoring up with arrival | Proposed by the assistant on 2026-10-11, while correcting its own crystal analogy (CLAIM-181), and filed at the owner’s request rather than on a second occurrence. The analogy is to morphological instability. Near equilibrium a growing crystal faces over, and far from it the faces branch. The evidence so far is anecdotal. The fastest stretch of the translation exchange carried two moves of thesis, and drift has not been measured against pace. There is no slow exchange to compare it with, so the claim is Proposed and untested. | Proposed |
| CLAIM-189 | Fidelity is the wrong measure of a developing argument: maturing drops and changes things legitimately, so what a record can secure is traceability, change that is announced and located, not preservation | The counter to CLAIM-191, filed with it. The transport line measures fidelity, and CLAIM-034 already says fidelity is one goal among several. A developing argument aims at maturing, and TERM-052 says maturing drops things legitimately. A fidelity profile would score legitimate dissolution as distortion. What the record secures is that change is announced and located: traceability. | Proposed |
| CLAIM-190 v2 | The anchoring measures are computed in the grammar that shapes the argument, so by themselves they cannot certify that drift fell: drift must also be judged under standards the record did not supply | An evaluation counter to the persistence and growth-rate claims, distinct from CLAIM-181. CLAIM-181 says the record shapes the argument. This says it also shapes the measures. Inbound references per code and turns per anchor are counted in the record’s own grammar, so by CLAIM-149 they cannot also certify that what they encourage reduced drift. Proposed from the synthesis review. | Superseded — by ARG-028 |
| CLAIM-191 | Restating an argument across memoryless sessions is iterated transport with only a weak channel back to the source: without anchors, restatements drift toward the collaborators’ own framings rather than at random, and a code restores continuity of transmission | The first claim joining the nucleating-argument and pragmatic-transport lines, which shared no edges. A sequence of memoryless sessions restating an argument is a chain of retellings, the telephone game of CASE-015. The transport line’s results then predict that drift has a direction, toward the transmitters’ prior (THEORY-155, CLAIM-090), and that convergence is not preservation (CLAIM-081). A code supplies CLAIM-002’s continuity of transmission. Proposed from a synthesis review; the counter is CLAIM-189. | Proposed |
| CLAIM-192 v2 | A multi-session argument’s thesis can move without any participant arguing for the move, which is a case of an organized whole’s course coming apart from its members’ intentions | Links the nucleating-argument line to the distributed-agency line. The translation exchange’s thesis moved from CLAIM-017 to CLAIM-115 to CLAIM-133 with no turn arguing either move (CLAIM-177). CLAIM-030 says an organized whole’s operative intention can evolve apart from what its members intend. The owner, the assistant sessions and the record make up such a whole, and its thesis moved that way. CLAIM-186’s test is an intervention test of both. Proposed from the synthesis review; the owner’s memory and veto are the main reason to doubt it. | Proposed |
| CLAIM-195 v2 | For an argument, the constraint set that persistence is relative to is fixed by an amendable decision, not discovered: the record stipulates what counts as the same claim persisting, which makes the choice explicit without making it non-arbitrary | Files the point the workbench of 2026-10-11 (214308) left as notes on CLAIM-185 and CLAIM-181. Viability is relative to a constraint set the theory does not supply (THEORY-134), and the will-organization line leaves “who fixes the constraint set” open (CLAIM-079, ARG-007). For an argument the record fixes it by decision (ADR-032 and its successors), so the set is explicit and amendable. That shows how one system fixes its set; it does not show the choice is non-arbitrary. | Active |
| CLAIM-250 | What a developing argument should preserve through legitimate revision is its accountability structure, what was asserted, why, how it was challenged and what justified its revision, not its propositions, so fidelity is defined over justificatory and provenance relations while propositional content changes | From the interlocutor’s reading of PR #121 and its reconciliation, relayed by the owner on 2026-10-12, on the third open tension (CLAIM-189 against CLAIM-252). It reads the tension as mostly reconcilable and moves the fidelity object from propositions to justificatory relations. Proposed and not adopted. | Proposed |
| CLAIM-295 v2 | A record of an inquiry’s justifications adds nothing for decisions its current state already suffices for: what it can add is a wider family of decisions for which what is kept suffices, and decisions a bounded agent can make that it otherwise could not | A10’s conclusion, with A5’s second claim and A10 §5’s three values of history: informational, computational and option value. It places CLAIM-250 without settling it. CLAIM-250 says what accountable inquiry ought to preserve; this says what preserving it could buy. The cases make the first half exact (CLAIM-294, CLAIM-300). The second half, that real inquiries change their questions in ways that make the purchase worth its cost, is not shown. | Proposed |
| CLAIM-299 | Decision sufficiency, historical accountability and correctness are three properties of a record of inquiry, and each can hold while the other two fail | A8’s “small mathematical structure”, with A5’s “Epistemic traceability and epistemic sufficiency are different properties”. Shown by construction: a sufficient posterior without history (CASE-082), a perfectly accountable record that is wrong (CASE-084), a current marginal that is right and cannot be revised (CASE-093). CLAIM-189 and CLAIM-190 hold neighbouring points about measuring an argument. This names the three predicates so the others can say which they mean. | Active |
| CLAIM-303 | Filing an argument moves work across time: it is paid for now, in filing, indexing, tracking dependencies and checking it is still current, against reconstruction later, so it is worth its cost only when expected reuse covers it, and recurrence is evidence of reuse, not the criterion | A11, at the owner’s request for “content to the effect of computation-storage tradeoffs”. A11’s four expenditures (materialization, indexing, dependency tracking, refresh) and its break-even condition. The arithmetic is trivial. The thesis is about the record: that its second-occurrence rule (ADR-032) and the nucleation threshold of CLAIM-185 are approximations to this trade, and can fail in both directions. | Proposed |
| CLAIM-308 v3 | Where reuse cannot be forecast, recurrence weighted by reconstruction cost is the filing criterion, not only evidence for one: filing at the first use at which reconstructing again would take the overpayment past the cost of filing is within 2 − (c_a + u)/c_r of the hindsight optimum on every sequence of uses, at most twice, and no deterministic rule without foresight guarantees materially better, under fixed known costs, with staleness left out and the cost of recognizing what a filed argument answers taken as fixed | Filed at the owner’s request, from the rent-or-buy result of Karlin et al. 1988 (THEORY-348) set against CLAIM-303’s clause that recurrence is evidence of reuse, not the criterion. In CLAIM-303’s own terms the break-even rule needs no forecast and is worst-case optimal; ADR-032’s second-occurrence rule is that rule when filing costs about one reconstruction. It does not reach staleness, which the theorem forbids rather than prices, or drifting costs, and where reuse can be forecast an expected-reuse rule can do better, so CLAIM-303’s criterion survives there. | Proposed |
| CLAIM-313 v2 | A fixed number of bins realizes one partition only when each item is stored once: with copies, overlapping partitions coexist, as hashing-based similarity search stores each item in many partitions and pays for it in space, so sortings conflict as arrangements only under a one-copy constraint, which binds bricks but not index entries | Filed at the owner’s request, from the readings on locality-sensitive hashing (Indyk and Motwani 1998; Andoni, Laarhoven, Razenshteyn and Waingarten 2017) set against CLAIM-310’s premise that “a set of k bins realizes one partition of the collection at a time”. That holds when each item is in one place. An index can hold many copies, and hashing-based similarity indexes do exactly that, trading the space of the copies against query time on an exact curve. It narrows CLAIM-310 to collections whose items cannot be copied, which includes the LEGO case; it does not touch the claim about descriptions. | Active |
| CLAIM-314 | Reusing a filed argument has a recognition cost that a fixed per-use price leaves out: certifying that stored answers cover a new question is NP-complete even for conjunctive queries, grows with the number and size of the stored definitions rather than being a constant per item, and is undefined for an item filed without a statement of what it answers, so each filing raises the cost of later reuse and per-item break-even decisions are not independent | Filed at the owner’s request, from the readings on answering queries using views (Levy, Mendelzon, Sagiv and Srivastava 1995; Chandra and Merlin 1977; Halevy 2001). CLAIM-308’s guarantee needs a fixed, known per-use cost c_a; recognizing that a stored answer covers a new question is a search whose cost depends on everything stored, so filing one item changes the price of using the others. It undermines the premise CLAIM-308 states, not its arithmetic. The hardness is worst case and over short definitions, partial reuse is cheap, and nothing here is measured on the record. | Proposed |
| CLAIM-324 v2 | In the What Survives Translation? exchange, the manuscript drafted straight from the crystallized argument changed the thesis with no turn arguing the move and dropped 24 of that argument’s items, none on request, and the second crystallized argument announced its change of question but left items out without saying which had dissolved and which were lost | Split from CLAIM-178 under ADR-043: the documented case on which that claim’s normative conclusion rests, scoped to the one exchange it comes from. The evidence is the workbench reconstructions of that exchange (2026/10/09/025539, 2026/10/10/040457). One exchange, reconstructed turn by turn by the record’s own readers; it says nothing about drafts in general. | Active |
| CLAIM-419 v2 | The record’s grammar is fixed at any moment but amendable by decision, and in practice a move that fit no scheme or relation has repeatedly been treated as a defect of the grammar and answered by amending it, so a move the grammar cannot hold is not only forced or lost; whether every such move is caught is not shown | The owner’s, at U18 of the exchange of 2026-10-22: “when we’ve encountered representational challenges, we’ve generally interpreted those as a symptom of a represntational weakness of the record and used that opportunity to mature the luria configuration, featureset, or both.” It answers CLAIM-181, which had no reply on file, with the record’s own decisions as evidence. It narrows CLAIM-181 rather than defeating it: the record shows moves that were caught and the grammar amended, and one case (ADR-032’s literature roles) where a recurring move was left in prose. | Active |
| CLAIM-469 v2 | Luria is an apparatus for a record’s objects in the operational sense: through its schemes, vocabularies, validators and generated views it realizes a system of distinctions that fixes what counts as a referable and governable object within the record, so that a split scheme makes one object two and a promoted vocabulary makes a value an entity; it keeps, enforces and propagates those distinctions; and its distinctions are revised through the record’s own use | The operational half of CLAIM-476, split from it at the owner’s review of the pull request. In TERM-089’s sense, which needs no observer and no constitutive metaphysics, luria differentiates, retains, enforces and revises distinctions among a record’s entries. That is established by how its grammar works (CLAIM-479) and by the record’s own amendments (CLAIM-419, CASE-131, CASE-178). The further thesis that the record’s objects are constituted in Barad’s sense stays in CLAIM-476, which now rests on this one. Split so that luria’s evidential role does not depend on accepting Barad’s ontology. | Active |
| CLAIM-470 v3 | Inquiry is a form of specification: a question fixes which differences would count as an answer, an inquiry adds the operations that make those differences accessible, and what it finds can stabilize into a specification that constrains later inquiry; so inquiry stands to its findings as a specification to its realizations, with one difference, that an inquiry can revise what an answer could be | The owner’s, U15 of the exchange of 2026-10-27: “inquiry is a form of specification.” It carries CLAIM-477’s analogy into inquiry: question and finding stand as specification and realization, and a stabilized finding becomes a specification for the next inquiry. A15 and A16 found Dewey and Collingwood the nearest predecessors, and counterexample-guided abstraction refinement the nearest formal case. TERM-065 already keeps a description apart from the regime it is judged under; the claim adds that the regime is itself a product of inquiry and can be its object. It does not say that inquiry makes what it investigates. | Active |
| CLAIM-472 v2 | Because an apparatus makes some distinctions determinate and leaves others unstatable, choosing and maintaining one is open to evaluation and not only to verification; but that a cut excludes something fixes no obligation, since every distinction excludes, and which exclusions matter is a judgment indexed to a standard, a scale and those affected | The owner asked at U6 of the exchange of 2026-10-27 for Barad’s ethico-onto-epistem-ology and “practices of knowing are simultaneously practices that participate in the world’s becoming”. A6 §4 and A10 §6 kept two things apart, and the claim keeps both: “the choice and maintenance of an apparatus can itself be an object of ethical evaluation”, and “Practice produces differences ⇏ A particular normative obligation”. The second half is CLAIM-363’s indexing, which A6 named as the bridge. Barad is unread here. | Proposed |
| CLAIM-475 v2 | Specifying is itself a resource-bounded realization: formulating a question takes time, concepts and computation as realizing a configuration takes energy and matter, so the questions an agent can ask are a product of what it has already realized; a stabilized specification is past inquiry stored so that later questions become cheaper to ask, and it can make other questions harder | The owner’s, U17 of the exchange of 2026-10-27: “resource constraints impact specification in exactly the same way as they impact realization. I can’t interrogate a question that takes me more time than I have to even ask it.” It extends CLAIM-470: if inquiry is specification, specifying is a process with costs, and the feasible questions are bounded before any answering starts. A17 and A18 drew a consequence the record can use: TERM-065 takes its query family as supplied, and this claim says that family is the output of bounded activity. A stable specification amortizes the work that made it, which is a separation of time scales (CLAIM-478), and entrenches what it makes cheap. | Active |
| CLAIM-476 v4 | Beyond what it does operationally, luria is an apparatus in Barad’s constitutive sense for the objects of a record, and only for them: the record’s objects are constituted, and not only made referable and governable, by the distinctions its grammar enacts, so that the same authored material is a different set of objects under a revised apparatus, and the record’s own inquiry reconstitutes the apparatus that constitutes them | The owner’s, U7 of the exchange of 2026-10-27: “oh shit, I think I may have inadvertently operationalized this notion of apparatus already, check out github.com/dmarx/luria”. Split at the owner’s review of the pull request. What luria demonstrably does, differentiating, retaining, enforcing and revising the distinctions that fix a record’s objects, is now CLAIM-469, stated without Barad. This claim keeps the further, constitutive thesis: those objects are constituted in Barad’s sense, not only made governable. That needs an argument the operational facts do not supply, and the readings press on it, since Barad rejects carrying agential realism as a template. Of Barad, only her 2012 essay is read here (NOTE-1458), and it gives no general account of an apparatus. | Proposed |
| CLAIM-479 | In the record a typed relation is more constrained than either of its relata: a claim’s content is open prose, while rests_on fixes the scheme at both ends, has supports written as its converse and says what retiring its target leaves, and none of that moves when either claim’s content does; so a relation’s rigidity is a fact about the grammar, not evidence that the dependency it records is sound | The owner’s, U6 of the exchange of 2026-10-27, against A5’s “its relationships are explicitly represented rather than metaphysically primitive”: “and yet interestingly, relations like “supports” are less flexible than the raw contents of either relata.” Shown from luria.yaml, which A6 §6 read correctly. The relation’s type is determinate where the relata’s content is not, and that determinacy is no warrant for the dependency: CLAIM-293 is the demonstrated case. CASE-131 is the instance in which the rigidity of a relation outran what its relata meant and the grammar was amended. | Active |
| CLAIM-483 | An argument developed with collaborators who keep no memory fails mainly at identity and not at structure, so that coding what recurs, not argument mapping, is the remedy, and this holds beyond one owner and one assistant family | The comparative and general half of CLAIM-177 version 1, split off by the status review of 2026-10-27 (ADR-057) and kept Proposed. CLAIM-177 now says what the record observed: identity failures recurring across six exchanges with one owner and one assistant family. Whether they outnumber structure defects was counted in one exchange only, and the population is one owner and one family, which CLAIM-177’s own body called “a pattern, not a measurement”. | Proposed |