E.22 - Improvement-Oriented Quality Evaluation Question Framing

Status: Stable.

E.22:1 - Problem frame

Use E.22 when a request such as “review this” leaves it unclear what the recipient needs to learn about an object version. A floor check, a search for further improvement and a check of applied findings can require different answers about the same object.

First useful move: state what the recipient will use the answer for, identify the object version and choose the judgement that is still missing. Then name the criterion, the grounds the evaluator must examine and the answer to return. Section 4.0 develops this short construction; section 5 gives a filled request.

When those bindings are already settled and one direct evaluation is enough, run that evaluation. Rewriting its question as a separate frame adds no answer. Use E.23 when repeated improvement across passes is needed.

What goes wrong if missed: a reviewer can answer a different question, count closed findings without judging the changed object, or propose improvements that damage a quality the recipient needs.

What this buys in practice: requester and evaluator agree on the question before doing the evaluation. A small floor question can stay small; a request for alternatives can name the additional trade-offs and proposals it needs.

The result of framing is the question about the selected object version. The evaluator must still obtain the quality result, and the recipient must still make any decision that uses it.

E.22:2 - Problem

Quality evaluations fail when the evaluator has to infer the question. The same object can be checked for floor adequacy, improved toward exceptional expression, compared across trade-offs, mined for open questions, or evaluated after finding absorption. Those purposes produce different findings.

An unframed question hides the object under improvement, the evaluation that supplies values, and the allowed shape of returned work.

E.22:3 - Forces

E.22:4 - Solution

E.22 gives one compact declaration for improvement-oriented quality evaluation questions. It keeps the question from replacing the evaluation and keeps the evaluation result from becoming a decision or work product beyond its authority.

E.22:4.0 - Form a usable first request

Start from the result the recipient needs. A document can be required to explain an operation; the operation can be required to obtain a result; that result can support another decision. Select the object and judgement needed now. A candidate’s narrower description cannot establish that the larger receiving need has been satisfied.

1. Name the use and object version. Say who needs the answer, what work or decision it will inform, and which version is being evaluated. Include the conditions that make a difference to that use. If the receiving need is unclear, recover it with the recipient or the applicable problem-formulation method.
2. Choose the question and criterion. Say whether the recipient needs floor adequacy, further improvement, a comparison of trade-offs or the effect of applied findings. Use the characteristic space and predicate or comparator supplied by an adequate evaluation. State the floor or improvement aim and the qualities a proposed repair must preserve.
3. Connect the criterion to attainable grounds. Identify the content, observations or reasoning needed to answer it. Following a source into an instruction can establish a coherent construction; trying the instruction on material can expose a missing action; an observed application can support a performance claim under its conditions. State which answer is required, what the intended reader or performer can supply, and what the candidate must supply. If indispensable grounds are absent, ask for the exact unresolved condition rather than an unsupported pass.
4. Specify the useful return. Name the evaluation’s result form and the conclusion it can support. A floor answer identifies sufficiency or the first needed repair; an improvement answer also describes the proposed change, expected gain, protected trade-offs and closure test. State evaluator conditions only when they change the question or admissibility of the answer.

When several contributions are needed, retain what their available evaluations establish and ask about the necessary connection still unanswered. A good explanation, a supported source claim and a correct constituent operation can all remain valid while their combined use is unestablished. Evaluate that connection at its own object and use; unlike scores do not form a quality score for the whole.

Write the request in ordinary language with these bindings recoverable, as in section 5. The local names and schemas below specify their exact meanings when the question is represented as a QualityEvaluationQuestionFrame and QualityEvaluationUseDeclaration. Reuse the selected evaluation’s adequate descriptions and defaults. Add an intended evaluator’s identity or a dated-Work account only when the receiving question requires it.

Stop framing when the question and expected answer are sufficiently determined for the intended evaluation. If an existing request already supplies them, perform the direct evaluation and inspect whether its grounds support the consuming conclusion. A separate frame is useful when it resolves missing or disputed bindings; it does not improve an already adequate answer merely by restating them.

E.22:4.1 - Local names and kind settlement

