C.17:1 - The practitioner route

C.17:1.1 - Qualitative first move

Name the bearer, comparison set, practical objective or must-criterion, observed or argued difference, supported consequence, evidence, and limitation. A useful statement can be as simple as:

Compared with the admitted five-year pump-design set, P-22’s inspected split-clamp arrangement is a supported difference. The cited assembly evidence supports shorter assembly, and the design must not require new tooling. The inspection does not support claims about other pump families.

This is already a valid C.17 result for an ordinary design discussion. It does not imply a numerical Novelty value or an overall assessment occurrence.

C.17:1.2 - Quantified or reusable branch

When a quantified, comparison-ready, or reusable result is needed:

1. select one A.19 CharacteristicSpace and its A.19.ECS specification;
2. fix the finite comparison corpus, inclusion rule, source editions, scope, comparison window, and evidence;
3. identify the objective, acceptance criterion, and must-constraints actually used;
4. identify the similarity or measurement Method used and any model, encoder, distance definition, invariances, calibration, and uncertainty basis it needs;
5. for each coordinate, cite an existing complete C.16 measurement result, perform and constitute the missing C.16 measurement, or state a C.2.1 non-measurement ascription under its declared rule;
6. form only the aggregate conclusion needed by the receiving comparison;
7. add an optional profile payload, representation, or record only when a named receiver needs it.

Return only the missing premise that blocks the current coordinate or conclusion. A missing measurement does not invalidate independent qualitative claims or other coordinates.

C.17:1.3 - Dated overall-assessment branch

Open this branch only when the claim says that an overall assessment actually occurred and later reliance needs that fact. Recover the evaluator System through A.13 and the admitted Method through A.3.1, then use A.15.1 to independently admit the dated Work that enacts that Method. Add the exact A.2.1 assignment occurrence and F.6 relation only when later reliance expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; missing or failed F.6 leaves the assessment Work intact. Only the evaluator System performs the Work. A separate MethodDescription may explain the reusable Method; it is not enacted. Coordinate-measurement Work remains its own C.16 Work, and the aggregate result states claims.

Do not infer an A.6.1 operation application from the Method, Work, configuration, or result. If a receiving claim separately asserts an exact operation application or binding, satisfy the current A.6.1 application account and cite that application. Otherwise retain only the C.17-local evaluator System, assignment, Method enactment, dated assessment Work, coordinate results, and aggregate result that the claim actually needs.