A.3.4:4.2.4 - Keep work and production claims outside transformation identity

Do not infer a work-to-change connection from shared timing, a common affected subject, or the word successful. Once the U.Work and U.Transformation participants are identified, apply a matching current subject predicate or, when A.6.RCD disposition 2 permits it, state the local compound claim over named base facts and an admitted substrate. Preserve the applicable A.6.RCD result: missing-governor for an absent needed governing rule; missing-information for an unavailable fact needed by an existing test; factually unsupported when sufficient facts fail its positive test; that rule’s inapplicable result when applicability fails; or missing-substrate when the proposed derivation lacks admitted constructor semantics.

Production is a separate question. For a production claim, test production-work participation, first existence of an entity, and production completion separately. Apply A.15.PROD to the exact work, work part, subject-identity facts, completion criterion, and direct effect facts. A.3.4 contributes only the independently identified transformations.

Filled positive branch — result: C.2.1 assertion BuildWorkPopulatedStore-12 states the local connection between ReleaseBinary12_BuildWork_2026-07-21T0900_0912 : U.Work and ArtifactStorePopulationTransformation_12 : U.Transformation. The BuildOps predicate BuildWorkPopulatedStore@BuildOps-v12(work, transformation) holds only when the storeWrite application performed as part of that work changes the same ArtifactStorePartition_12 across the same boundary. BuildApplication_12 supplies the performed application and its builtBinary -> ReleaseBinary_12 binding; the partition’s before/after artifact-presence facts ground the transformation. This is an A.6.RCD disposition-2 local compound claim, not a universal FPF work-to-change kind or occurrence.

Pump 14 — current result and earlier no-governor stage: A.3.4 identifies T-P14-PRESSURE-RISE : U.Transformation as the bounded change of continuing HydraulicLoop_P14; the loop’s discharge-pressure characteristic is belowBand at the opening boundary and inBand at the closing boundary. The current case record contains relation-declaration episteme P14-REL-2026, owned by Pump14OperationsRelations, which declares AdjustmentWorkCausesPressureRise for exact participants W-P14-ADJUST-1010-1020 : U.Work and T-P14-PRESSURE-RISE; a separately stated case fact satisfies its actual-causation predicate. Therefore write: W-P14-ADJUST-1010-1020 caused T-P14-PRESSURE-RISE. In the explicitly earlier case record, P14-REL-2026 is absent; at that epistemic stage, keep the same Work and transformation, return missing-governor: work-to-change claim for <W-P14-ADJUST-1010-1020, T-P14-PRESSURE-RISE>, and route the missing declaration to Pump14OperationsRelations instead of asserting causation.