E.18:15 - Conformance Use Checks
Choose tests from the current use, then apply the selected profile to those tests. The full CC-E18 table is available for combined or high-assurance uses; it is not an instruction to run every row for every selected structure.
- Ordinary selected-structure check: verify the selected structure, independently grounded locus values, one internal
U.Transferrelation kind, and only the current position, path, path slice, or valuation. The cooling-loop first-use slice can close here when it asserts no crossing, launch, publication, comparison or selection, cycle or refresh, or assurance branch; missing faces,LaunchGate, selector,DecisionLog, and SquareLaw are then not defects. - Crossing or launch check, when current: for a
GateCrossing, apply its crossing and gate rows, including the exact positions and changed-binding account; add launch rows only for a currentLaunchGateor work-entry claim. Do not infer a Work occurrence from either gate. - Publication or assurance check, when current: for a published face, apply the MVPK, pin, and no-new-claim rows. Inspect
DecisionLog, evidence-lane, replay, or SquareLaw material only when the current decision, crossing, publication, or named downstream reliance needs it. - Comparison, selection, cycle, or refresh check, when current: apply comparator and set-return tests to a current comparison or selection; apply budget, sentinel, edition, and slice-local replay tests to a current cycle or refresh. Hold editions fixed only for a replay claim, and test an edition bump only for a current refresh use.
- Structural reinterpretation check, when current: confirm one exact A.6.4 arrow r, an affirmative q, a separate current-case judgement of
satisfies, unchangedCtxState, andPathSliceIdlocality. Apply A.20 only when q also raises a current internal constraint. Test an independent F.9 Bridge and its bounded-use claim only when cross-semantic correspondence is also claimed; keep optionalCL, evidence, reliance, any application, and Work separate.
Relation boundary: E.18 defines selected transformation-flow structures whose loci may bind independently identified actual U.Transformation values and structure-positioned adjacent values whose definitions or constraints are identified independently. It does not define a second change ontology, a transformation-composition relation, a work sequence, a method, a mechanism, a mathematical graph expression, or a publication record. A flow arrow, adjacency, shared work, common affected referent, or placement in one selected structure establishes neither an actual transformation nor transformation composition. When a selected-structure use raises bounded-transformation, dynamics-episteme, temporal-aspect, temporal-claim adequacy, work planning, performed work, work-to-change, production, evidence, assurance, gate, decision, architecture, structural-view, mechanism, selector, comparison, refresh, publication, or wording-use claims, apply the pattern whose Solution answers that exact claim before relying on the structure.
When a selected structure locus, selected path, path slice, substructure, or flow valuation expresses or constrains one independently identified actual bounded transformation, apply A.3.4 to the U.Transformation claim and E.18 to the selected structure, containing locus, pins, locus kind, crossing, publication, comparability, and refresh discipline. Cite the exact predicate and case facts when dated work is claimed to cause or realize it, and cite the separate local A.15.PROD claim when production-work participation, entity-identity inception, or production completion is current. E.18 locus kinds do not automatically fill slots in other patterns. For a claim about the independently identified value bound at a locus, apply A.3.4 to the bounded-transformation claim, A.6.0 to the signature declaration, A.6.1 and E.20 to the mechanism claim, the applicable A.15 pattern to planning or dated Work, and A.20 or A.21 to the current internal-step-validity or gate claim.