A.15.1:10 - Work-claim interpretation checks
When another decision relies on a work occurrence, perform three quick checks:
- Method-description interpretation. Does
methodDescriptionRefresolve to the selectedU.MethodDescriptionepisteme under the effectiveU.ReferenceSchemeused by the receiving claim? If the claim also says this is an edition of an earlier description, does the exact C.2.1EpistemeEditionRelationobtain? If two local senses must be related, test an F.9 Bridge and state the bounded use separately rather than treating the reference change as a Bridge. - Performer and conditional assignment coverage. For every admitted
U.Systemnamed as performer, does section 4.0 recover its A.13 basis? If this receiving check expressly consumes precise assignment-bound attribution, does the account also cite the exact directly declared assignment species and the same obtaining occurrenceRAalready recovered through A.2.1 and A.13, and does F.6 obtain for the already admitted Work and thatRA? DoesRAcarry the actual participant values, have that System as holder, and cover the Work or exact performed part? If no attribution is current, stop after the performer and Work checks. If the conditional attribution branch fails, retain the Work and performer and repair or reject only the assignment occurrence or F.6 attribution that failed. - Evaluation boundary. Has separately performed evaluation or acceptance work applied the selected criterion episteme to the independently obtaining relations involving the Work occurrence, changed subject, measurement results, or delivered entity that the criterion actually requires? If not, no acceptance verdict follows. If yes, keep the evaluation work, result episteme, verdict content, evidence, and acceptance relation separate. Claim edition continuity only when the exact C.2.1 relation obtains.
These checks tell the reader which description, assignment, criterion, evaluation, and relation to cite. They neither create one judgment-context object nor make acceptance part of work identity.