ADR-051: A CASE names where the record got it: reported_in links it to the work, reading or account that reports it

Context

Filing the exchange “Framework Overview Request” (workbench of 2026-10-23, 03:12:25), Bigand et al.’s dance study was read (NOTE-1093), filed as a documented CASE (CASE-149), and its result stated as a THEORY (THEORY-891). The reading agent gave the CASE supports: THEORY-891, and lint refused it: a CASE’s supports names CLAIMs and ARGs only. No field linked a CASE to the work, reading or account it came from, so the link was prose.

The owner: “update the nucleation config to permit linking CASEs, THEORYs, LITs, and NOTEs (e.g. so if a reading describes a CASE we want to reference, we know where we got it)”.

Of the record’s cases, 49 are documented. Each says in its summary or body where it came from (for instance CASE-136, “Reported studies, read here from their abstracts”), and none can say it in a field.

Decision

• CASE gains reported_in, naming LIT, NOTE or THEORY entries, many, optional: where the record got this case. A LIT for the work that reports it, a NOTE for the reading that describes it, a THEORY for the account that states its result. A case may name several, as CASE-149 names the paper, its reading and the THEORY.
• LIT, NOTE and THEORY gain the converse reports, written by luria link --fix.
• Provenance, not support. reported_in says where a case came from. It does not say the case bears on the account’s truth, and it is not grounds. A case can be reported in a work the record has not read (a Deferred or Unavailable LIT), and the field then says what the case’s standing rests on.
• Scope. New and revised cases use it. Existing documented cases are not backfilled in bulk; a case gains the field when it is next revised, or in a sweep the owner asks for.

Alternatives

• Widen CASE’s supports to THEORY. It would let the refused line pass, but supports means a case bears weight for what it points at, with the converse grounds. A paper does not rest on the case the record took from it.
• Put the link on the other side only (a THEORY or NOTE describes CASE). The CASE is where a reader asks where it came from, so the field that is written by hand belongs there, and the converse is generated.
• A source: field like THEORY’s. THEORY’s source is required and LIT-only; a case’s provenance is optional and can be a reading or an account. A separate name avoids two meanings for one word.

Consequences

• The CASE pages and indexes can show provenance as an edge.
• A documented CASE whose reported_in is only unread LITs is visibly a case taken on a work’s word; that is the standing the prose already gave it.
• Nothing is required: a stipulated or fictional case, or a specimen the record holds first-hand, has no reported_in.