E.22 frames the question. It does not evaluate the object. evaluationPatternLocator identifies the FPF pattern description containing the evaluation predicate or constraint; an optional semanticEvaluationMethodRef names the separately identified U.Method used for that evaluation. A characteristic-space specification, Q-Bundle description, rubric description, review-profile description, evidence-basis description, and result-form description constrain or describe that evaluation. None of those specifications performs the evaluation or substitutes for the subject assertion or semantic Method. For example, E.21, E.9.DA, or E.2.DA may supply the predicate for evaluating one FPF object, while A.19.ECS and C.25 supply supporting quality-model descriptions. E.19 instead defines an admission or refresh review-gate and findings profile. Use E.19 as evaluationPatternLocator only when its review result is itself the object under evaluation; otherwise its later gate check remains distinct from the quality evaluation.

A below-floor value, finding, improvement aim, or need for evaluation is not by itself an actual Problem. If the consuming use relies on an actual Problem, cite one current C.22.PFR ProblematicForRelation occurrence with its direct participants and temporal identity; the frame, evaluation, result, and evidence may support a claim about it but neither create nor split it.

The framing episteme, evaluation method, descriptions used by that method, any question-changing evaluator condition, dated evaluation Work, actual operation application, evidence use, and result occupy different positions. QualityEvaluationUseDeclaration keeps the applicable evaluation bindings together without turning a plan, declaration, or named candidate into a current performer or occurrence.

The remaining local support names ending in @Context are compatibility and retrieval names only. The suffix supplies no context entity, scope, participant, relation, or identity component; every episteme follows C.2.1 identity, every set is identified by its stated extensional rule, and every neighboring Work, decision, evidence, viewpoint, grounding, or result relation remains under its direct governor.

QualityEvaluationUseDeclaration <: U.Episteme:
  entityOfConcernRef: U.EntityRef, referencing the exact object version under evaluation
  entityOfConcernKindRef: U.KindRef, referencing the exact kind of that object version
  claimGraph: U.ClaimGraph by value
  referenceScheme: U.ReferenceScheme by value
  editionId
  evaluatorConditionRef?: U.EpistemeRef, referencing an eligibility, independence, capability, or planned condition only when it changes the evaluation question or admissibility of the result
  intendedEvaluatorSystemRef?: U.EntityRef, referencing one admitted U.System only when that exact identity is itself part of the declared question; it asserts neither assignment nor performance
  evaluationPatternLocator: U.EntityRef, locating the exact FPF pattern description that contains the defining or constraining ClaimGraph
  semanticEvaluationMethodRef?: U.MethodRef, referencing the separately identified U.Method used for the evaluation
  selectedEvaluationCharacteristicSpaceRef: U.EntityRef, referencing one exact U.CharacteristicSpace
  selectedEvaluationPredicate?: CharacteristicSpacePredicate by value
  selectedComparatorSpecRef?: ComparatorSpecRef
  evaluationClaimScopeRef: U.EntityRef, referencing one exact U.ClaimScope
  evaluationQualificationWindowDescriptionRef: U.EpistemeRef, referencing one EvaluationQualificationWindow description
  evaluationCharacteristicSpaceSpecDescriptionRef?: U.EpistemeRef, referencing one A.19.ECS specification description
  evaluationQBundleDescriptionRef?: U.EpistemeRef, referencing one C.25 Q-Bundle description
  evaluationRubricDescriptionRef?: U.EpistemeRef, referencing one evaluation-rubric description
  evaluationReviewProfileDescriptionRef?: U.EpistemeRef, referencing one evaluation-review-profile description
  expectedEvaluationEvidenceBasisRef: U.EpistemeRef, referencing one ExpectedEvaluationEvidenceBasis@Context
  expectedEvaluationResultFormDescriptionRef: U.EpistemeRef, referencing one ExpectedQualityEvaluationResultFormDescription

ExpectedEvaluationEvidenceBasis@Context <: U.Episteme:
  entityOfConcernRef: U.EntityRef, referencing the exact object version whose evaluation needs the expected evidence
  entityOfConcernKindRef: U.KindRef, referencing the exact kind of that object version
  claimGraph: U.ClaimGraph by value
  referenceScheme: U.ReferenceScheme by value
  editionId
  evaluationPatternLocator: U.EntityRef, locating the same exact FPF evaluation pattern description
  selectedEvaluationCharacteristicSpaceRef: U.EntityRef, referencing the same exact U.CharacteristicSpace
  selectedEvaluationPredicate?: CharacteristicSpacePredicate by value
  selectedComparatorSpecRef?: ComparatorSpecRef
  evaluationClaimScopeRef: U.EntityRef, referencing the same exact U.ClaimScope
  expectedEvidencePositionDescriptionRefs[1..*]: U.EpistemeRef, each referencing one evidence-position description
  expectedEvidenceRelationKindRefs[1..*]: U.KindRef, each referencing one expected evidence-relation kind
  missingEvidenceDispositionRuleRef: U.EpistemeRef, referencing one exact episteme that states the missing-evidence disposition rule under its subject pattern
  qualificationWindowDescriptionRef: U.EpistemeRef, referencing one EvaluationQualificationWindow description

