fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 85542–85556

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:00:09 UTC

E.8.ECSPF:4.3 - By-value carry-through

Carry the accepted specification through the pattern in practitioner order. “By value” means that the reader can find the actual selected value and use it; a field name, an A.19.ECS citation, or an author-only attachment is not enough.

Practitioner needAccepted values that must be present
Recognize whether to enterEvaluatedObjectKindRef, DeclaredUseScope, WorkingReaderScope, QualificationWindow, and ObjectVersionUnderImprovementRef when the evaluation is tied to one object version.
Test the boundaryDiscriminatingCaseSet and ObjectKindFitRule, including admissible, below-floor, and outside-kind outcomes.
Judge the objectCharacteristicSlotSet, ScaleBindingSet, PolarityAndPreferredMovement, and FloorAndExceptionalMeaningSet, with the actual coordinate and value meanings rather than their field labels.
Justify and record a resultEvaluationEvidenceBasisRule, EvidenceAndMissingnessRule, ResultRowShape, AdjacentValueRationaleRule, CalibrationPointSet, and CoordinateSpecificEvidencePayloadRule whenever a coordinate triggers such a payload.
Protect a useful result from false improvementProtectedTradeoffSet and DominanceOrComparisonRule whenever the accepted specification declares a comparison rule.
Continue, stop, or leave this evaluationStatusValueSet, StopOrReopenCondition, NeighborPatternExitSet, E22QuestionFrameUse when selected, and E23StartCondition.

The fields may be expressed in plain language, tables, or worked cases. Keep them close to the practitioner action they qualify. Do not hide required values in conformance rows, source notes, or review evidence.