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 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 10:45:12 UTC

E.21:4.1 - Local names and kind settlement

Local nameKind and function
PatternQualityEvaluationCompatibility compound label for the configured evaluation package. Any use resolves to the exact characteristic space/specification, configuration, ordinary assessment or separately asserted dated Work, result episteme, witnesses/evidence-use relations, optional record, and exact declared-operation application only when the compact A.6.1 condition holds.
PatternQualityCharacteristicSpaceRefReference to the exact A.19 U.CharacteristicSpace whose slots are the required E.21 coordinates and whose bindings use the E.21 ordinal scale.
PatternQualityEvaluationSpecRefReference to this object-specific A.19.ECS evaluation-specification episteme: applicability, coordinate and scale meanings, evidence/missingness rules, calibration, result shape, local status meanings, and reopen conditions.
PatternOfConcernRefExact authored FPF pattern edition or bounded version named by value as the checked object, with its host path or monolith section and edition, commit, hash, or other pinned version basis recoverable. PatternOfConcern is relation-relative: the same pattern can also be the concern in another use, review, or evaluation flow. The evaluated pattern also has its own primary EntityOfConcern: the subject that its Problem, Solution, or guidance is about. FPF patterns are applied to situations, claims, texts, or work objects. Say that a pattern defines, constrains, tests, or supplies a repair for a claim, relation, or boundary only when its content actually does; use related pattern for a looser pattern relation and relation only for the relation itself.
ClaimScopeQuality claim boundary recovered from the governing frame: ordinary use, authoring input, landing input, release input, external-review input, high-assurance reuse input, canonization input, or another explicitly requested pattern-quality use. It is not chosen by the evaluator to make a failing request pass.
WorkingReaderScopeWorking-reader family, viewpoint, and first-use situation the pattern must serve.
IntendedUseAction that may use the result: continue drafting, admit for declared use, repair, refresh, or compare candidates.
QualificationWindowEdition, SoTA, related-pattern, release, time, or comparison window in which the evaluation is current.
EvaluationEvidenceBasisChecked evidence loci named by value for the evaluation: pattern body version, host or monolith section, README scenario, ToC row, E.11 entry-distribution locus, including a worked comparison when corpus-facing, card or retrieval cue when claimed, the best-known-line comparison and source-role loci when SoTA is valued, source-identity/currentness traces when replayability or the qualification window needs them, mature comparator set when maturity is valued, and worked case or absence of worked case when case coverage is valued. Inclusion here is neither a witness claim nor an evidence-use relation.
QualityEvaluationQuestionFrameRefE.22 frame when purpose, floor, trade-offs, absorption, or proposal expectation needs to be declared.
PatternQualityEvaluationConfigurationLocal input tuple binding the exact checked pattern, scope, use, reader, and window, characteristic space and specification, question frame when used, and evidence basis, plus the semantic evaluation Method only when its identity or actual assessment Work is asserted.
SemanticPatternQualityEvaluationMethodRefReference to the exact semantic U.Method when Method identity or actual assessment Work is asserted. Exact assessment Work enacts that Method; the E.21 specification and coordinate table supply its evaluation questions.
PatternQualityAssessmentWorkRefUsed only when the evaluation asserts exact dated A.15.1 U.Work. Then the item 5 Work account applies. Add an application ref only when the separately admitted mechanism-operation condition is also satisfied.
PatternQualityEvaluationApplicationRefReference to one exact A.6.1 application occurrence admitted under one exact operation declared by a separately admitted U.Mechanism, together with its actual declaration-local bindings. It is present only when the compact conditional rule in E.21:4 holds.
CoordinateValueRationalesOne result claim for every required coordinate: Coordinate, Value, ShortRationale.
CoordinateEvidenceRefsPer-coordinate text, case, relation, SoTA, mature comparator, projection, or review refs where the short rationale depends on evidence outside the pattern body row being discussed. Reference presence does not itself establish a coordinate value.
PrecisionRestorationProfileCompact quality summary of the F.19 whole-span reading: overallEffect, checkedLoci, and affectedCoordinates. Optional issue-bearing fields in E.21:4.3a retain the six diagnostic layers: word, head, and use precision; phrase-level apparatus; repeated or distributed material; ontic and slot-relation clarity; description, publication, and source boundary separation; and pattern-application ontology. The profile collapses their findings into one scalar effect and the affected existing coordinates. A finding names the restoration locus or concrete pattern contribution needed; a clean result names its checked absence scope once.
PatternQualityQBundleE.21-local non-arithmetic bundle-shaped ClaimGraph payload for one exact pattern edition, effective ReferenceScheme, ClaimScope, intended use, and qualification window. It contains the complete coordinate-result claims and rationales, PrecisionRestorationProfile, local PatternQualityStatus, stop or repair condition, reopen condition, and an optional grounded non-use boundary when a named competing use or plausible confusion makes that boundary material. The aggregate C.2.1 result episteme carries this payload; a general C.25 engineering Q-Bundle or another evaluation object remains separate.
DominanceSetCoordinates used to compare already evaluated candidate versions. It never changes the required coordinate set.
PatternQualityResultRefOne C.2.1 result episteme whose EntityOfConcern is the exact checked pattern edition and whose ClaimGraph carries the same-bearer PatternQualityQBundle: declared use and window, every coordinate-result claim, PrecisionRestorationProfile, local status, stop or repair, reopen, and any grounded non-use boundary. Assessment work, witnesses, records, admission, and authority remain separate objects or relations.
PatternQualityWitnessRefsExact pattern loci, cases, comparators, sources, traces, or projection loci cited by result claims; witness presence is neither a value nor evidence use.
PatternQualityEvidenceUseRefsExact A.10 evidence-use/provenance relations supporting reliance on result claims.
PatternQualityEvaluationRecordRefOptional C.2.1 record episteme packaging the current configuration, work or application, result, witness or evidence, reopen refs, and any grounded non-use boundary. Its function is reference packaging; status, admission, assurance, and authority use their direct relations.
PatternQualityStatusLocal admissible-use value asserted by the aggregate E.21 result episteme. It is not an E.19 admission or refresh decision; any F.10 status use or interpretation by a receiver is a separate relation.
StopConditionWhy improvement may stop, continue, refresh, or hold.
ReopenConditionChange in evidence, use, source, or other stated premise that requires reconsidering the result.
BoundedNonUseOptional non-use boundary, included only when an independently grounded competing use or plausible confusion changes the result’s use.

Names are local to pattern-quality evaluation unless F.18 promotes a durable name. Each has only the direct function stated above; any later receiving use requires its own relation.