Every field above with a *Ref suffix stores the stated A.6.5 RefKind; resolving it yields the referent kind named after referencing. The use declaration and expected evidence basis carry the same exact object version, governing evaluation pattern, selected characteristic space, criterion binding, ClaimScope, and qualification window. The expected basis does not point back to the declaration: it can be constituted from those exact values, expected evidence positions and relation kinds, and missingness rule; the declaration is then constituted with a reference to that completed basis. This preserves the acyclic construction.

At least one of selectedEvaluationPredicate and selectedComparatorSpecRef is present; both may be present. A label such as review, quality, or current context supplies neither. A.19 defines the predicate by value. Use A.19.CPM or the exact direct consumer rule for comparator admission; identify any actual comparison application separately. Selecting the predicate or comparator does not by itself establish the evaluation scope, evidence, time, Work, or result.

evaluatorConditionRef states only a condition that changes the evaluation question or admissibility of its result. intendedEvaluatorSystemRef is present only when the declared question depends on that exact intended System; neither field establishes assignment or performance. The actual evaluator System, every obtaining assignment, and dated evaluation Work belong to the separately identified evaluation application or result account. Keep any local evaluator system-role classification separate and route unresolved role wording through E.10.ROLE. evaluationPatternLocator locates the pattern that defines or constrains the evaluation; it is not the Method, performer, Work, or result. Claim Method or MethodDescription identity only after A.3.1 and A.3.2 admit it. Characteristic-space, Q-Bundle, rubric, profile, evidence-basis, and result-form references identify separate descriptions.

None of these declaration fields is dated evaluation Work or an evaluation result. A pre-evaluation frame contains no actual-Work identifiers. An ordinary result that asserts no actual Work needs none. If a compact projection does assert dated evaluation Work, recover every exact actual performer through A.13 and follow A.15.1 for independent Work admission; performer, Method, time, containing System, Work identity, and the result relation remain recoverable. Add assignment and F.6 refs only when the projection or receiving use expressly represents precise assignment-bound attribution; missing or failed F.6 leaves the Work intact. Keep any durable result episteme, evidence use, provenance, currentness, viewpoint, grounding, and Work-to-result or decision-use relation under their own patterns. A frame, declaration, description, assignment, dashboard, or carrier establishes none of them.

Two carriers may publish the same edition of either episteme. A QualityEvaluationUseDeclaration changes edition when its object version, claim graph, reference scheme, question-changing evaluator condition or intended-evaluator identity, evaluation pattern, semantic Method, selected characteristic space, predicate and comparator, ClaimScope, qualification window, quality-model descriptions, expected evidence-basis edition, or result-form description changes. Replacing one qualified actual evaluator with another does not change the declaration unless the declared condition or claim changes. An ExpectedEvaluationEvidenceBasis@Context changes edition when its object version, claim graph, reference scheme, evaluation pattern, selected space, predicate and comparator, ClaimScope, expected evidence positions or relation kinds, missingness rule, or qualification window changes. Carrier, context label, viewpoint, grounding record, or support serialization alone changes neither episteme. TradeoffProtectionSet@Context and CandidateImprovementProposalPortfolio@Context are set values, not records; an episteme may describe or publish either set without becoming the set.

E.22:4.2 - Quality evaluation purposes

Purposes can be combined, but the result keeps them distinguishable. A floor result does not answer exceptional improvement. Absorption count does not establish a changed evaluation result. A proposal is not a selected work item.

E.22:4.3 - Question frame

Use the construction in section 4.0 to settle the requested judgement before expressing these bindings. The schema preserves that question for its declared use.

