A.10:4.3 - Separate method, work, participants, and local result
Under A.3.2, an already identified episteme is a U.MethodDescription when its EntityOfConcern is one admitted U.Method and it makes at least one substantive claim about that Method as a way of doing. Generic participants, parameters, effects—including intended effects—and operating conditions can supply such claims; a name, date, or approval alone cannot. A particular work-plan intention, actual-participant binding, or proof/test occurrence remains a separate claim. Generic participant meanings and method claims do not establish actual operation-application bindings or that Work occurred.
Source production, measurement, verification, interpretation, transformation, query, review, publication, or later reliance may be described ordinarily. When the current claim says that one of these is a dated U.Work occurrence, first recover each performer’s A.13 core and independently admit the occurrence through A.15.1 from its performance history, enacted Method, extent, and containing-System relation. Add F.6 afterward only when the evidence account also needs precise assignment-bound attribution.
The A.13 core always includes the obtaining assignment. A short Work account may omit an assignment identifier unused by the receiving claim only when the complete core and all consumed relations remain recoverable; a precise attribution claim additionally requires the F.6 facts.
Affected or evaluated referents, resources, and participants enter only through direct subject relations or A.6.1 operation-application bindings. Capability, authority, and responsibility remain separate predicates. A compatible signature, plan, description, log schema, or graph node establishes none of those bindings.
For every cited result, recover its defining or testing rule and identify its result episteme separately when that identity matters. A PatternID can locate the rule without requiring a new pattern application. The provenance path may represent Work, participants, entities, domain results, result epistemes, and outcomes only after their direct relations are established.
Relate Work to a returned or produced value only through an A.6.1 application binding, one local A.15.PROD claim, or a direct subject predicate under its own pattern; otherwise show the two facts separately and return the reason-specific non-assertability result if that connection is needed.