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

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:25:09 UTC

C.16.Q:4.9 - Lexical guardrails

In Tech and normative prose:

  • bare quality MUST NOT appear without immediate resolution to a QualitySense;

  • high-quality, low-quality, quality metric, quality score, quality requirement, model quality, architecture quality, and solution quality are red-flag tokens;

  • quality characteristic MAY appear only as:

    • a bridge label to an external standard or tradition, or
    • a family label immediately rewritten into one explicit U.Characteristic or Q-Bundle;

  • quality requirement or quality requirements MUST NOT remain bare noun phrases; rewrite them into explicit requirement-use, source-use, gate, commitment, acceptance-spec, characteristic, Q-Bundle, objective, or publication-use claims or relations using the applicable pattern and one named U.Characteristic, Q-Bundle head, or objective head; the wording itself establishes none of those objects;

  • architecture quality or architectural quality MUST NOT appear without an explicit bearer lane (EntityOfConcern being described, description or another episteme, publication face, or carrier when the carrier itself is evaluated) and, when omission changes meaning, an explicit referencePlane;

  • in QD and NQD contexts, bare quality MUST default to QS.UseValue;

  • preconceptual uses MUST NOT be presented as if they were already Characteristics;

  • latent and distributed fit MUST NOT be presented as if it were automatically explanatory merit;

  • if the occurrence is primarily action-invitation talk, the text MUST NOT assign a QualitySense; use A.6.A for wording recovery, then the pattern for the recovered claim or question, with source-tradition affordance wording kept only as a quoted cue when needed;

  • scope words (applicability, envelope, generality, validity) MUST NOT be used as hidden substitutes for U.ClaimScope, U.WorkScope, U.PublicationScope, or another exact governed scope;

  • quoted metalinguistic uses of the token quality are allowed, but SHALL be marked as token-under-discussion, not as a boundary-bearing term.