An improvement aim is not a command to make every coordinate exceptional. A 5 is assigned only by the named evaluation after the changed object earns it. The frame may ask for substantive non-dominated proposals that could move named coordinates toward exceptional expression, while admitting no proposal or stay at current value when every plausible change would add apparatus, proof prose, boundary catalogues, or process evidence while damaging protected qualities. That no-proposal result needs checked review locations and evidence-basis references; it is not a cheap refusal to improve.

QualityEvaluationQuestionFrame <: U.Episteme:
  entityOfConcernRef: U.EntityRef, referencing the exact object version under evaluation
  entityOfConcernKindRef: U.KindRef, referencing the exact kind of that object version
  claimGraph: U.ClaimGraph by value
  referenceScheme: U.ReferenceScheme by value
  editionId
  qualityEvaluationUseDeclarationRef: U.EpistemeRef, referencing one QualityEvaluationUseDeclaration about the same object version
  selectedEvaluationCharacteristicSpaceRef: U.EntityRef, referencing the same exact U.CharacteristicSpace
  selectedEvaluationPredicate?: CharacteristicSpacePredicate by value
  selectedComparatorSpecRef?: ComparatorSpecRef
  evaluationClaimScopeRef: U.EntityRef, referencing the same exact U.ClaimScope
  resultConsumingUseRef: U.EntityRef, referencing one exact directly governed intended-work, dated-work, or decision object
  resultConsumingUseKindRef: U.KindRef, referencing its exact kind
  resultConsumingUseDescriptionRef: U.EpistemeRef, describing how that work or decision will use the evaluation result
  evaluationPurposeSelection: QualityEvaluationPurposeSelectionValue
  declaredQualityFloorDescriptionRef?: U.EpistemeRef, referencing one declared-quality-floor description
  desiredImprovementAimDescriptionRef?: U.EpistemeRef, referencing one desired-improvement-aim description
  tradeoffProtectionSet: TradeoffProtectionSet@Context by value
  evaluationQualificationWindowDescriptionRef: U.EpistemeRef, referencing one EvaluationQualificationWindow description
  nonUseBoundaryDescriptionRef?: U.EpistemeRef, referencing a non-use-boundary description only when the grounded condition in CC-E22-6 holds

The frame’s exact object version, characteristic space, predicate/comparator binding, ClaimScope, and qualification window equal those of its use declaration and expected evidence basis. These bindings make the question replayable; they do not reidentify the space, predicate, comparator, scope, method, or consuming object. A changed binding creates a changed frame edition and requires a newly evaluated result.

resultConsumingUseRef is not a generic use placeholder. Before occurrence it may resolve to one A.15.2 U.WorkPlan that names the particular intended Work, or to the exact decision question or decision-governing object under its direct pattern. It may resolve to U.Work only when that dated Work already obtains under A.15.1. The frame neither creates the consuming Work or decision nor authorizes it.

The shortest floor frame names the object version, one QualityEvaluationUseDeclaration, the exact selected characteristic space, applicable predicate and/or comparator, ClaimScope, result-consuming work or decision, purpose floorEvaluation, and the declared floor. The declaration may cite defaults supplied by the governing evaluation pattern for its quality-model descriptions, evidence basis, result form, and qualification window, but defaults do not replace the exact selected space, criterion, scope, or consumer. If the question depends on another edition, source state, comparison set, time window, or declared use, state that window explicitly. For one FPF pattern version under E.21, compactness never permits omitted coordinates, missing ShortRationale, absent PrecisionRestorationProfile, scope narrowing, or a blocker-only substitute result.

Connect the question, grounds and supported conclusion. State what the evaluation must establish about the object for the declared consuming use. In the expected evidence basis, identify the judgement that connects the selected criterion to the relevant content: for example, whether a Method’s conditions permit the proposed action, whether a computation yields the stated result, or whether a source supports the claim made from it. A direct presence or identity check is sufficient when presence or identity is the property being asked about.

When receiving the result, read its rationale and observations for that connection. Determine whether they support the requested conclusion under the declared criterion, scope and qualification. Retain supported findings and identify the exact missing judgement or inference before claiming more. Obtain that answer through the applicable evaluation, reusing current supported parts and keeping the answer in its existing result. Apply the same connection to an already-scoped direct evaluation; no new QualityEvaluationQuestionFrame is needed.

