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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 10:17:34 UTC · last check 2026-10-03 10:20:08 UTC

C.16.Q:4.3 - Normative starter set of sense families

A declared local vocabulary under one effective ReferenceScheme MAY add local senses, but the following starter set is normative as the initial disambiguation menu:

QualitySense tokenUse when “quality” means…Default normal formTypical substrateMust not be silently collapsed into
QS.PreconceptualFitpreconceptual fit, felt rightness, “quality before definition”, kinesthetic or embodied salienceSignalPackembodied-kinesthetic or hybridCharacteristic, utility, fitness score
QS.PhenomenalCharacterphenomenal character, qualia, or felt characteristic when the experienced quality itself is describedSignalPackembodied-kinesthetic or hybridQS.PreconceptualFit, engineering quality, utility
QS.LatentFitdistributed fit or tension in learned representations, world models, probes, prediction structuresSignalPacklatent-distributed or hybridQS.PreconceptualFit, engineering quality, explanatory merit
QS.ExplanatoryMeritepistemic merit of an explanation, conjecture, problem frame, or theoryBundlesymbolic-local or hybridengineering -ilities, use-value
QS.ArchitecturalDescriptionFitnesstask-fit and compression merit of an architecture description, architecture model, or viewpoint bundle as a description of structure for downstream reasoningBundlesymbolic-local or hybridQS.EngineeringQualityFamily, QS.ExplanatoryMerit, publication polish
QS.EngineeringQualityFamilyreliability, availability, security, maintainability, evolvability, usability, and related engineering familiesBundlesymbolic-local or hybridfunction or capability statements, preconceptual fit
QS.UseValueusefulness of a candidate under a declared goal or CG-frame; the “Q” head in NQD or QD by defaultObjectivesymbolic-local or hybridengineering quality family, explanatory merit
QS.ControlAdequacyadequacy of a policy, model, or controller in a closed action loopBundlehybridbare model “quality”, felt fit

Default-form note. QS.EngineeringQualityFamily and QS.ControlAdequacy default to Bundle. A declared local use under one effective ReferenceScheme MAY operationalize one explicit head as a Characteristic, but that is a declared operationalization, not a second default normal form.

Normative rewrite note.

  • In NQD, QD, or selector contexts, bare quality SHALL rewrite to QS.UseValue unless a different QualitySense is explicitly declared.

  • In engineering contexts, bare quality SHALL rewrite either to:

    • one explicit U.Characteristic + CSLC Scale, or
    • one explicit Bundle, preferably published as a Q-Bundle when composite.

  • In phenomenological contexts, bare quality SHALL rewrite to QS.PhenomenalCharacter when the experienced quality itself is the topic of description, and to QS.PreconceptualFit when the talk is about preconceptual fit or felt rightness before stable characterisation.

  • In representation-learning and world-model contexts, bare model quality SHALL rewrite to QS.LatentFit, QS.ControlAdequacy, or both, with the distinction made explicit.

  • In epistemic evaluation contexts, “good explanation” SHALL rewrite to QS.ExplanatoryMerit.

  • In architecture-description fitness or viewpoint contexts, bare architecture quality or architectural quality SHALL first disambiguate the bearer lane: if the bearer is the system-side bearer, use QS.EngineeringQualityFamily; if the bearer is the description or episteme, use QS.ArchitecturalDescriptionFitness.