A.19.ECS:4.3 - Evaluation specification minimum
A.19.ECS does not prescribe a publication or record form. It states which evaluation characteristic-space elements must be recoverable before an evaluation characteristic space is reusable for judgement or improvement. The selected publication or record form may be an FPF pattern, local engineering standard, rubric, table, review form, model card section, protocol note, or project rule, but that form is not governed here. The evaluation characteristic-space specification must make these items recoverable by value:
| Specification item | Required content |
|---|---|
Evaluation problem frame | Evaluated object kind, declared use, first useful move, existing-evaluation boundary, and what goes wrong if no evaluation exists. |
Non-use boundary | Boundaries to single-characteristic, measurement, Q-Bundle, naming, evidence, assurance, gate, work, decision, publication, and loop-method patterns. |
Local names and kind settlement | Local field names, use named by values, and non-use boundaries. |
Evaluation record shape | The local record or bundle shape used by the evaluation. |
Object-kind fit rule | Admissible evaluated object, below-floor evaluated object, and outside-declared-object-kind boundary handling before and after invocation. |
Evaluation evidence basis | Loci named by value that must be checked or named when a value depends on object version, corpus projection, source currentness, mature comparator, worked case, retrieval, or other external evidence. |
Result-row shape | Required result row fields, at minimum coordinate, value, and short rationale; any required evidence-locus or coordinate-specific payload fields are declared here. |
Coordinate set | Coordinate heads, properties of the evaluated object, evaluated-object properties and use conditions, scale/value meanings, evidence loci, and protected trade-offs. |
Calibration and payload rules | Adjacent-value calibration points and coordinate-specific payloads that prevent impressionistic 3/4/5 assignment or category-list discharge. |
Status and stop condition | Admissible-use statuses, local stop meanings, and reopen conditions. |
Worked slices | At least one passing evaluated object, one below-floor evaluated object, and one outside-declared-object-kind boundary case. |
Common anti-patterns | The false interpretations or values the evaluation must block. |
Neighbouring-pattern claim assignment | Neighbouring FPF patterns named by value and the claims being made that each pattern defines or constrains. |
This minimum is a content requirement, not a file-format requirement. For an FPF pattern publication form, E.8 still governs the authoring form. A.19.ECS only states what the evaluation must make recoverable so that E.22 can frame an improvement-oriented quality evaluation and E.23 can run a repeated improvement loop.
When construction or repair changes coordinate wording or evaluation wording, the evaluation characteristic-space specification records PrecisionRepairKindRule or an equivalent result-row requirement. The check compares the pre-repair and post-repair evaluated object kind, characteristic kind, relation or claim kind, current ontic slot, relation position, use relation, admissible use, and scope; when another pattern description contains the relevant definition or constraint, it cites that exact ClaimGraph and may add a non-semantic subject-pattern locator. A cleaner phrase that changes those items, treats a coordinate position as an object kind, or loses the value’s slot, relation position, use relation, or claim kind is a changed evaluation decision, not a wording repair.