These instructions use the frame’s existing claimGraph, the declaration’s expectedEvaluationEvidenceBasisRef and the declared consuming use. The expected evidence basis describes what must be answered; the obtained grounds belong in the evaluation result.

The frame does not authorize post-hoc scope replacement. If the requested floor is landing-input, corpus-facing, Stable, release, external-review, or another stated use, the evaluator measures that use. If a different use becomes interesting, open a new QualityEvaluationQuestionFrame; do not report the current request as passed under an easier scope.

The frame and declaration state the evaluation’s intended use. An intended evaluator or planned condition makes neither a current assignment nor Work obtain. When dated evaluation Work is asserted, recover the exact evaluator through A.13 and let A.15.1 independently admit the Work; keep evidence use, typed result binding or direct result relation, and optional result episteme separate. Add F.6 only when the evaluation account expressly consumes precise assignment-bound attribution. An expected result-form description is not the result, and the consuming work or decision does not become current merely because the frame names it.

E.22:4.4 - Finding and proposal rows

An actionable finding first identifies where an issue was observed, which exact entity would change, the affected evaluation characteristic or coordinate, the current evaluation result for that characteristic or coordinate when known, the proposed correction, and the closure test. A proposal adds a typed expected evaluation effect, protected trade-offs, and any outside claim together with the subject-pattern locator needed to check that claim independently.

CandidateImprovementProposalRow@Context <: U.Episteme:
  entityOfConcernRef: U.EntityRef, referencing the exact object version under improvement
  entityOfConcernKindRef: U.KindRef, referencing the exact kind of that object version
  claimGraph: U.ClaimGraph by value
  referenceScheme: U.ReferenceScheme by value
  editionId
  qualityEvaluationQuestionFrameRef: U.EpistemeRef, referencing one QualityEvaluationQuestionFrame about the same object version
  evaluationClaimScopeRef: U.EntityRef, referencing that frame's exact U.ClaimScope
  reviewLocationDescriptionRef: U.EpistemeRef, referencing one description of the observed location in the reviewed object
  correctionTargetRef: U.EntityRef, referencing the exact entity proposed to change
  correctionTargetKindRef: U.KindRef, referencing the exact kind of the correction target
  affectedEvaluationCharacteristicOrCoordinateRef: U.EntityRef, referencing one governed characteristic or evaluation coordinate
  affectedEvaluationCharacteristicOrCoordinateKindRef: U.KindRef, referencing its exact kind
  currentAffectedEvaluationResultRef?: U.EntityRef, referencing the current result value for that characteristic or coordinate
  currentAffectedEvaluationResultKindRef?: U.KindRef, referencing the exact kind of that result value
  expectedSubstantiveEvaluationEffect: ProposalEvaluationEffectValue
  proposedCorrectionDescriptionRef: U.EpistemeRef, referencing one correction description
  kindRestorationCheckDisposition: ProposalKindRestorationCheckDispositionValue
  kindRestorationCheckRef?: U.EpistemeRef, referencing one KindRestorationCheck result
  expectedTradeoffRefs[]: U.EpistemeRef, each referencing one expected-trade-off description
  outsideClaimReferences[]?: CandidateImprovementOutsideClaimReference@Context by value
  closureTestRef: U.EpistemeRef, referencing one closure-test description

CandidateImprovementOutsideClaimReference@Context in CandidateImprovementProposalRow@Context.claimGraph:
  outsideClaimOrBoundaryDescriptionRef: U.EpistemeRef, referencing one description of the outside claim or boundary
  outsideValueRef?: U.EntityRef, referencing the exact outside governed value
  outsideValueKindRef?: U.KindRef, referencing the exact kind of that outside value
  outsideRelationSignatureRef?: U.EntityRef, referencing the exact U.Signature of the outside relation
  subjectPatternLocator: U.EntityRef, locating the exact FPF subject-pattern description; the evaluation claim separately cites the defining ClaimGraph
  reconsiderationConditionDescriptionRef: U.EpistemeRef, referencing one description of the condition that activates renewed use of that subject pattern

