A.3.4:5.3 - Specification repair

A safety specification is revised so that an emergency-stop boundary no longer permits two incompatible readings. First result: EmergencyStopSpec-E1 and EmergencyStopSpec-E2 are different C.2.1 epistemes because their claim content differs. EpistemeEditionRelation(EmergencyStopSpec-E1, EmergencyStopSpec-E2) may relate them when its historical-continuation predicate holds; neither is one continuing changed episteme.

A.3.4 may instead identify a change of EmergencyStopSpec-Carrier-17 : U.PresentationCarrier if E.24.PUB identifies the same carrier across the editing interval and the before/during/after borne-expression facts plus carrier-continuity rule are present. If the carrier identity, facts, or rule are missing, no carrier transformation follows. If editing U.Work first constituted EmergencyStopSpec-E2, name that work and the transformation by which the later identity closed. Apply 4.2.4 to the work-to-change pair, then apply A.15.PROD to the change-to-identity pair. Each connection needs a matching predicate or valid local compound basis; preserve the applicable A.6.RCD stop for either pair that lacks its required basis. The repair method, ambiguity-removal assertion, review result, and publication of the later episteme remain separate.