The record

Generated by luria index from this project’s luria.yaml — built, not edited. A table configured is a row here whether or not anyone remembered to describe it.

This is the shape this project gave the record machinery: the document families it named, where entries are filed, where views are rendered, and what to type to add one. It is a description of luria.yaml as configured, not of what luria.yaml can hold — for the key-by-key schema, with defaults and meanings, see Luria’s configuration reference.

Referable documents

A code — ADR-012 — resolves to a document, and every reference to it in this repository is checked. luria lint fails on a bare code that was never linked; luria link --fix writes the link so nobody has to know where the document renders.

a code looks like	filed in	rendered to	in force when status is
`LIT-001`	`record/literature.d/`	`docs/literature/README.md` + tag pages	`Active`
`NOTE-001`	`record/notes.d/`	`docs/notes/README.md` + tag pages	`Read`
`THEORY-001`	`record/theory.d/`	`docs/theory/README.md` + tag pages	`Active`
`ADR-001`	`record/decisions.d/`	`docs/decisions/README.md` + tag pages	`Active`
`DP-001`	`record/principles.d/`	`docs/design-principles.md` (one page, read as a whole)	`Active`
`QUESTION-001`	`record/questions.d/`	`docs/questions/README.md` + tag pages	`Open`
`CLAIM-001`	`record/claims.d/`	`docs/claims/README.md` + tag pages	`Active`
`CASE-001`	`record/cases.d/`	`docs/cases/README.md` + tag pages	`Active`
`TERM-001`	`record/terms.d/`	`docs/terms/README.md` + tag pages	`Active`
`ARG-001`	`record/arguments.d/`	`docs/arguments/README.md` + tag pages	`Active`

What each family is