ImprovementFollowUpHypothesis@Context <: U.Episteme:
  entityOfConcernRef: U.EntityRef, referencing the exact object version expected to change
  entityOfConcernKindRef: U.KindRef, referencing the exact kind of that object version
  claimGraph: U.ClaimGraph by value
  referenceScheme: U.ReferenceScheme by value
  editionId
  qualityEvaluationQuestionFrameRef: U.EpistemeRef, referencing one QualityEvaluationQuestionFrame about the same object version
  evaluationClaimScopeRef: U.EntityRef, referencing that frame's exact U.ClaimScope
  qualityReviewFindingDescriptionRef: U.EpistemeRef, referencing one episteme that describes the exact QualityReviewFindingRow
  proposedNextOperationDescriptionRef?: U.EpistemeRef, referencing one operation description
  proposedNextMethodRef?: U.MethodRef, referencing one U.Method
  expectedEvaluationEffectDescriptionRef: U.EpistemeRef, referencing one expected-evaluation-effect description
  testConditionDescriptionRef: U.EpistemeRef, referencing one test-condition description

Exactly one of proposedNextOperationDescriptionRef and proposedNextMethodRef is present. The question frame, proposal row, and follow-up hypothesis preserve the same exact object-version EntityOfConcern and ClaimScope unless a proposal explicitly opens a new frame for a different version or scope. QualityEvaluationQuestionFrame changes edition when the object version, use declaration, selected space, predicate/comparator binding, ClaimScope, consuming work or decision, purpose, floor or aim, trade-off set, qualification window, non-use boundary, claim graph, or reference scheme changes. A proposal row changes edition when its frame, ClaimScope, correction target, affected evaluation coordinate, current result reference, proposed correction, expected effect, trade-offs, outside-claim nodes, closure test, claim graph, or reference scheme changes. A follow-up hypothesis changes edition when its frame, ClaimScope, finding description, proposed operation or method, expected effect, test condition, claim graph, or reference scheme changes. A context label, carrier, viewpoint, grounding record, or serialization change alone changes none of these epistemes.

ProposalEvaluationEffectValue is the closed local value set repairFloor | raiseTowardExceptional | preventProtectedQualityLoss | classifyOutsideEvaluation | preserveCurrentValue. It identifies the coarse substantive evaluation effect expected from this proposal. It does not duplicate the coordinate-qualified prediction later carried by E.23 ExpectedEvaluationResultChange@Context and does not assert an actual changed result.

ProposalKindRestorationCheckDispositionValue is triggered | notTriggered | ordinaryProse | alreadySatisfied | blocker. The triggered and blocker states include kindRestorationCheckRef; the other values leave it absent. Current affected-evaluation result ref and kind are both present or both absent; when present, the exact result resolves through the direct evaluation pattern’s typed result relation or A.6.1 application binding, and any durable result episteme remains separately governed. The proposal row neither produces nor reidentifies that result. The exact kind recovers whether the named evaluation returned a scale value, status, or another admitted result for that characteristic or coordinate. Outside value ref and kind are paired, and outsideRelationSignatureRef is present when the outside value is a relation. CandidateImprovementOutsideClaimReference@Context is a bounded local ClaimGraph node form, not a U-kind, episteme, relation, or relation-reference episteme. It is constructed inside one proposal row without a back-reference to that row; its node identity is determined by the containing proposal edition and ClaimGraph position.

reviewLocationDescriptionRef describes where the issue was observed in the reviewed object. correctionTargetRef identifies the exact entity that would change. They are not interchangeable positions. The row is a faithful typed proposal form of QualityReviewFindingRow and one possible member of a CandidateImprovementProposalPortfolio@Context set. It remains a proposal episteme, not a selected repair, plan, work occurrence, actual Transformation, result binding, or proof of improvement.

For wording, naming, and precision-restoration proposals, proposedCorrectionDescriptionRef states the correction and its intended content effect. Apply F.19 for the ordinary repair and local revalidation. When the changed FPF-governed expression can alter meaning, KindRestorationCheck states the live object, kind, relation, slot or use position, claim kind, admissible use, and scope before and after the change. If the proposed repair cannot preserve those values and no accepted decision justifies changing them, the row remains blocking.

E.22:4.5 - Absorption impact values

The absorption result states the changed evaluation result under the object-under-improvement evaluation, not a count of accepted rows.

E.22:4.6 - OEE and NQD proposal portfolios

When the object is a candidate, archive or front member, selected set, parity report, refresh report, or declared transformation result, use E.22 to frame the quality question and return proposal rows. Use C.17 for candidate characteristics, C.18 for archive and front relations, C.19 for pool policy, G.5 for selected-set result declaration, G.9 for parity, and G.11 for currentness and refresh. When audience availability is current, use E.17 for a source-backed publication face and return to source and E.24.PUB for the publication occurrence, form, carrier, audience, bounded use, and availability.

