Context
On 2026-10-11, working on what makes a combined form one system (the dancing
couple, CASE-046; the owner’s CLAIM-175), the owner pointed to
their Mathematics of Meaning project (“I think there might be some useful
ideas regarding system boundary identification in there”). It is a Luria
record of its own (dmarx/mathematics-of-meaning). Its prefixes are CLM,
ARG, POS, CON, LIT, ADR and DP. Its status means standing (does the record
still assert it), and its tags grade the footing (derived, borrowed,
asserted, programmatic, stipulated).
A survey found what this record lacks: a priced boundary criterion (MOM-CLM-160 with MOM-CLM-144 and MOM-LIT-018), a persistence criterion (MOM-CLM-153), a gluing test for unity (MOM-CLM-165), and the caution that sufficiency-based individuation is relative to a target (MOM-POS-001). The owner then asked: “register MoM as a remote and then dual file anything we need from there on nucleation directly”.
Decision
- The remote.
MOMinluria.yaml, schemes CLM, ARG, POS, CON, LIT, ADR and DP at theirrecord/directories,ref: main. A citation is writtenMOM-CLM-160. Codes are not shared between the records. - Dual filing, extended to claims. ADR-013 lets a work be held in both
records when each reads it for its own question. This decision applies the
same rule to MOM’s own claims and positions:
- A needed MOM claim or position gets an entry here in the scheme that fits this record’s use. That is usually a CLAIM, in the line that needs it. MOM is the owner’s own reasoning, so it is the record’s own proposition, not a reading of someone else’s work, which would be a THEORY.
- The entries name each other one way. The entry here cites the MOM code in its summary and body, and its first history note says it is dual-filed. MOM is not edited from here.
- Status is this record’s own. MOM’s
derivedgrade is not inherited. An entry isActivehere only if this record re-ran the check or reads the result as standard. Otherwise it isProposed, with the reason in the entry. - Disagreements are reported, not fixed across the boundary. The same rule as ADR-013.
- Works held in both. Where MOM’s LIT and an entry here are the same work, ADR-013 applies as written. Each names the other. So far that is Simon (1962): MOM-LIT-018 and LIT-905. And Bruineberg et al. (2022): MOM-LIT-023 and LIT-603.
- Only what is needed. An entry is dual-filed when a question here uses it, and the curation entry that files it says which question. MOM is not mirrored.
Alternatives
- Cite across only. With the remote alone, the citation would resolve.
But a CLAIM here cannot
rests_ona MOM code, so the argument chains this record draws (ADR-032) would stop at the border. MOM’s status would also stand in for this record’s credence. - File MOM’s claims as THEORY. THEORY is a reading of a work’s account, sourced from a LIT. MOM’s claims are the owner’s reasoning, often repairs of the owner’s own drafts, and the record’s own propositions are CLAIMs.
- Copy MOM’s status and grade. That would let a
derivedtag there stand in for a check here. MOM’s own design principles (MOM-DP-010) ask that a check be run before a claim is called derived, and this record does the same.
Consequences
- The first batch. Five MOM entries are dual-filed as CLAIMs in
distributed-agency, from MOM-CLM-160, MOM-CLM-144, MOM-CLM-165, MOM-CLM-153 and MOM-POS-001. Three were re-checked by script before being made Active (curation entry of the same date). - The lint does not check MOM citations. This was fired on
2026-10-11 (curation entry of that date). A planted MOM-CLM-999 passed
luria lint, because remote codes resolve by filename convention without checking that the file exists.luria remotes --checkcannot verify a private repository anonymously. Until something better exists, a MOM citation is checked against a local clone of the repository when it is filed. All eight cited so far exist at MOM commit d987e2a. - Drift is possible. A MOM claim may be retired after its twin is filed
here.
luria remotes --pincan endorse the cited MOM documents by hash, so that a change upstream is reported. That is not done yet, and it waits for a second need.