Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:15:14 UTC

A.19.ECS:4.1 - Local names and kind settlement

Local nameUseNon-use boundary
EvaluationCharacteristicSpaceSpecLocal specification for constructing one evaluation CharacteristicSpace.Not a score sheet, review packet, work plan, gate, evidence record, or project approval.
EvaluatedObjectKindRefExact kind of object the evaluation evaluates.Not a vague artifact, file bundle, campaign, chat, or source collection.
DeclaredUseScopeUse for which the evaluated object is being judged or improved.Not all possible uses.
DiscriminatingCaseSetPositive, below-floor, and outside-declared-object-kind boundary cases used to test whether the characteristic space distinguishes the evaluated object kind and use.Not a substitute for the coordinate set.
ObjectKindFitRuleRule for admissible evaluated object, below-floor evaluated object, and outside-declared-object-kind boundary case.Not permission to omit declared coordinates after an evaluation has been invoked.
CharacteristicSlotSetThe grouped slots, each binding one characteristic to one scale.Not an arbitrary checklist and not hidden aggregation.
ScaleBindingSetThe chosen scale and value meaning for each characteristic slot.Not a metric dashboard unless a distance or measurement claim is explicitly declared by the neighbour.
PolarityAndPreferredMovementDirection of preferred movement for each coordinate, or a statement that the coordinate has no simple preferred direction.Not permission to optimize one coordinate while damaging protected trade-offs.
FloorAndExceptionalMeaningSetViable-for-use and exceptional-for-use value meanings for declared coordinates.Not a maturity ladder and not proof that future improvement is impossible.
EvaluationEvidenceBasisRuleThe checked evidence loci required for the result: object version, corpus/projection loci when corpus-facing, source-currentness loci when currentness is valued, comparator loci when parity is valued, worked-case loci when case coverage is valued, and any missing or unchecked basis that limits the conclusion.An unchecked premise leaves its dependent value unestablished; it supplies neither a low property value nor a positive evaluation. Do not infer values from reputation, review state, or absence of visible defects.
EvidenceAndMissingnessRuleWhat justifies a value and how missing, censored, unknown, object-kind-fit, or boundary-return cases are handled.Not project evidence, assurance, or gate proof by itself.
ResultRowShapeRequired result row fields for the evaluation, including coordinate, value, and a short rationale; some evaluations may add evidence-locus or payload fields.Not a free-form review paragraph and not a two-column coordinate/value table.
AdjacentValueRationaleRuleRule that each result rationale says why the lower adjacent value would understate the evidence and why the higher adjacent value would overstate it, or for the top value what would lower or reopen the claim.Not verbosity for its own sake.
CalibrationPointSetReusable 3/4/5 or equivalent adjacent-value calibration points for common evaluator disagreements.Not a second score system and not a shortcut around the declared scale.
CoordinateSpecificEvidencePayloadRuleExtra payload that a coordinate needs when a category label can fake discharge: comparator plus selected ingredient plus current locus, source plus adopted payload plus currentness window, projection locus plus retrieval cue, or another payload named by value.Not administrative burden, not the evaluated object’s method, and not live evaluated-object text unless the evaluated object itself is an evaluation result or projection carrier.
ProtectedTradeoffSetQualities or neighbour claims that must be checked when visible coordinates improve.Not a hidden veto without a declared evaluation pattern or value meaning.
PrecisionRepairKindRuleRule for checking 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 coordinate or evaluation wording is repaired; when another pattern description contains the defining or constraining content, cite its subjectPatternLocator and exact ClaimGraph.Not a lexical substitution table and not permission to change object kind or slot, relation position, use relation, or claim kind by cleaner wording.
StatusValueSetLocal admissible-use result values for the evaluation.Not release state, gate status, or evaluator praise.
E23StartConditionMinimum condition for using this evaluation inside E.23.Not the improvement loop itself.

These names are local to this pattern. They do not mint kernel U.* kinds, measurement templates, gate states, evidence kinds, or release states.