E.22:5 - Worked slices

Floor evaluation: from “review the studio method” to a usable request. A studio practitioner needs to decide whether to use C.39 to develop the recording-preparation method in C.39:5.3. “Review the studio method” leaves three possible objects: the pattern’s explanation, the conditional preparation it describes, and an actually prepared recording. The present need is the first: whether the complete pattern provides usable development guidance. Let M1 name the immutable complete C.39 edition supplied with this illustrative request.

Evaluate the attached C.39 edition M1 for my decision whether to use its guidance to develop the studio preparation in C.39:5.3. The intended user is a practitioner familiar with FPF and studio editing who can obtain the recording engineer’s interval qualification. The pattern must explain how to construct and connect the needed operations, identify missing prerequisites and reconsider affected uses after a change.

Use the E.21 nineteen-coordinate characteristic space and its floor predicate: every required coordinate at least 4 for this declared use. Evaluate the complete pattern. Examine its instructions, conditions, worked reasoning and necessary direct suppliers; use the studio case to trace what the reader can actually obtain. Preserve the distinction between the engineer’s premises and the pattern’s contribution. A worked conditional calculation supports a claim about the explained construction; it does not establish performed editing, practitioner learning or a better movement judgement.

Return the complete E.21 result: coordinate values with adjacent-value rationales, the precision-restoration profile, evidence basis and supported status. For a failed coordinate, identify the smallest sufficient repair and how to check it. Protect the useful source contribution and independently valid viewing use. This request concerns M1, the stated reader and studio use with the case’s supplied premises; it does not ask for a general release decision or exceptional-improvement proposals.

Once the requester and evaluator agree on this question, the evaluation can begin. Its purpose is floorEvaluation; the complete E.21 result remains to be obtained.

Suppose the evaluator observes that M1 explains the justified interval [40,45] ms, qualified editing and the 42.5 ms correction with a 2.5 ms bound. That observation supports the specific guidance claim about a conditional preparation meeting 3 ms analysis and 8 ms viewing requirements. It leaves every other E.21 coordinate to its own judgement. If the interval qualification is unavailable in the receiving studio, the example’s answer is to obtain that missing basis; it is not permission to edit on three marker readings alone.

Tightening the analysis requirement to 2 ms changes the preparation’s applicability: no constant correction can meet it for the given 5 ms offset span. The pattern’s instruction to return that dependent use for development remains useful, and the unchanged 8 ms viewing use remains qualified. A request to assess an actually edited recording would instead need that recording version and evidence about it. Where the receiving question is already the limited calculation under the supplied interval, evaluate that calculation directly; a full E.21 pattern evaluation and a newly written frame add no needed answer.

A method recovered from a source. A recipient needs a usable way to examine a proposal and decide how to continue. A draft faithfully summarizes a source’s discussion of criticism and correctly names proposal, evidence and action, but never explains how the critique changes the next choice. A text-quality result can support the summary’s fidelity; it cannot establish the missing obtaining explanation. The frame asks whether the candidate gives the intended reader that connection under the stated preparation and available grounds. C.39:5.4 develops this use.

A difficult adequate answer can instead return a proposal worth testing, with the exact condition that prevents immediate enactment and a justified attainable next inquiry. Whether that is sufficient depends on the recipient’s requested result: it can answer which inquiry to undertake, while leaving a request for completed enactment open. The evaluation must not reject every conditional answer as defective or silently lower the receiving requirement.

Deleting the source’s whole proposal because one inference lacks support is a potentially harmful repair: it can remove the useful propose–criticize–revise construction. Ask the evaluation to inspect both the repaired connection and the contribution it must preserve. When the ground for one later application changes, retain the source-fidelity judgement and any unaffected use, and reopen the dependent application claim. If a proposed change to the evaluation itself was developed on these cases, use A.19.ECS:4.5 to compare it with adequate execution of the incumbent evaluation and examine an independently grounded new case before claiming broader improvement.

