A.19.ECS:3 - Forces · fpf.tools

Force	Tension
evaluated-object-kind discrimination vs broad reuse	The evaluation must fit the evaluated object kind, but it should reuse existing FPF characteristic and scale discipline where possible.
Small first version vs enough coordinates	A useful first evaluation can be compact, but it needs enough coordinates to block false improvement and wrong-kind comparison.
Measurement admissibility and scale lawfulness vs ordinal judgment	Some coordinates are measured through `C.16`; others are evidence-backed ordinal content values. The evaluation must say which is which.
Improvement direction vs trade-off protection	Preferred movement must be visible without turning every coordinate into an optimization command.
Contrast cases vs overfitting	Contrast cases are needed to test the scale set, but the evaluation must not become a list of examples only.
Reusable specification vs local use	A reusable evaluation must make the same evaluation characteristic-space elements recoverable across uses. A local project can use a smaller specification when the use is bounded and non-reusable.
Local stop vs open-ended improvement	A loop may stop for the declared use while the object and the scale set remain improvable under a new use, source, or comparison concern.