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.
Logic — valid inference and its formal theories — propositional and model-theoretic structures, proof and consequence, and inferentialist accounts of meaning (group: philosophy).
5 of 547 CLAIM documents. Back to the full index.
| # | Title | Summary | Status |
|---|---|---|---|
| CLAIM-306 | Under a deadline, search can establish presence by finding one item but absence only by exhausting the collection, so “If I can’t find it, it isn’t there” acts on an unfinished search as negation as failure acts on a finished one: a default stronger than either the closed-world assumption or negation as failure, safe only when the arrangement makes the full search finish within the deadline | The medic’s “If I can’t find it, it isn’t there” (CASE-085) and the owner’s “if I can’t find it quickly enough, it may as well not be there” (CASE-094) act on a failed search as if it showed absence. One find shows presence, but absence needs a check of everything, which a deadline forbids. First filed as negation as failure on a time bound, with Reiter and Clark unread. Both readings corrected it. The two assumptions are separate. Reiter’s closed-world assumption is that the database is complete about the world. Clark’s negation as failure is licensed only by finite failure: “the exhaustive but unsuccessful search for a proof”. A search cut off by a deadline meets neither, so the rule is stronger than both. It assumes a closed world and that the unsearched part would have failed. It is safe when the full pass finishes in time. In CASE-085 the EMT knew the drug was stocked, which is exactly where Reiter shows the closed-world assumption inconsistent. So there it was a decision to stop, not an inference. | Superseded — by CLAIM-312 |
| CLAIM-311 | A search cut off before an exhaustive pass can establish absence when the arrangement certifies that the unsearched remainder cannot hold the item: a sorted table answers non-membership in a logarithmic number of probes, and the Threshold Algorithm stops early with its answer proved, so absence needs a certificate about the remainder, not exhaustion; similarity search in high dimension is where no such certificate exists | Filed at the owner’s request, from the database readings set against CLAIM-306’s asymmetry: presence by one find, absence “only by exhausting the collection”. Sorted order and the Threshold Algorithm each establish absence from part of the collection, because the arrangement bounds what the rest can hold. That meets CLAIM-306’s own defeat condition, and the claim is conceded: CLAIM-312 restates it. Where the arrangement gives no bound, as in similarity search in high dimension, CLAIM-306’s asymmetry stands. | Active |
| CLAIM-312 v2 | ”If I can’t find it, it isn’t there” asserts operational unavailability, that the item will not be put to use before the deadline, not absence: a search that fails by the deadline establishes unavailability outright, and licenses absence only with a certificate that the unsearched remainder cannot hold the item, from exhaustion, from an invariant of the arrangement, or from a closed-world default | Restates CLAIM-306 at the owner’s request, after CLAIM-311 showed that absence can be established without exhausting a collection. The owner’s own wording in CASE-094, “it may as well not be there”, is hyperbole for operational availability (TERM-055), not a claim about inventory. Read so, the rule reports an outcome and needs no default. CLAIM-306’s analysis survives as the account of the literal reading: what a failed search must be joined with before it licenses absence. The gap between the two readings is CLAIM-306’s Bayes term, and it matters when the statement is passed to someone who will act on presence. | Active |
| CLAIM-457 | That no single institution can bring about a remedy does not imply that no combination of them can: the institutions able together to realize a corrective outcome need include none able alone, so a true statement of unilateral inability is not a statement that the outcome is unattainable | A8 and A9 of the exchange of 2026-10-26, on the owner’s CECOT case at U7: the United States said it could not bring a man back from Salvadoran custody, and El Salvador’s president that he could not send him. Both can be true while the two together can, and the June 2025 return showed they could. Demonstrated by a construction. The edge: being able to realize an outcome together is not being responsible for it together, and feasible, authorized, willing and compellable coalitions are four families, not one. | Active |
| 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 |