E.11.PUA:5.1a - Evaluation specification without a ProblemCard

An architecture team already has a bounded comparison question and needs no accepted C.22.2 ProblemCard episteme. It applies A.19.ECS and states one exact EvaluationCharacteristicSpaceSpec with declared coordinates, scales, comparators, and evidence rules; A.19.ECS and C.2.1 govern that specification episteme. The optional problemCardRef remains absent.

The application-flow label is only a readable PUA position. If the team claims that exact planning or specification Work first constituted the episteme, cite its local A.15.PROD inception claim for that subject fact. A reliance-bearing PUA closure separately identifies the category-correct basis that makes the specification a result relative to the current pattern use or another named relative object. If a later comparison actually uses the specification, cite the exact direct relation, A.6.1 binding, or local relation-bearing claim defined or constrained by that comparison pattern. Without the corresponding basis, keep the specification, its PUA closure, and the later comparison separate.