A scheme’s own account of itself, where it gives one — title and blurb on schemes.X. The table above says where a family’s files live and how its codes are spelled; this says what the family is for, which is the part a reader needs first and the part a config could not previously state (#279).

LIT — Works

One entry per work: its bibliography, its source identifier and its standing here, which is whether it is worth reading and not whether its findings are true. A work nobody has tried to read is Deferred; one whose lawful copy was not reached is Unfetched or Unavailable. Ported unchanged from the Anthology of the SOTA, so a work can move between the two records (ADR-001).

NOTE — Readings

One entry per work actually read: what it contains, assumes and shows, and how deeply it was read. Its status says Read or Skimmed, honestly. A reading is not the work’s standing, which is the LIT’s, and the two may disagree. No NOTE means the work is unread.

THEORY — Accounts

A claim about what is true, attributed to the work it comes from, with the evidence that work gives. Its status is the record’s credence in the account. A Proposed one says in promote_when what would make it accepted, and asks only for what its title asserts (ADR-065).

ADR — Decisions

A decision about how the record works, with the alternatives it rejected. It is superseded when the choice changes, and corrected in place, with its version bumped, when only a reason was wrong.

DP — Design principles

A standing value that decisions cite by number, stated as a claim someone could disagree with. Read as one page.

QUESTION — Questions

What the record is asking, filed under a line of inquiry. A question is Open until an Active claim or account answers it. A partly answered one splits into an Answered child and a narrowed Open parent (ADR-049).

CLAIM — Claims

What the record itself holds about its subject matter, as distinct from its readings of others’ (ADR-032). Each has a credence (status), a voice (role) and a warrant (demonstrated, empirical or interpretive; ADR-043). An objection is a claim. rests_on joins claims and grounds points outside them, so an argument and its objections render as chains.

CASE — Cases

An example the argument uses: a real specimen, a thought experiment, a formal construction, or a study reported, proposed or executed (ADR-042). Its standing says how much of it is fact, and reported_in says where the record got it (ADR-051).

TERM — Terms

A concept the record defines and uses, versioned by supersession. A term says what job its definition does (ADR-056). Where the record uses a concept in its own sense, it cites the term by code (ADR-038).

ARG — Arguments

What the record says about support between its entries: that these premises do, or do not, establish this conclusion (ADR-061). Its status is the verdict on the inference, not on the conclusion. “X does not show Y” is the ARG from X to Y, Rejected, with the form’s critical questions answered in its body.

What an entry must carry

Every entry carries title and date. Everything else is listed below rather than assumed: status and the axis are controlled fields the scheme declares, and every relation — the successor a retiring document names included — is a reference the scheme declares, with the conditions it states (ADR-071, ADR-125). What each scheme’s entries must carry, compiled from luria.yaml into the contract luria lint checks, with where each obligation was declared. A finding cites the same line.

LIT

extends — optional, one or more LIT codes when present (luria.yaml: schemes.LIT.references.extends) — the earlier paper this one builds on and could not stand without. Papers fork where the DESIGNS differ, practices where the RECOMMENDATIONS do, so a fork can exist at one layer and not the other (ADR-011).
extended_by — optional, one or more LIT codes when present (luria.yaml: schemes.LIT.references.extended_by) — the converse of extends, written by luria link --fix.
compared_against — optional, one or more LIT codes when present (luria.yaml: schemes.LIT.references.compared_against) — this paper evaluated itself against that one. Somebody ran the comparison; a shared topic is not one (ADR-011).
corrects — optional, one or more LIT codes when present (luria.yaml: schemes.LIT.references.corrects) — this paper shows the earlier one wrong on something it claimed. Retire by status, never by deletion — the body stays.
rivals — optional, one or more LIT codes when present (luria.yaml: schemes.LIT.references.rivals) — this paper argues for an account of the same phenomenon that the other paper’s account excludes, and neither tests or corrects the other. Settled, it becomes corrects on the winner (ADR-022).
corrected_by — optional, one or more LIT codes when present (luria.yaml: schemes.LIT.references.corrected_by) — the converse of corrects, written by luria link --fix.
supports — optional, one or more CLAIM or ARG codes when present (luria.yaml: schemes.LIT.references.supports) — the record’s own claims and arguments that rest on this work without a reading of it, written by luria link --fix from their grounds. A THEORY drawn from the work is the stronger footing
reports — optional, one or more CASE codes when present (luria.yaml: schemes.LIT.references.reports) — the cases the record took from this work, written by luria link --fix from their reported_in (ADR-051).
superseded_by — required when status is Superseded, one or more LIT or ANTH codes when present; forbidden when status is Active (luria.yaml: schemes.LIT.references.superseded_by)
status — optional, one of Active, Proposed, Deferred, Unavailable, Unfetched, Superseded, Rejected (luria.yaml: schemes.LIT.fields.status; vocabulary ‘lit-statuses’: values) — A work’s standing in this record: whether it is worth reading. Not whether its findings are true — that is the THEORY scheme’s business, and the two can disagree in either direction.
tags — required, one or more of quantum-foundations, contextuality, mathematics, game-theory, network-science, complex-systems, probabilistic-modeling, neuroscience, natural-sciences, ecology, endosymbiosis, thermodynamics, operations-research, society-and-governance, information-theory, representation-learning, learning-theory, compositionality, mathematical-statistics, information-retrieval, databases, design-rationale, social-science, causality, pragmatics, myth-and-folklore, translation, linguistics, metaphysics, mereology, agency, individuation, self, personhood, behavioral-integration, phenomenal-unity, narrative-unity, self-governance, phenomenology, social-ontology, social-identity, altruism, future-generations, moral-psychology, psychopathology-and-treatment, motivation, well-being, learning-and-conditioning, psychometrics, philosophy-of-biology, embodied-cognition, free-will, model-comparison, information-geometry, loss-landscapes, control-theory, ethics, consciousness, cognition, emotion-and-affect, philosophy-of-science, epistemology, logic, philosophy-of-mathematics, philosophy-of-language, religion, anthology-candidate (luria.yaml: schemes.LIT.fields.tags; vocabulary ‘topics’: values) — 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.
published — required (luria.yaml: schemes.LIT.fields.published)
primary_topic — derived — {tags[0]}, never written (luria.yaml: schemes.LIT.fields.primary_topic)
source — at least one of arxiv, doi, url (luria.yaml: schemes.LIT.field_groups.source)
philosophy — any of agency, cognition, consciousness, embodied-cognition, emotion-and-affect, epistemology, ethics, free-will, individuation, logic, mereology, metaphysics, moral-psychology, narrative-unity, personhood, phenomenal-unity, phenomenology, philosophy-of-biology, philosophy-of-language, philosophy-of-mathematics, philosophy-of-science, self, self-governance, social-ontology (luria.yaml: schemes.LIT.fields.tags.groups.philosophy) — the topics that are philosophical questions — metaphysics, mereology, agency, individuation, ethics, consciousness, cognition, emotion and affect, self, personhood, phenomenal unity, narrative unity, self-governance, philosophy of biology, embodied cognition, free will, phenomenology, social ontology, moral psychology, philosophy of science, epistemology, logic, philosophy of mathematics and philosophy of language. A label over the words, not a rule about how they combine (ADR-003).
flags — any of anthology-candidate (luria.yaml: schemes.LIT.fields.tags.groups.flags) — tags that mark a work for a curation decision rather than say what it is about. Carried after the topics, never first (ADR-005).

NOTE

paper — required, a LIT code (luria.yaml: schemes.NOTE.references.paper) — the paper this note is a close reading of. Absence of a note means the paper is unread (ADR-025).
reports — optional, one or more CASE codes when present (luria.yaml: schemes.NOTE.references.reports) — the cases the record took from this reading, written by luria link --fix from their reported_in (ADR-051).
superseded_by — required when status is Superseded, one or more NOTE codes when present; forbidden when status is Read (luria.yaml: schemes.NOTE.references.superseded_by)
status — optional, one of Read, Skimmed, Unread, Superseded (luria.yaml: schemes.NOTE.fields.status; vocabulary ‘note-statuses’: values) — How deeply the paper was READ — not whether it is any good, which is lit-statuses. The two disagree in every direction: a foundational paper can carry a Skimmed note, and a paper in the attic can carry a Read one, since reading it carefully is often how it got there (ADR-025).
published — derived — {published} from paper, never written (luria.yaml: schemes.NOTE.fields.published)
primary_topic — derived — {tags[0]} from paper, never written (luria.yaml: schemes.NOTE.fields.primary_topic)
tags — derived — {tags} from paper, never written (luria.yaml: schemes.NOTE.fields.tags)

THEORY

source — required, one or more LIT codes (luria.yaml: schemes.THEORY.references.source) — the work this account comes from. Same test as a practice’s: what the explanation could not survive losing.
extends — optional, one or more THEORY codes when present (luria.yaml: schemes.THEORY.references.extends) — the earlier account this one builds on — a refinement or a widening of the same mechanism, not a rival one.
extended_by — optional, one or more THEORY codes when present (luria.yaml: schemes.THEORY.references.extended_by) — the converse of extends, written by luria link --fix.
rivals — optional, one or more THEORY codes when present (luria.yaml: schemes.THEORY.references.rivals) — another account of the same phenomenon that cannot also be right, where neither yet corrects the other. Settled, it becomes corrects on the winner and a status on the loser (ADR-022).
corrects — optional, one or more THEORY codes when present (luria.yaml: schemes.THEORY.references.corrects) — this account replaces the earlier one’s reasoning. What the old account explained may still happen; only the reason was wrong.
corrected_by — optional, one or more THEORY codes when present (luria.yaml: schemes.THEORY.references.corrected_by) — the converse of corrects, written by luria link --fix.
presupposes — optional, one or more THEORY codes when present (luria.yaml: schemes.THEORY.references.presupposes) — this account takes the other’s conclusion as a premise for a claim about something else. If the other falls, this one loses a premise and needs another route; it is not a refinement of the same mechanism, which is extends (ADR-029).
presupposed_by — optional, one or more THEORY codes when present (luria.yaml: schemes.THEORY.references.presupposed_by) — the converse of presupposes, written by luria link --fix.
answers — optional, one or more QUESTION codes when present (luria.yaml: schemes.THEORY.references.answers) — a question of the record’s own that this account answers, so the question’s page shows the literature beside the record’s claims (ADR-032)
bears_on — optional, one or more QUESTION codes when present (luria.yaml: schemes.THEORY.references.bears_on) — a question of the record’s own that this account is evidence for or against, or a premise of, without answering it or a part it settles exactly; answers is for an answer (ADR-060)
supports — optional, one or more CLAIM or ARG codes when present (luria.yaml: schemes.THEORY.references.supports) — the record’s own claims and arguments resting on this account, written by luria link --fix from their grounds. Rejecting this account leaves each of them needing another route
corroborates — optional, one or more CLAIM codes when present (luria.yaml: schemes.THEORY.references.corroborates) — a claim of the record’s own that this account gives independent evidence for, without the claim resting on it. Rejecting this account leaves the claim with less support, not without its footing; a claim that needs the account names it in grounds (ADR-058)
reports — optional, one or more CASE codes when present (luria.yaml: schemes.THEORY.references.reports) — the cases the record took from this account, written by luria link --fix from their reported_in (ADR-051).
superseded_by — required when status is Superseded, one or more THEORY codes when present; forbidden when status is Active (luria.yaml: schemes.THEORY.references.superseded_by)
status — optional, one of Active, Proposed, Deferred, Rejected, Superseded (luria.yaml: schemes.THEORY.fields.status; vocabulary ‘theory-statuses’: values) — Whether the record believes the ACCOUNT, which is not what the same word means on a practice. An explanation can be Rejected while the thing it explained goes on working exactly as well as it ever did (ADR-031).
tags — required, one or more of quantum-foundations, contextuality, mathematics, game-theory, network-science, complex-systems, probabilistic-modeling, neuroscience, natural-sciences, ecology, endosymbiosis, thermodynamics, operations-research, society-and-governance, information-theory, representation-learning, learning-theory, compositionality, mathematical-statistics, information-retrieval, databases, design-rationale, social-science, causality, pragmatics, myth-and-folklore, translation, linguistics, metaphysics, mereology, agency, individuation, self, personhood, behavioral-integration, phenomenal-unity, narrative-unity, self-governance, phenomenology, social-ontology, social-identity, altruism, future-generations, moral-psychology, psychopathology-and-treatment, motivation, well-being, learning-and-conditioning, psychometrics, philosophy-of-biology, embodied-cognition, free-will, model-comparison, information-geometry, loss-landscapes, control-theory, ethics, consciousness, cognition, emotion-and-affect, philosophy-of-science, epistemology, logic, philosophy-of-mathematics, philosophy-of-language, religion, anthology-candidate (luria.yaml: schemes.THEORY.fields.tags; vocabulary ‘topics’: values) — 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.
promote_when — required when status is Proposed, Deferred (luria.yaml: schemes.THEORY.fields.promote_when)
primary_topic — derived — {tags[0]}, never written (luria.yaml: schemes.THEORY.fields.primary_topic)
published — derived — {published} from source[0], never written (luria.yaml: schemes.THEORY.fields.published)

ADR

superseded_by — required when status is Superseded, one or more ADR codes when present; forbidden when status is Active (luria.yaml: schemes.ADR.references.superseded_by)
status — optional, one of Active, Proposed, Deferred, Superseded, Rejected (luria.yaml: schemes.ADR.fields.status; vocabulary ‘statuses’: values)
tags — required, one or more of record, taxonomy, mechanism, migration (luria.yaml: schemes.ADR.fields.tags; vocabulary ‘adr-tags’: values) — What a decision is about, in the order the index shows them. Open, unlike the topics: a decision that needs a word it does not have simply gets one.

DP

superseded_by — required when status is Superseded, one or more DP codes when present; forbidden when status is Active (luria.yaml: schemes.DP.references.superseded_by)
status — optional, one of Active, Proposed, Deferred, Superseded, Rejected (luria.yaml: schemes.DP.fields.status; vocabulary ‘statuses’: values)
tags — required (luria.yaml: schemes.DP.fields.tags)

QUESTION

refines — optional, one or more QUESTION codes when present (luria.yaml: schemes.QUESTION.references.refines) — the broader question this one is a part or a sharpening of
refined_by — optional, one or more QUESTION codes when present (luria.yaml: schemes.QUESTION.references.refined_by) — the converse of refines, written by luria link --fix.
answered_by — optional, one or more CLAIM or THEORY codes when present (luria.yaml: schemes.QUESTION.references.answered_by) — the record’s own claims and the literature’s accounts that answer it, written by luria link --fix from their answers. Both, on one page, is what synthesis is
bearing — optional, one or more CLAIM or THEORY codes when present (luria.yaml: schemes.QUESTION.references.bearing) — the claims and accounts that bear on this question without answering it, written by luria link --fix from their bears_on (ADR-060)
superseded_by — required when status is Superseded, one or more QUESTION codes when present; forbidden when status is Open (luria.yaml: schemes.QUESTION.references.superseded_by)
status — optional, one of Open, Answered, Dissolved, Deferred, Superseded (luria.yaml: schemes.QUESTION.fields.status; vocabulary ‘question-statuses’: values) — Where a QUESTION stands. A question is never deleted; it is answered, dissolved or set aside, and the record keeps what it was.
tags — required, one or more of quantum-foundations, contextuality, mathematics, game-theory, network-science, complex-systems, probabilistic-modeling, neuroscience, natural-sciences, ecology, endosymbiosis, thermodynamics, operations-research, society-and-governance, information-theory, representation-learning, learning-theory, compositionality, mathematical-statistics, information-retrieval, databases, design-rationale, social-science, causality, pragmatics, myth-and-folklore, translation, linguistics, metaphysics, mereology, agency, individuation, self, personhood, behavioral-integration, phenomenal-unity, narrative-unity, self-governance, phenomenology, social-ontology, social-identity, altruism, future-generations, moral-psychology, psychopathology-and-treatment, motivation, well-being, learning-and-conditioning, psychometrics, philosophy-of-biology, embodied-cognition, free-will, model-comparison, information-geometry, loss-landscapes, control-theory, ethics, consciousness, cognition, emotion-and-affect, philosophy-of-science, epistemology, logic, philosophy-of-mathematics, philosophy-of-language, religion, anthology-candidate (luria.yaml: schemes.QUESTION.fields.tags; vocabulary ‘topics’: values) — 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.
line — required, one or more of distributed-agency, will-organization, organizational-affect, authenticity, pragmatic-transport, nucleating-argument, evidence-for-experience, learned-structure, formal-apparatus (luria.yaml: schemes.QUESTION.fields.line; vocabulary ‘lines’: values) — A named line of the record’s own argument, so that a line can be set aside as a whole and what depends on it can be found. Retracting a line is a status change on its members, never a deletion (ADR-032).

CLAIM

answers — optional, one or more QUESTION codes when present (luria.yaml: schemes.CLAIM.references.answers) — the question this claim is an answer to
bears_on — optional, one or more QUESTION codes when present (luria.yaml: schemes.CLAIM.references.bears_on) — a question this claim is evidence for or against, or a premise of, without answering it or a part it settles exactly; answers is for an answer, held or offered (ADR-060)
rests_on — optional, one or more CLAIM codes when present (luria.yaml: schemes.CLAIM.references.rests_on) — another of the record’s own claims this one could not stand without — the spine of the argument, walked as the argument chain. Retired, it leaves this claim needing another route (ADR-032)
grounds — optional, one or more THEORY or CASE or LIT codes when present (luria.yaml: schemes.CLAIM.references.grounds) — evidence from outside the record’s own argument — an account it has read (THEORY), a case, or a work cited without a reading (LIT), which is the weakest. The split from rests_on is THEORY’s own, between presupposes and source (ADR-032)
supports — optional, one or more CLAIM or ARG codes when present (luria.yaml: schemes.CLAIM.references.supports) — the converse of rests_on, written by luria link --fix.
argued_by — optional, one or more ARG codes when present (luria.yaml: schemes.CLAIM.references.argued_by) — the arguments concluding this claim, written by luria link --fix from their concludes. Two of them is two independent lines of support
objects_to — optional, one or more CLAIM codes when present (luria.yaml: schemes.CLAIM.references.objects_to) — the claim this one denies — a rebuttal, or an undermining if that claim is a premise. Walked as the dialectic chain, so an objection, its reply and the reply to that read as one thread (ADR-032)
objected_by — optional, one or more CLAIM codes when present (luria.yaml: schemes.CLAIM.references.objected_by) — the converse of objects_to, written by luria link --fix.
undercuts — optional, one or more ARG codes when present (luria.yaml: schemes.CLAIM.references.undercuts) — the argument whose inference this claim denies, leaving its premises and its conclusion standing. Kept for a claim about the subject matter that defeats an inference; a claim whose content is only “that does not follow” is the ARG’s status and body instead (ADR-061)
superseded_by — optional, one or more CLAIM or ARG codes when present (luria.yaml: schemes.CLAIM.references.superseded_by) — the claim that replaced this one, or the ARG a claim about support moved to (ADR-061). Declared here rather than left to the built-in, so it has a converse and the revisions chain can walk how a thesis changed (ADR-032)
supersedes — optional, one or more CLAIM codes when present (luria.yaml: schemes.CLAIM.references.supersedes) — the claim this one replaced, written by luria link --fix from its superseded_by
complements — optional, one or more CLAIM codes when present (luria.yaml: schemes.CLAIM.references.complements) — answers a different part of the same question, so the two belong together rather than competing. The relation the record had no word for when three accounts were wrongly set up as rivals (ADR-032). Between the record’s own claims for now; THEORY joins it once luria reads a symmetric relation across schemes correctly (dmarx/luria#358)
corroborates — optional, one or more CLAIM codes when present (luria.yaml: schemes.CLAIM.references.corroborates) — a claim of the record’s own that this one gives independent evidence for, without that claim depending on it. If this one is retired, the other loses support, not its footing. Not walked by the argument chain or by retraction; a dependency is rests_on (ADR-044)
corroborated_by — optional, one or more CLAIM or THEORY codes when present (luria.yaml: schemes.CLAIM.references.corroborated_by) — the claims, and the readings (THEORY), that give this claim independent evidence without its resting on them; the converse of corroborates, written by luria link --fix. A reading that this claim needs is grounds (ADR-044, ADR-058)
uses — optional, one or more TERM codes when present (luria.yaml: schemes.CLAIM.references.uses) — the TERM this claim is stated in, so that a term’s revision finds the claims built on it
illustrated_by — optional, one or more CASE codes when present (luria.yaml: schemes.CLAIM.references.illustrated_by) — the converse of a case’s illustrates, written by luria link --fix.
countered_by — optional, one or more CASE codes when present (luria.yaml: schemes.CLAIM.references.countered_by) — the converse of a case’s counterexample_to, written by luria link --fix.
status — optional, one of Active, Proposed, Deferred, Rejected, Superseded (luria.yaml: schemes.CLAIM.fields.status; vocabulary ‘theory-statuses’: values) — Whether the record believes the ACCOUNT, which is not what the same word means on a practice. An explanation can be Rejected while the thing it explained goes on working exactly as well as it ever did (ADR-031).
role — required, one of thesis, counter, granted, disclaimed, supposed (luria.yaml: schemes.CLAIM.fields.role; vocabulary ‘claim-roles’: values) — Whose voice a CLAIM is in, within the record’s own deliberation. Not whether the record believes it, which is the status: the two vary independently, and the mismatched pairs are the information (ADR-032).
warrant — required, one of demonstrated, empirical, interpretive (luria.yaml: schemes.CLAIM.fields.warrant; vocabulary ‘claim-warrants’: values) — How a CLAIM as stated is supported, apart from whether the record accepts it (status) and in whose voice (role). Attached to the claim, never inherited along rests_on or corroborates (ADR-043).
tags — required, one or more of quantum-foundations, contextuality, mathematics, game-theory, network-science, complex-systems, probabilistic-modeling, neuroscience, natural-sciences, ecology, endosymbiosis, thermodynamics, operations-research, society-and-governance, information-theory, representation-learning, learning-theory, compositionality, mathematical-statistics, information-retrieval, databases, design-rationale, social-science, causality, pragmatics, myth-and-folklore, translation, linguistics, metaphysics, mereology, agency, individuation, self, personhood, behavioral-integration, phenomenal-unity, narrative-unity, self-governance, phenomenology, social-ontology, social-identity, altruism, future-generations, moral-psychology, psychopathology-and-treatment, motivation, well-being, learning-and-conditioning, psychometrics, philosophy-of-biology, embodied-cognition, free-will, model-comparison, information-geometry, loss-landscapes, control-theory, ethics, consciousness, cognition, emotion-and-affect, philosophy-of-science, epistemology, logic, philosophy-of-mathematics, philosophy-of-language, religion, anthology-candidate (luria.yaml: schemes.CLAIM.fields.tags; vocabulary ‘topics’: values) — 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.
line — required, one or more of distributed-agency, will-organization, organizational-affect, authenticity, pragmatic-transport, nucleating-argument, evidence-for-experience, learned-structure, formal-apparatus (luria.yaml: schemes.CLAIM.fields.line; vocabulary ‘lines’: values) — A named line of the record’s own argument, so that a line can be set aside as a whole and what depends on it can be found. Retracting a line is a status change on its members, never a deletion (ADR-032).
works — optional, one or more of organization-of-will, what-survives-translation, luria-nucleating-an-argument, self-as-recursive-ecology, organization-of-perspective, self-without-a-sovereign, who-gets-to-say-stop, character-that-changed-parties, who-makes-the-promise (luria.yaml: schemes.CLAIM.fields.works; vocabulary ‘works’: values) — A manuscript the record’s claims are marshalled into. Membership says a claim is in the work; whether the record believes it is the status, and the two disagree (ADR-032).
defeated_if — required when role is thesis (luria.yaml: schemes.CLAIM.fields.defeated_if) — what would defeat the thesis — a kind of result or argument, stated so that the wrong kind cannot satisfy it

CASE

supports — optional, one or more CLAIM or ARG codes when present (luria.yaml: schemes.CASE.references.supports) — the claims and arguments grounded in this case, written by luria link --fix from their grounds.
illustrates — optional, one or more CLAIM codes when present (luria.yaml: schemes.CASE.references.illustrates) — a claim this case makes vivid without bearing its weight. Losing the case costs the claim an example, not a premise; that is what separates this from grounds
counterexample_to — optional, one or more CLAIM codes when present (luria.yaml: schemes.CASE.references.counterexample_to) — a claim this case shows false as stated
variant_of — optional, one or more CASE codes when present (luria.yaml: schemes.CASE.references.variant_of) — the case this one alters in a stated respect, as Northstar-B alters Northstar-A
variants — optional, one or more CASE codes when present (luria.yaml: schemes.CASE.references.variants) — the converse of variant_of, written by luria link --fix.
substitutes_for — optional, one or more CASE codes when present (luria.yaml: schemes.CASE.references.substitutes_for) — the case this one replaces in the argument — usually a fictional company standing in for a real one, so the argument does not ride on contested facts about it
substituted_by — optional, one or more CASE codes when present (luria.yaml: schemes.CASE.references.substituted_by) — the converse of substitutes_for, written by luria link --fix.
reported_in — optional, one or more LIT or NOTE or THEORY codes when present (luria.yaml: schemes.CASE.references.reported_in) — where the record got this case — the work that reports it, the reading that describes it, or the account that states its result. Provenance, not support; a case can be reported in a work the record has not read (ADR-051).
superseded_by — required when status is Superseded, one or more CASE codes when present; forbidden when status is Active (luria.yaml: schemes.CASE.references.superseded_by)
status — optional, one of Active, Proposed, Deferred, Superseded, Rejected (luria.yaml: schemes.CASE.fields.status; vocabulary ‘statuses’: values)
standing — required, one of documented, stipulated, fictional (luria.yaml: schemes.CASE.fields.standing; vocabulary ‘case-standing’: values) — How much of a CASE is fact. A case serves claims whatever its standing; what its standing changes is what it can show (ADR-032).
kind — required, one of specimen, thought-experiment, construction, reported-study, proposed-study, executed-study (luria.yaml: schemes.CASE.fields.kind; vocabulary ‘case-kinds’: values) — What kind of thing a CASE is, beside how much of it is fact (standing). The two are orthogonal (ADR-042).
tags — required, one or more of quantum-foundations, contextuality, mathematics, game-theory, network-science, complex-systems, probabilistic-modeling, neuroscience, natural-sciences, ecology, endosymbiosis, thermodynamics, operations-research, society-and-governance, information-theory, representation-learning, learning-theory, compositionality, mathematical-statistics, information-retrieval, databases, design-rationale, social-science, causality, pragmatics, myth-and-folklore, translation, linguistics, metaphysics, mereology, agency, individuation, self, personhood, behavioral-integration, phenomenal-unity, narrative-unity, self-governance, phenomenology, social-ontology, social-identity, altruism, future-generations, moral-psychology, psychopathology-and-treatment, motivation, well-being, learning-and-conditioning, psychometrics, philosophy-of-biology, embodied-cognition, free-will, model-comparison, information-geometry, loss-landscapes, control-theory, ethics, consciousness, cognition, emotion-and-affect, philosophy-of-science, epistemology, logic, philosophy-of-mathematics, philosophy-of-language, religion, anthology-candidate (luria.yaml: schemes.CASE.fields.tags; vocabulary ‘topics’: values) — 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.
line — required, one or more of distributed-agency, will-organization, organizational-affect, authenticity, pragmatic-transport, nucleating-argument, evidence-for-experience, learned-structure, formal-apparatus (luria.yaml: schemes.CASE.fields.line; vocabulary ‘lines’: values) — A named line of the record’s own argument, so that a line can be set aside as a whole and what depends on it can be found. Retracting a line is a status change on its members, never a deletion (ADR-032).

TERM

used_by — optional, one or more CLAIM or ARG codes when present (luria.yaml: schemes.TERM.references.used_by) — the claims and arguments stated in this term, written by luria link --fix from their uses.
superseded_by — optional, one or more TERM codes when present (luria.yaml: schemes.TERM.references.superseded_by) — the term whose definition replaced this one’s (ADR-032)
supersedes — optional, one or more TERM codes when present (luria.yaml: schemes.TERM.references.supersedes) — the term this one’s definition replaced, written by luria link --fix
rivals — optional, one or more TERM codes when present (luria.yaml: schemes.TERM.references.rivals) — another definition of the same concept that cannot be adopted beside this one for the same use, where neither has yet replaced the other. A Proposed term rivals the Active one it would replace. Settled, the winner supersedes the loser, which goes Superseded, or Rejected if it was never adopted (ADR-046)
complements — optional, one or more TERM codes when present (luria.yaml: schemes.TERM.references.complements) — another definition in force beside this one, for a different sense or dimension of the same subject. Neither competes with nor replaces the other (ADR-046)
refines — optional, one or more TERM codes when present (luria.yaml: schemes.TERM.references.refines) — the broader term this one is a special case of, fixed by further conditions. The broader term does not replace it; both stay in force (ADR-046)
refined_by — optional, one or more TERM codes when present (luria.yaml: schemes.TERM.references.refined_by) — the special cases of this term that stay in force beside it, written by luria link --fix
status — optional, one of Active, Proposed, Deferred, Superseded, Rejected (luria.yaml: schemes.TERM.fields.status; vocabulary ‘statuses’: values)
tags — required, one or more of quantum-foundations, contextuality, mathematics, game-theory, network-science, complex-systems, probabilistic-modeling, neuroscience, natural-sciences, ecology, endosymbiosis, thermodynamics, operations-research, society-and-governance, information-theory, representation-learning, learning-theory, compositionality, mathematical-statistics, information-retrieval, databases, design-rationale, social-science, causality, pragmatics, myth-and-folklore, translation, linguistics, metaphysics, mereology, agency, individuation, self, personhood, behavioral-integration, phenomenal-unity, narrative-unity, self-governance, phenomenology, social-ontology, social-identity, altruism, future-generations, moral-psychology, psychopathology-and-treatment, motivation, well-being, learning-and-conditioning, psychometrics, philosophy-of-biology, embodied-cognition, free-will, model-comparison, information-geometry, loss-landscapes, control-theory, ethics, consciousness, cognition, emotion-and-affect, philosophy-of-science, epistemology, logic, philosophy-of-mathematics, philosophy-of-language, religion, anthology-candidate (luria.yaml: schemes.TERM.fields.tags; vocabulary ‘topics’: values) — 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.
line — optional, one or more of distributed-agency, will-organization, organizational-affect, authenticity, pragmatic-transport, nucleating-argument, evidence-for-experience, learned-structure, formal-apparatus (luria.yaml: schemes.TERM.fields.line; vocabulary ‘lines’: values) — A named line of the record’s own argument, so that a line can be set aside as a whole and what depends on it can be found. Retracting a line is a status change on its members, never a deletion (ADR-032).

ARG

rests_on — optional, one or more CLAIM codes when present (luria.yaml: schemes.ARG.references.rests_on) — the record’s own claims the inference starts from. The premises of one argument work together; a claim with two arguments has two independent lines of support
grounds — optional, one or more THEORY or CASE or LIT codes when present (luria.yaml: schemes.ARG.references.grounds) — the readings, cases and works the inference starts from, as on a CLAIM
concludes — required, one or more CLAIM codes (luria.yaml: schemes.ARG.references.concludes) — the claim or claims the inference arrives at. One inference may conclude several theses when the same premises bear on each in the same way, so that one verdict is filed once (ADR-061)
undercut_by — optional, one or more CLAIM codes when present (luria.yaml: schemes.ARG.references.undercut_by) — claims denying this inference, written by luria link --fix from their undercuts.
uses — optional, one or more TERM codes when present (luria.yaml: schemes.ARG.references.uses) — the TERM this inference is stated in, so that a term’s revision finds the arguments built on it (ADR-061)
supersedes — optional, one or more CLAIM codes when present (luria.yaml: schemes.ARG.references.supersedes) — the claim about support this argument replaced, written by luria link --fix from its superseded_by (ADR-061)
superseded_by — required when status is Superseded, one or more ARG codes when present; forbidden when status is Active (luria.yaml: schemes.ARG.references.superseded_by)
status — optional, one of Active, Proposed, Deferred, Rejected, Superseded (luria.yaml: schemes.ARG.fields.status; vocabulary ‘theory-statuses’: values) — Whether the record believes the ACCOUNT, which is not what the same word means on a practice. An explanation can be Rejected while the thing it explained goes on working exactly as well as it ever did (ADR-031).
form — required, one of analogy, contrast, existence, formal-application, generalization, abduction, cause-to-effect, reductio, evidence, source (luria.yaml: schemes.ARG.fields.form; vocabulary ‘arg-forms’: values) — The form of inference an ARG makes, and with it the critical questions that inference has to survive (Walton’s argumentation schemes). An ARG answers each question in its body or is objected to (ADR-032).
tags — required, one or more of quantum-foundations, contextuality, mathematics, game-theory, network-science, complex-systems, probabilistic-modeling, neuroscience, natural-sciences, ecology, endosymbiosis, thermodynamics, operations-research, society-and-governance, information-theory, representation-learning, learning-theory, compositionality, mathematical-statistics, information-retrieval, databases, design-rationale, social-science, causality, pragmatics, myth-and-folklore, translation, linguistics, metaphysics, mereology, agency, individuation, self, personhood, behavioral-integration, phenomenal-unity, narrative-unity, self-governance, phenomenology, social-ontology, social-identity, altruism, future-generations, moral-psychology, psychopathology-and-treatment, motivation, well-being, learning-and-conditioning, psychometrics, philosophy-of-biology, embodied-cognition, free-will, model-comparison, information-geometry, loss-landscapes, control-theory, ethics, consciousness, cognition, emotion-and-affect, philosophy-of-science, epistemology, logic, philosophy-of-mathematics, philosophy-of-language, religion, anthology-candidate (luria.yaml: schemes.ARG.fields.tags; vocabulary ‘topics’: values) — 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.
line — required, one or more of distributed-agency, will-organization, organizational-affect, authenticity, pragmatic-transport, nucleating-argument, evidence-for-experience, learned-structure, formal-apparatus (luria.yaml: schemes.ARG.fields.line; vocabulary ‘lines’: values) — A named line of the record’s own argument, so that a line can be set aside as a whole and what depends on it can be found. Retracting a line is a status change on its members, never a deletion (ADR-032).
works — optional, one or more of organization-of-will, what-survives-translation, luria-nucleating-an-argument, self-as-recursive-ecology, organization-of-perspective, self-without-a-sovereign, who-gets-to-say-stop, character-that-changed-parties, who-makes-the-promise (luria.yaml: schemes.ARG.fields.works; vocabulary ‘works’: values) — A manuscript the record’s claims are marshalled into. Membership says a claim is in the work; whether the record believes it is the status, and the two disagree (ADR-032).
premises — at least one of rests_on, grounds (luria.yaml: schemes.ARG.field_groups.premises)

Journals

Dated observations. An entry is true about the day it was written and is never revised or consumed — the books are a view over sources that stay, which is what makes a journal safe to write into without coordinating.

journal	entries filed at	books rendered to	one book per	titled
`curation`	`record/curation.d/` `yyyy/mm/dd/hhmmss.md`	`docs/curation/`	month	Curation log
`workbench`	`record/workbench.d/` `yyyy/mm/dd/hhmmss.md`	`docs/workbench/`	month	Workbench
`devlog`	`record/devlog.d/` `yyyy/mm/dd/hhmmss.md`	`docs/devlog/`	month	Development log

Fragment directories

One file per contribution, assembled into a single document and then consumed. The point is the absence of a shared file to conflict on: every contributor writes a new path.

directory	assembled into	style
`record/changelog.d/`	`CHANGELOG.md`	append

Other projects this record cites

A prefixed code reaches into another project’s record, so a citation says whose decision it is at the point of use rather than leaving the reader to guess.

cited as	project	repository	ref
`ARXIV-ADR-001`	arXiv	—	main
`DOI-ADR-001`	DOI	—	main
`ANTH-LIT-001`	Anthology of the SOTA	dmarx/anthology-of-the-sota	main
`MOM-CLM-001`	Mathematics of Meaning	dmarx/mathematics-of-meaning	main
`LU-DP-001`	luria	dmarx/luria	main
`FX-ADR-001`	fixtures	—	main

Filing something new

Every kind this project scaffolds, straight from the dispatch table luria new itself uses.

command	files
`luria new --kind adr --title "…"`	a document in the `ADR` scheme, numbered for you
`luria new --kind arg --title "…"`	a document in the `ARG` scheme, numbered for you
`luria new --kind case --title "…"`	a document in the `CASE` scheme, numbered for you
`luria new --kind changelog --title "…"`	a fragment in `record/changelog.d/`
`luria new --kind claim --title "…"`	a document in the `CLAIM` scheme, numbered for you
`luria new --kind curation --title "…"`	a dated entry in the `curation` journal
`luria new --kind devlog --title "…"`	a dated entry in the `devlog` journal
`luria new --kind dp --title "…"`	a document in the `DP` scheme, numbered for you
`luria new --kind lit --title "…"`	a document in the `LIT` scheme, numbered for you
`luria new --kind migration --title "…"`	a migration spec
`luria new --kind note --title "…"`	a document in the `NOTE` scheme, numbered for you
`luria new --kind question --title "…"`	a document in the `QUESTION` scheme, numbered for you
`luria new --kind term --title "…"`	a document in the `TERM` scheme, numbered for you
`luria new --kind theory --title "…"`	a document in the `THEORY` scheme, numbered for you
`luria new --kind workbench --title "…"`	a dated entry in the `workbench` journal

Settings this project changed

Everything not listed here is at Luria’s default.

key	this project	Luria’s default
`issue_url`	`https://github.com/dmarx/nucleation/issues/{n}`	empty
`code.globs`	`.claude/skills/*/.md`	empty
`chains.lineage`	6 keys set	unset
`chains.theory`	6 keys set	unset
`chains.argument`	7 keys set	unset
`chains.dialectic`	6 keys set	unset
`chains.revisions`	6 keys set	unset
`chains.term-revisions`	6 keys set	unset
`patterns.inverted_premise`	3 keys set	unset
`patterns.inverted_ground`	3 keys set	unset
`patterns.answered_but_open`	3 keys set	unset
`patterns.answered_but_open_reading`	3 keys set	unset
`patterns.read_but_unreached`	3 keys set	unset
`patterns.read_but_unfetched`	3 keys set	unset
`patterns.read_but_unreviewed`	3 keys set	unset
`patterns.argued_from`	2 keys set	unset
`patterns.undercuts_support_of`	2 keys set	unset
`patterns.argued_for`	5 keys set	unset
`patterns.argued_for_undercut`	2 keys set	unset
`stale_days`	`14`	`90`
`reliance`	`rests_on`, `grounds`, `uses`, `presupposes`	empty
`load_bearing`	`5`	`None`
`lint.fail_on`	`workflow-temp-codes`, `source-mismatch`, `inverted_premise`, `inverted_ground`, `answered_but_open`, `answered_but_open_reading`, `read_but_unreached`, `read_but_unfetched`, `read_but_unreviewed`	empty
`lint.mute`	`inert-status`, `acknowledged-uniformity`	empty
`lint.baseline`	1 key set	empty
`vocabularies.topics`	4 keys set	unset
`vocabularies.lit-statuses`	4 keys set	unset
`vocabularies.note-statuses`	4 keys set	unset
`vocabularies.theory-statuses`	4 keys set	unset
`vocabularies.statuses`	5 keys set	unset
`vocabularies.adr-tags`	3 keys set	unset
`vocabularies.claim-roles`	4 keys set	unset
`vocabularies.claim-warrants`	4 keys set	unset
`vocabularies.case-standing`	4 keys set	unset
`vocabularies.case-kinds`	4 keys set	unset
`vocabularies.arg-forms`	4 keys set	unset
`vocabularies.question-statuses`	4 keys set	unset
`vocabularies.lines`	4 keys set	unset
`vocabularies.works`	4 keys set	unset

nucleation

Explorer