Exceptional improvement. A pattern already passes the floor. The frame asks for substantive non-dominated improvements for named coordinates while protecting usability and related-pattern fit. The result returns proposal rows for content improvements such as missing worked cases, source-currentness carry-through, mature-comparator discharge, deletion of displaced apparatus, or relation cleanup, plus checked no-candidate dispositions for coordinates where no non-dominated content move remains. It does not ask the evaluator to make every coordinate 5.

Absorption. External review returns many suggestions. The frame asks for absorptionEvaluation. The result says which changes improved coordinates, which were already satisfied, which introduced trade-offs, and which belong outside the evaluation.

Proposal portfolio. A candidate improvement campaign needs alternatives before editing. The frame asks for candidateImprovementProposalEvaluation. The result returns bounded proposal rows; selection or generation stays with the pattern that defines or constrains that claim and is not decided by the evaluation frame.

Physical-system proposal. A vibration evaluation of PumpAssembly@Prototype-3 selects the vibration CharacteristicSpace, RMS-vibration predicate and any comparator, one evaluation ClaimScope over the declared operating-point slices, and the design decision that will consume the result. Here the account includes dated test-bench evaluation Work, so the account first recovers the exact evaluator through A.13 and A.15.1 independently identifies the Work, Method, time, and containing System. If this test-bench account also needs the exact assignment under which the evaluator acted, add F.6 through the same obtaining A.13 assignment; missing or failed F.6 leaves the Work and result route intact. An exact application of the declared vibration-evaluation operation returns the finding of excessive RMS vibration at one operating point under its result declaration. The result binding connects that application to the finding. The frame, subject-pattern reference, assignment, expected evidence basis, and result-form description remain separate. The proposal’s reviewLocationDescriptionRef points to that evaluation row. Its correctionTargetRef points to ImpellerBladeGeometryDescription@v3, the design episteme that would change; the measurement row is not the correction target. The affected coordinate is RMS vibration. The coarse proposal effect is raiseTowardExceptional, kindRestorationCheckDisposition=notTriggered, and the trade-off set includes efficiency and manufacturability. If the proposal is selected for a repeated loop, E.23 adds a scale-qualified ExpectedEvaluationResultChange@Context. Manufacturing a new impeller remains dated Work under A.15.1 rather than an E.22 result.

E.22:6 - Bias annotation

This pattern biases FPF toward asking the quality question by value. The bias is useful because unframed review requests often produce plausible but wrong answers.

The bias is bounded. E.22 does not supply quality values, run repeated improvement, publish selected sets, decide work, or certify project claims.

E.22:7 - Conformance checklist

E.22:8 - Common anti-patterns and repairs

E.22:9 - Consequences

E.22:10 - Rationale

There is no neutral generic request when a quality result is wanted. The useful artifact is the framed question: object version, selected characteristic space, predicate and any comparator, one evaluation ClaimScope, consuming work or decision, evaluation pattern, any separately identified semantic Method, purpose, expected evidence basis, expected result form, and boundary. When needed, it also states a question-changing evaluator condition or intended-evaluator identity. The frame makes those bindings inspectable without becoming the pattern, Method, assignment, descriptions, dated evaluation Work, evidence use, result, decision, or project authority.

E.22:11 - SoTA-Echoing

E.22:11.1 - Choosing the lightest sufficient question construction

Practice question. How should a requester obtain an evaluation question that will support the recipient’s actual next use, without adding another description when direct evaluation already suffices? The selected line is conditional: retain an adequate direct question; otherwise recover its missing purpose, object, criterion, grounds or use. Express exact E.22 bindings when they are needed to preserve that question across evaluators and consuming uses.

Two serious alternatives already provide purpose-first construction. Basili et al., Linking Software Development and Business Strategy Through Measurement (2010), especially “Background” and “GQM+Strategies”, links goals, derived measurement questions and interpretation to context and assumptions. It is a historical method still relevant to this comparison; its organizational alignment model is useful when that larger linkage is the question. Kidder et al., CDC Program Evaluation Framework, 2024, Steps 3–5, develops evaluation purpose, intended users and use, questions, design, credible evidence and supported conclusions. It expressly accommodates available resources and revision when needed evidence is infeasible. Their software-organization and program-evaluation settings supply no FPF characteristic values.

Comparison on the same receiving question. Keep the complete M1, reader, studio use, available premises and E.21 criteria from section 5 fixed. The following is a worked adaptation of the methods to that question, not a measurement of practitioner time or error rates.