Proxy risk, missing-data policy, and protected counter-characteristics are named before a receiving synthesis, comparison, or selection pattern uses the eval result.
CC-ACE-6
Source-side “fitness function” wording is not used as the FPF object name in the record.
CC-ACE-7
A check or test is admitted only as one eval operation when an expectation or hard constraint is being inspected.
CC-ACE-8
The eval result does not select, decide, certify, or carry an architecture-adequacy claim by itself.
CC-ACE-9
A project-local program names both projectWorkOccurrenceRef and architectureEvalProgramProjectUseRelationRef; the suffix or either reference alone asserts no locality.
CC-ACE-10
The record separately identifies any reusable Method, MethodDescription, planned evaluation, dated evaluation Work, actual operation application, and typed result that the use needs; evalOperation or resultForm supplies none of those occurrences or identities.
CC-ACE-11
Every actual evaluation use binds one exact U.ClaimScope, relevant A.2.6 U.ContextSlice membership, effective reference scheme and plane, evaluation window, and input projections; evalScope, runContext, and parityFrameRef do not replace them.