A.3.4:4.8 - Multi-reading source phrase

Use this example when one phrase seems to name method, mechanism, formal construction, work, evidence, and transformation at once:

“The workflow algorithm transforms the emergency-stop specification, and the proof shows the new plant boundary is safe.”

Keep these objects separate:

• the workflow or algorithm may designate a U.Method or U.MethodDescription;
• the proof is a claim-bearing episteme using a declared formal substrate;
• when claim content changes, the earlier specification episteme and the later specification episteme are distinct C.2.1 identities; EpistemeEditionRelation relates them only when its historical-continuation predicate obtains;
• dated editing or review is a U.Work occurrence admitted under A.15.1;
• edition succession alone establishes no transformation of one continuing episteme. Open A.3.4 only for a separately continuing subject—such as a selected U.PresentationCarrier under E.24.PUB or a claim-bearing constituent organization—after naming its boundary, before/during/after facts, and continuity rule; otherwise stop without a transformation claim;
• if revision U.Work first constitutes the later episteme, open a separate A.15.PROD first-existence question: name the exact productIdentitySpecification episteme, the named applicability predicate or filled local claim that applies it to the candidate basis, subject context, and boundary, the identityClosingWork, and the work-to-change and change-to-identity predicates or local compound claims. If that specification continues an earlier specification, state the separate C.2.1 EpistemeEditionRelation only when its historical-continuation predicate obtains; without that relation, treat it as a non-continuing replacement and evaluate its applicability independently. Return the applicable A.6.RCD stop for either named connection that lacks its required basis;
• a plant change, safety evaluation, assurance claim, gate decision, and publication are separate objects and relations.

If only the proposed wording and proof are available, do not assert a project-world plant transformation. Different claim content gives two epistemes; test their EpistemeEditionRelation. Assert an A.3.4 specification-side transformation only for a separately continuing carrier or constituent organization with its boundary, before/during/after facts, and continuity rule. If the question instead concerns the later episteme’s first existence, use A.15.PROD and stop when either direct connection lacks a basis. The proof can support an assertion only through its evidence or derivation use.