A.12:4.3 - Episteme And Publication Cases
If a source says “the document updates itself”, identify the acting participant and decide which changed-object reading the claim needs:
- Carrier-change reading. One exact publication file, representation carrier, or source-record carrier continues through a separately grounded change under its direct carrier identity rule. It may fill
changedSubjectRefas that exact carrier, not as aU.Holonmerely by carrier form; use A.3.4 only when the bounded change of that same referent is independently admitted. - Episteme-edition reading. Changed claim content identifies another episteme, with the predecessor, successor, and exact edition relation governed separately. Do not call it transformation of one unchanged episteme.
- Relation-occurrence reading. One exact episteme-related direct relation—for example constitution, empirical grounding, edition, reference, or publication use—obtains when its actual participants satisfy its direct predicate. Its direct identity and change rules determine whether that occurrence continues, ceases, or is replaced. Use C.2.1 for episteme identity and edition distinctions and E.17 or E.24.PUB for publication use. The relation occurrence does not fill
changedSubjectRef; if an actual change is also claimed, identify its continuing subject and A.3.4 facts separately.
Choose the reading before filling a singular field; carriers, epistemes and relation occurrences are not interchangeable values. Call the acting entity a U.System only after A.1 recognition, and fill a work-facing assignment only when that U.SystemRoleAssignment obtains. Use C.2.1 for episteme identity, E.17/E.17.2 for publication relations and E.24.PUB for the publication-form boundary when those claims are needed.