| “Review this” prompt. The evaluator infers purpose. | Add a QualityEvaluationQuestionFrame with exact object version, space, criterion, ClaimScope, consumer, purpose, and boundary. |
| Context-labelled frame. Project, domain, dashboard, cadence, or context label supplies identity or evaluation scope. | Identify the frame by its C.2.1 claim content and exact EntityOfConcern; bind the exact U.ClaimScope and other use values separately. |
| Floor pass sold as excellence. Readiness is mistaken for exceptional improvement. | State exceptionalImprovementEvaluation if wanted. |
| Frame replaces result. The question frame names a purpose but returns prose, a two-column value table, or proposal rows without the named evaluation’s result form. | Complete the missing evaluation judgements and return the named evaluation’s declared coordinates, evidence basis, rationales, payload fields, and typed result binding or direct result relation, reusing supported parts under E.22:4.3. If the result asserts dated Work, recover the evaluator through A.13 and apply A.15.1 independently; add F.6 only for an expressly represented precise assignment-bound attribution. If it asserts an A.6.1 application, name the operation bindings. Do not infer any of them from the frame. |
| Description performs evaluation. A method description, characteristic-space specification, expected evidence basis, assignment occurrence, or result-form description is treated as evaluation Work or its result. | Keep each description and assignment separate. Identify the direct evaluation result; when dated Work is asserted, recover the evaluator System through A.13, apply A.15.1 independently and add F.6 only when the receiving account expressly consumes precise assignment-bound attribution. Keep evidence use and result under their direct patterns. |
| Scope laundering. The frame asks one use, but the result answers an easier, local-only, diagnostic, or evaluator-selected use. | Obtain the missing judgements under the requested U.ClaimScope, reusing any supported parts that answer it under E.22:4.3. Preserve a result for another use at its actual scope; frame that other use separately if it is now wanted. |
| Applied-count absorption. Closure count replaces re-evaluation of the changed object. | Re-evaluate the changed object and classify impact. |
Goodharted improvement. Visible values rise while protected qualities worsen, or a 5 target makes the evaluator add apparatus instead of improving content. | Frame the expected evaluation effect as a substantive content change, add trade-off protection, reject dominated changes, apply E.13 when a visible value replaces the intended value, and admit no proposal only when checked positions show that no worthwhile content improvement remains. |
| Recommendation as decision. A follow-up hypothesis is treated as chosen work. | Open the exact decision, work, publication, parity, refresh, evidence, or assurance pattern if that claim is needed. |
| Finding as actual Problem. A low coordinate, finding, or floor miss is treated as a Problem occurrence. | Keep the evaluation result epistemic; cite C.22.PFR only when its actual-condition and criterion-applicability participants make one ProblematicFor occurrence obtain. |
| Lexical repair request. A finding says only “replace this word” or “avoid that wording.” | State the intended content effect and apply F.19. Add the before/after KindRestorationCheck when the changed expression can alter FPF-governed meaning; leave an unjustified meaning change blocking. |