Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:20:20 UTC

C.16.Q - Quality-Term Precision Restoration

Type: Characterization precision-restoration pattern Status: Stable Normativity: Normative unless explicitly marked informative

Plain-name. Quality-term precision restoration.

Intent. Recover what a quality statement means for its subject and intended use. Distinguish the sense, interpretation basis and kind of result before using the statement for evaluation or another decision.

Use the form already defined for a known endpoint. When unresolved alternatives must remain inspectable, qualityTermAscription(...) supplies a transitional form with explicit participants and conditions. Its detailed fields do not apply to every occurrence of the word “quality.”

Philosophical, representation-learning, engineering and search uses can retain their different meanings. A recovered action question, relation, requirement or commitment follows its own subject rule.

C.16.Q:0 - Use this when

Use this pattern when wording such as quality, good, fit, high-quality, quality characteristic, quality improved, or an evaluative -ility claim hides the intended quality meaning or evaluative use.

First useful move. Identify what the quality statement concerns and what “quality” means here. For an evaluation, also recover the criterion used to judge that subject. Use the sentence and its receiving question to distinguish the plausible interpretations. If the meaning and applicable endpoint are already clear, use that endpoint directly.

Lowest sufficient use. Keep ordinary praise and source-local description ordinary when no further FPF-governed claim is made. A supported ordinary explanation can settle the ambiguity. Preserve an insufficiently articulated cue under A.16.1 or its possible continuations under B.4.1; do not invent the missing interpretation to complete a record. Use the transitional form only when the remaining ambiguity must be inspected or reused, with the required interpretation basis in §4.1.

Practical gain. The reader can recover what is described or evaluated, what any comparison establishes, and what the resulting claim supports. A shared quality word no longer substitutes for the relation between different traditions or for a separate evidence or decision claim.

Not this pattern when.

  • If the issue under repair is hidden characteristic, scale, score, metric, coordinate, threshold, or comparison construction, use C.16.P first.
  • If the claim being made is already a Q-bundle, pattern-quality coordinate, relation construction, action invitation, evidence, assurance, gate, work, decision, causal-use, release, or source-use claim, apply the pattern for that claim directly after any needed quality-word repair.
  • If the word is ordinary praise or source-local wording with no FPF-governed use, keep it ordinary, quote-only, or reduced-use rather than publishing a quality-term repair.

C.16.Q:1 - Problem frame

Quality statements, including evaluation claims such as “the model quality improved” or “the architecture is high-quality”, can concern different subjects and senses. For example:

  1. Phenomenal character or qualia when the experienced quality itself is the topic of description rather than an externally measured characteristic.
  2. Preconceptual fit or felt rightness before stable EntityOfConcern characterization.
  3. Latent and distributed fit signals in learned representations, world models, or active inference loops.
  4. Explanatory merit of a theory, problem frame, or conjecture.
  5. Architectural-description fitness and compression merit of an architecture description or architecture model under a declared viewpoint.
  6. Engineering quality families such as reliability, maintainability, security, evolvability.
  7. Usefulness and selection value in open-ended search, novelty–quality–diversity, or portfolio selection.
  8. Control adequacy of a policy, model, or controller in a closed loop.

The failure modes are recurrent:

  • Sense elision. One quality word hides several non-equivalent senses.
  • Bearer confusion. The subject of the quality statement is unclear: record, publication carrier when the carrier itself is described or evaluated, episode, model, policy, explanation, candidate, architecture, relation, or action loop.
  • Form confusion. A non-metric signal is rewritten as a metric; a bundle is treated as one scalar; an objective is mistaken for a characteristic.
  • Substrate confusion. Embodied and preconceptual, latent and distributed, and symbolic-local representations are silently collapsed.
  • Plane confusion. Quality of the EntityOfConcern being described, quality of the description, quality of the carrier, and quality of the publication face are silently collapsed across ReferencePlane values and A.7 lanes.
  • Bridge illusion. Similar wording across traditions is mistaken for sameness.
  • Illegal scalarisation. Composite engineering families or explanatory merit are compressed into one number without an admissible scoring method.
  • Viewpoint conflict. One stakeholder means architectural attributes, another means usefulness, another means preconceptual fit.

C.16.Q:2 - Problem

How can a reader retain the convenience of “quality” while recovering its intended sense, subject and conditions? The difficulty is greatest when a statement connects traditions whose evaluative criteria differ. An action-oriented use may need meaning recovery under A.6.A rather than an evaluative ascription.

C.16.Q:3 - Forces

  • Breadth vs precision. “Quality” is attractive because it is broad; that breadth can obscure which sense is intended when uses meet.
  • Preconceptuality vs auditability. Some uses refer to something real but not yet stably characterised.
  • Distributed substrate vs local publication. Some evaluative signals arise in distributed or embodied substrates but must later be published in explicit local forms.
  • Comparability vs non-reduction. Engineering and selection settings need comparability, but not every evaluative signal is an admissible metric.
  • Cross-tradition dialogue vs false unification. The framework should permit parallels without asserting identity.
  • Progressive articulation. A person can notice a mismatch before being able to name a criterion. An account of what they noticed can guide a choice of measure or objective. To claim a measured value, establish how the measure bears on the characteristic and obtain the observation.

C.16.Q:4 - Solution

Recover the intended claim first. Use a known endpoint directly; retain a transitional ascription only for unresolved interpretation that the receiving work needs to inspect.

C.16.Q:4.0 - Trigger rule

Inspect quality wording when its sense, bearer, comparison or consequence is unclear, especially in a claimed improvement, admission or cross-tradition use. Familiar phrases such as quality score, model quality and quality requirement are cues to that question. Their appearance alone does not require a new ascription or a repeated repair of an already explicit endpoint.

C.16.Q:4.0a - Operational repair sequence

  1. Read the whole assertion. Recover what the sentence claims or asks. Retain its wording when an inspectable before/after comparison is needed.
  2. Recover the subject being described or evaluated. Distinguish the EntityOfConcern being described from its description, publication face or carrier when that distinction changes the claim. Keep ordinary non-governed wording ordinary.
  3. Distinguish the plausible interpretations. Use the stated purpose and interpretation scheme, together with any relevant evaluation conditions or comparison, to resolve plausible alternatives. If an existing endpoint already conveys the intended claim, use it and stop this repair. Keep a short Candidate-Set Note only when unresolved alternatives need to remain inspectable for the receiving decision or publication; use an existing explanation when it already does that job.
  4. Follow the recovered question. For action-oriented wording, a relation, evidence, a gate or another non-quality question, apply its subject rule. Use A.6.A, A.6.P, C.16.P or another recovery pattern only while the corresponding meaning is still unclear. An adequately expressed question can finish without a QualitySense.
  5. Choose a sense when a transitional ascription is needed. Select the applicable QualitySense and retain consequential rival interpretations while they remain unresolved. Explain a rejected alternative only when that distinction helps recover the intended claim.
  6. State the supported interpretation. Use the known endpoint’s form, or the transitional form under §4.1 with its required bearer, scheme, probe/model and comparison conditions, evaluator/viewpoint, scope and normal form. Add result, evidence, grounding or cross-local references only for independently established relations used by this claim.
  7. Apply conditions for a further use. A clarified quality statement can contribute to a decision, evidence claim or other result. Establish that further use under its own rule; the word “quality” and completion of the repair do not establish it.

C.16.Q:4.1 - Transitional repair frame: quality-sense interpretation anchored by qualityTermAscription(...)

A transitional ascription makes an unresolved quality interpretation explicit under one effective ReferenceScheme and a named endpoint pattern or source relation. It records the intended characterization without asserting a result or evidence relation merely through its fields.

qualityTermAscription(...) is the canonical transitional quality-term repair form when the endpoint choice is not yet fixed. The form is not a relation kind by default and does not replace the endpoint source.

Use of qualityTermAscription(...) presupposes enough articulation explicitness to name the bearer, effective scheme, probe/model frame, A.19.CPM profile comparison frame or explicit none, ClaimScope, and at least one candidate quality-sense family. Closure degree may remain low while qualityTermAscription(...) is transitional, but content that is still only a cue pack, forwarded cue, or open explanatory probe stays in A.16.1, B.4.1, or B.5.2.0. If a published record later loses an interpretation-bearing scheme, frame, scope, or direct source relation required for its stated use, retreat via A.16.2; changed witnesses, evidence use, or grounding reopen only the neighboring result or reliance claim they bear on.

The transitional form is:

qualityTermAscription :=
{
  bearerTuple: exact bearer designator(s),
  qualitySense: QualitySense,
  effectiveReferenceScheme: EpistemeInterpretationScheme,
  probeOrModelFrameRef: exact domain-local probe or model frame,
  comparisonFrameRef: exact A.19.CPM-governed comparison frame | none,
  evaluatorRef: exact evaluator or policy ref | none,
  viewpointRef: U.ViewpointRef | none,
  referencePlane?,
  representationLanguageRef?: U.EntityRef with referent satisfying RepresentationLanguage (E.5.2.L:4.3),
  normalForm: SignalPack | Characteristic | Bundle | Objective,
  claimScope: U.ClaimScope,
  contextSliceRefs?: exact U.ContextSlice refs,
  gammaTime?,
  representationSubstrate?: embodied-kinesthetic | latent-distributed | symbolic-local | hybrid,
  qualityResultClaimRef?: exact separately constituted result-episteme ref,
  witnessRefs?: exact witness refs,
  evidenceProvenancePathRefs?: refs to exact direct relations in an A.10 path,
  empiricalGroundingRelationRef?: exact EpistemeEmpiricalGroundingRelation occurrence ref | none,
  bridgeOccurrenceRef?: exact F.9 Bridge occurrence ref | none,
  bridgeUseClaimRef?: exact F.9 bounded-use claim ref | none,
  bridgeCardRef?: exact F.9 Bridge Card ref | none,
  bridgeStanceNoteRef?: exact F.9.1 stance-episteme ref | none,
  endpointPatternLocator?: pattern ref for the endpoint,
  endpointSourceRelationRef?: exact direct source or publication relation ref,
  admissibleUse,
  nonAdmissibleUse?
}

effectiveReferenceScheme, probeOrModelFrameRef, comparisonFrameRef, and claimScope are explicit. Use the probe or model frame for the domain procedure, including any qualitative comparison it makes. Reserve comparisonFrameRef for a comparison of admitted profiles under A.19.CPM. It identifies the CG-Spec, comparator edition, comparison scope, reference plane and interval. Set it to none when the claim uses no such profile comparison.

The record designates, but does not embed, a viewpoint. A non-none viewpointRef is one U.ViewpointRef whose governed resolution yields an exact viewpoint episteme; the reference, the viewpoint episteme, and the evaluator remain different objects.

qualityResultClaimRef is not assessment work, while witness refs and an A.10 evidence-provenance path establish neither a result nor empirical grounding. Cite empiricalGroundingRelationRef only for a separately obtaining C.2.1 relation between the identified episteme and exact holon under governed observation, intervention, measurement, test, or evaluation relations.

Likewise, cite an F.9 Bridge occurrence and bounded-use claim only when each independently exists. Cite a Card only when that optional package exists. Cite a stance note only when its reference resolves a C.2.1 episteme whose EntityOfConcern is that exact use claim.

At least one of endpointPatternLocator and endpointSourceRelationRef is required. The locator identifies the pattern passage that defines or tests the endpoint. A separate assertion or ClaimGraph is required only when a named later use depends on that rule identity.

For a use whose quality meaning remains consequentially ambiguous, “X has quality” is insufficient. State the supported interpretation, use the known endpoint, or retain the unresolved alternatives in the transitional form when its entry conditions are met.

Discipline note. QualitySense is a slot value inside the transitional repair form; it is not a replacement for the endpoint FPF pattern or explicit endpoint source reference. The sense token refines the intended quality sense while the endpoint source, applicable pattern, or EntityOfConcern remains explicit.

Separation note. evaluatorRef and viewpointRef are not synonyms. The evaluator is the observing, criticizing, or selecting party or policy. viewpointRef is a governed reference whose resolution yields one exact U.Viewpoint episteme; selecting or resolving it grants no membership, conformance, authority, or evaluation result.

The checked bearer, any dated assessment work, the resulting claim episteme, witness carriers, an A.10 evidence-provenance path, and an optional EpistemeEmpiricalGroundingRelation remain independently governed. A filled qualityTermAscription(...) may refer to each, but record completion, a result label, or stored witnesses makes none of the neighboring relations obtain.

C.16.Q:4.1b - Polarity discipline (bearer-centred; no silent inverse)

qualityTermAscription is bearer-centred. A transitional ascription SHALL keep the described or evaluated participant in the bearer position and SHALL publish evaluatorRef and governed viewpointRef separately, using none when either is absent. A known endpoint retains its own form and the same participant distinctions.

  • When the evaluating architects are identified as ArchitectureReviewBoard, “Architects rate the system highly” rewrites to qualityTermAscription(bearerTuple={System}, evaluatorRef=ArchitectureReviewBoard, viewpointRef=none, …).
  • When the benchmark’s evaluation policy is identified as BenchmarkPolicy, “The benchmark says model quality is high” rewrites to qualityTermAscription(bearerTuple={Model}, evaluatorRef=BenchmarkPolicy, viewpointRef=none, …).

There is no inverse token that silently makes the evaluator the bearer. If inverse wording is used in Plain prose, rewrite it into the bearer-centred form, or use the explicit inverse form supplied by the applicable pattern.

C.16.Q:4.1c - Endpoint-first discipline

When the endpoint pattern or explicit endpoint source relation is already known, publish the form it defines directly. Keep qualityTermAscription(...) only when preserving the transitional ambiguity is itself informative.

Typical direct endpoints are:

  • engineering -ility heads published as one Characteristic or one Q-Bundle,
  • selector-context uses published as an Objective headed by QS.UseValue unless overridden explicitly,
  • architecture-description uses published under the description-side evaluative head already selected by the viewpoint bundle,
  • explanatory-merit uses published under the explicit merit bundle when that bundle head is already known.

C.16.Q:4.2 - Core construct: QualitySense

Every transitional ascription SHALL identify an explicit QualitySense token. A known endpoint can express the intended claim directly without adding this token or record.

A QualitySense token publishes at least:

QualitySense :=
  ⟨
    senseId,
    bearerArity,
    articulationMode,
    representationSubstrate,
    defaultNormalForm,
    admissibleNormalForms,
    probeOrModelFrameKind,
    comparisonFrameRequired,
    admissibleEvidenceModes,
    admissibleChangeClasses,
    bridgePolicy
  ⟩

Where:

  • articulationMode ∈ { preconceptual, exemplar-grounded, proxy-grounded, characteristic-bound, bundle-bound, objective-bound }
  • representationSubstrate ∈ { embodied-kinesthetic, latent-distributed, symbolic-local, hybrid }
  • defaultNormalForm ∈ { SignalPack, Characteristic, Bundle, Objective }
  • admissibleNormalForms is the explicitly declared set of admissible normal forms for the sense. defaultNormalForm names the primary normal form; any additional endpoint forms MUST be declared here rather than inferred ad hoc. probeOrModelFrameKind constrains only the domain-local probe/model configuration, while comparisonFrameRequired states whether the endpoint calls for two admitted profiles and their A.19.CPM comparator. bridgePolicy can require F.9 recovery or forbid silent reuse, but it cannot establish a Bridge. If the quality ascription is published, handle publication face, form, unit, carrier, and rendering questions under E.17, E.8, or the applicable publication pattern.

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 interpretation rules. Choose the family from the claim; a domain label alone does not determine its sense.

  • In NQD, QD or selector use, the evaluative Q head defaults to QS.UseValue unless another sense is explicitly declared.
  • An engineering quality claim resolves to one explicit U.Characteristic with its CSLC Scale, or an explicit Bundle, preferably a C.25 Q-Bundle when its conditions apply.
  • Description of experienced phenomenal character uses QS.PhenomenalCharacter; preconceptual fit or felt rightness uses QS.PreconceptualFit.
  • A claim about distributed fit in a learned representation uses QS.LatentFit; a claim about closed-loop adequacy uses QS.ControlAdequacy. A model can also receive a different evaluation under its corresponding sense; the phrase “model quality” alone selects none of them.
  • Evaluation of an explanation’s epistemic merit uses QS.ExplanatoryMerit. A different claim, such as readability of its presentation, retains its own subject and criteria.
  • For architecture wording, distinguish the bearer first. Engineering quality of the system and fitness of its architecture description use different subjects and criteria; the latter uses QS.ArchitecturalDescriptionFitness.

C.16.Q:4.4 - Required slots for a conforming qualityTermAscription

A conforming qualityTermAscription SHALL make explicit:

  1. Bearer tuple. Name the exact subject designator or tuple and its arity. A description, carrier, evaluator, or result claim cannot silently replace that bearer.

  2. QualitySense. Name the intended quality-sense family; retain the evaluative criteria when the claim evaluates that subject.

  3. Effective ReferenceScheme. State the effective reference scheme by value in the C.2.1:4.1.2 range EpistemeInterpretationScheme: supply the designation and interpretation rules with their semantic dependencies so every designator and local sense in the ascription is interpretable. The name of a context or representation language alone leaves those rules unspecified.

  4. Probe or model frame. Name the exact domain-local exemplar pack, probe pack, test or criticism pack, Q-bundle definition, CG-frame, acceptance specification, control horizon, or other governed probe/model configuration.

  5. Comparison frame. For a comparison of profiles under A.19.CPM, name the admitted profiles and the applicable comparator and comparison scope. If the claim needs such a comparison and an input is missing, say which conclusion is still open. For a domain comparison that uses a different operation, describe what was compared and on what grounds in the probe or model frame and in the claim. Use comparisonFrameRef = none whenever the claim uses no CPM comparison. When both operations are used, identify the grounds for each.

  6. Evaluator and viewpoint reference. State the evaluator or policy and, independently, either one U.ViewpointRef or none. A non-none reference SHALL resolve to one exact viewpoint episteme under E.17.0; neither the reference nor its resolution is the evaluator.

  7. Normal form and result boundary. State whether the ascription uses SignalPack, Characteristic, Bundle, or Objective. If separately performed assessment work produced a result claim, cite that exact C.2.1 episteme through qualityResultClaimRef; do not identify the work, result, bearer, or transitional record with one another.

  8. ClaimScope, selected slices, and time. State one U.ClaimScope and its exact U.ContextSlice membership when the members matter. State Γ_time when omission changes meaning. U.WorkScope and U.PublicationScope remain with their own work or publication claims rather than substituting for this claim scope. Keep freshness, qualification, and evidence-decay windows with the evidence, capability, or currentness claims they qualify, instead of treating them as quality.

  9. Reference plane when relevant. Name the plane when the same trigger phrase could concern the EntityOfConcern being described, its description, a carrier, or a publication face.

  10. Representation language and substrate when relevant. When it matters to this use, identify the representation language of the selected expression of the quality-term ascription. If the use depends on reading a source expression or a separately obtained result claim, identify the language of that expression in its own right. Retain the effective interpretation rules of the ascription. A viewpoint-specific decoding convention or an embodied-kinesthetic, latent-distributed, symbolic-local or hybrid substrate may also matter. Name each when omission changes interpretation.

  11. Witnesses, evidence use, and empirical grounding when relied on. Name the witnesses relied on for this use. If an evidence-provenance path is relied on, use A.10 for its descriptive account and cite each obtaining direct relation under the pattern that defines it. When empirical grounding is at issue, independently cite an obtaining EpistemeEmpiricalGroundingRelation, or state none; witness or record presence does not create that relation.

  12. Cross-local and endpoint boundaries. Cite an exact F.9 Bridge occurrence and bounded-use claim only when they independently exist. Cite a Card only when that optional package exists, and cite an F.9.1 stance note only when its EntityOfConcern is that claim. State the endpoint pattern or endpoint source relation, the admissible use, and necessary applicability or stop conditions. Add an explanatory non-admissible-use guard only under F.19:4’s independent-ground, plausible-reader, contribution, and smallest-clear-correction test.

C.16.Q:4.5 - Normal-form discipline

A QualitySense SHALL declare one admissible default normal form and MAY declare additional admissible normal forms explicitly.

The normal forms in this section express the recovered quality sense. They are not publication forms by themselves. Publication face, publication form, publication unit, carrier, rendering, export, and front-end questions remain with E.17, E.8, or the applicable endpoint-publication pattern.

QNF-1 - SignalPack. Use for QS.PhenomenalCharacter, QS.PreconceptualFit, and many cases of QS.LatentFit.

A conforming SignalPack contains:

  • exemplar or contrast set or probe set,
  • articulation notes,
  • source episode, carrier, and observer,
  • optional ordinal or thresholded summaries,
  • the signal use it supports and the additional declaration needed before treating a proxy as a Characteristic.

QNF-2 - Characteristic. Use only when the sense is one measurable characteristic on one declared scale. This uses A.17, A.18, and C.16 and inherits full scale legality.

QNF-3 - Bundle. Use when the sense is composite. Typical for QS.ExplanatoryMerit, many engineering quality families, and QS.ControlAdequacy.

A conforming bundle contains:

  • member heads,
  • whether each head is Characteristic, status, mechanism, scope, or test,
  • aggregation policy if any,
  • prohibition on hidden scalarisation.

Engineering note. For engineering -ility families, the preferred bundle endpoint is Q-Bundle (C.25), because it keeps Measures[CHR] distinct from ClaimScope and WorkScope and from Mechanisms and Status. Q-Bundle is a C.25-governed bundle endpoint rather than a fifth normal form beside SignalPack | Characteristic | Bundle | Objective. Do not use a free-floating bundle with hidden metric semantics.

QNF-4 - Objective. Use for QS.UseValue in selection, generation, or search contexts.

A conforming objective contains:

  • CG-frame or objective endpoint source reference,
  • admissible comparators,
  • acceptance or selector policy,
  • reference plane and window,
  • relation to novelty, diversity, and constraints.

C.16.Q:4.6 - Functional vs quality-family discipline

C.16.Q SHALL prevent the collapse of function or capability claims into quality-family claims.

  • A statement about what a system does uses A.6.F first when function-like wording hides the FPF kind, relation, or claim, then applies the pattern for the recovered capability, Method, Work, system-role kind or assignment, A.6.M module-interface, architecture, mathematical, evidence, assurance, gate, decision, or release claim.
  • Choose the sense of how well by the bearer and the evaluation. Maintaining the controlled quantity under a stated class of disturbances over a given horizon uses QS.ControlAdequacy. Evaluating a system’s maintainability under stated service conditions uses QS.EngineeringQualityFamily.
  • “Quality characteristic” and “functional characteristic” SHALL NOT be used as interchangeable labels.
  • In engineering contexts, -ility names are quality-family labels, not automatically Characteristics. They become admissible only as one explicit U.Characteristic or one explicit Bundle (preferably expressed through Q-Bundle when composite).
  • Cross-references are allowed; category collapse is not.

C.16.Q:4.7 - Local repair stances and cross-local Bridge discipline

Within one exact <ReferenceScheme, LocalSenseClaim> interpretation basis, lexical restoration may choose a local sense or rename without asserting an F.9 Bridge. When a use depends on semantic correspondence between two quality senses with different interpretation bases, resolve both exact F.17 SchemeSenseCell values and test the direct F.9 Bridge predicate. Source-local description or separate citation of the two senses needs no such correspondence. Scheme difference, shared spelling, an analogy, a loss note, or a quality record establishes no Bridge.

If the Bridge obtains, cite its exact occurrence and state any proposed comparison, substitution, operationalization, or projection as a separate F.9 bounded-use claim. That claim names the direction, rule, tolerated loss, polarity, and effective ReferenceScheme. Apply A.10 or B.3 only for the reliance branch involved in the proposed use. A Bridge Card remains optional reusable packaging.

Add an F.9.1 stance note only when a short interpretive cue helps a reader understand that exact bounded-use claim. The note is a separate C.2.1 episteme whose EntityOfConcern is the claim. Its optional label may be, for example:

  • localRename — read this use as near-renaming within its declared local boundary; do not infer cross-local identity.
  • operationalizes — read the receiving expression as a procedural or measurable aid for this use; do not infer work, implementation, permission, or suitability beyond the cited claim.
  • partialAnalogy — read the stated correspondence as partial; do not infer substitution.
  • projection — read this use as a deliberate reduction of the source reading; the F.9 claim still carries its rule and tolerated loss.
  • nonEquivalent — treat this as a warning against equivalence and silent substitution; the label alone asserts neither Disjoint, negative polarity, nor an evidence score.

These tokens are optional reading labels inside a stance note. They are not Bridge kinds, direct relations, result claims, or substitutes for the Bridge, bounded-use claim, evidence, or loss account.

Examples:

  • QS.PreconceptualFit and QS.LatentFit are usually only candidates for partial correspondence. If the proposed use depends on correspondence between their exact cross-local F.17 cells, test an F.9 kind such as Partial-overlap; an optional partialAnalogy note may help read the resulting bounded-use claim but cannot establish identity.
  • A progression from QS.PreconceptualFit to QS.PhenomenalCharacter needs its exact direct relation or bounded-use account; shared articulation history does not make the senses identical.
  • A felt cue can prompt a choice of engineering measure without asserting that the measure represents that cue. If the claim instead proposes a cross-local operationalization or projection, establish its Bridge, bounded-use rule and tolerated loss separately from the measurement result. Add a stance note only if it improves the reading.
  • An engineering measure can be selected as an objective under a declared CG-frame. That use does not identify the whole engineering family with selector value. When it depends on a cross-local correspondence, state the F.9 use and any demonstrated loss; selecting an objective alone establishes no loss.
  • An obtaining F.9 Bridge between QS.ExplanatoryMerit and QS.UseValue does not by itself establish identity. An F.9.1 nonEquivalent note may help read an existing bounded-use claim but cannot replace the Bridge finding or claim polarity.
  • Pirsig-style dynamic quality may locally cue QS.PreconceptualFit or sometimes QS.LatentFit. Within one exact interpretation basis this may be a local rename; a proposed correspondence across bases needs exact F.17 cells and F.9 treatment. A source-local account can retain its own meaning. The label alone supplies neither identity nor empirical grounding.
  • Pirsig-style static quality usually cues a Characteristic or Bundle publication under another declared sense; it is not identical with dynamic quality.
  • QS.ArchitecturalDescriptionFitness and QS.EngineeringQualityFamily have different bearer lanes. Any cross-local correspondence must keep the exact description-side and system-side cells, Bridge occurrence, bounded-use claim, and losses separate and must name which description-fitness heads, if any, are proposed to proxy which system-side characteristics.

C.16.Q:4.8 - Change lexicon

Changes to a transitional ascription SHALL preserve the distinctions in this change lexicon. Ordinary wording is sufficient when it makes the changed value or reference clear; the tokens below can support a reusable record:

  • declareQualityTermAscription(...) — create a new explicit quality-ascription record.
  • withdrawQualityTermAscription(...) — retire a prior record.
  • retargetBearer(...) — retarget the bearer ref or tuple while keeping the repair-form schema.
  • reviseSense(...) — change the value in the qualitySense slot.
  • reArticulate(...) — change articulationMode while preserving the sense family.
  • reProxy(...) — change proxy, probe, or operationalization details.
  • reBundle(...) — change bundle members or aggregation policy.
  • reScale(...) — change characteristic scale or scale type.
  • reProbeOrModelFrame(...) — change the exact domain-local probe or model frame.
  • reComparisonFrame(...) — change the independently governed A.19.CPM comparison configuration.
  • retargetEvaluator(...) — change the evaluator or policy ref without changing the viewpoint by implication.
  • retargetViewpointRef(...) — retarget the governed U.ViewpointRef; resolution yields another exact viewpoint episteme only when the new reference resolves.
  • reReferenceScheme(...) — change the effective ReferenceScheme explicitly; because that changes interpretation, re-check C.2.1 identity for any published claim episteme.
  • rescopeClaim(...) — change U.ClaimScope or its exact U.ContextSlice members.
  • retime(...) — change Γ_time.
  • refreshWitnessRefs(...) — refresh witness bindings without silently changing an evidence-provenance path or grounding relation.
  • replaceEvidenceProvenancePath(...) — replace the cited A.10 path of exact direct relations; replacing the path does not by itself constitute a quality result.
  • replaceEmpiricalGroundingRelationRef(...) — cite another independently obtaining C.2.1 grounding occurrence; a record edit cannot make it obtain.
  • retargetBridgeOccurrenceRef(...) — retarget an exact F.9 occurrence ref; it does not retarget a bounded-use claim, optional Bridge Card, or optional stance note by implication.
  • exitQualityAscription(...) — end use of the quality-ascription form and continue with the pattern for the recovered non-quality claim; never silently retype the old record.

A silent sense rewrite is a breaking semantic change. If the record no longer expresses a quality ascription, close it with exitQualityAscription(...) and publish the recovered claim in the form needed for its use.

A.6.P rewrite note. retargetBearer(...) is the family-specific form of retargetParticipant(BearerSlot, …). It, retargetEvaluator(...), retargetViewpointRef(...), and retargetBridgeOccurrenceRef(...) are reference-retargeting moves and SHALL preserve the A.6.5 distinction between a reference and the object it resolves. reviseSense(...), reArticulate(...), reProxy(...), reBundle(...), reScale(...), reProbeOrModelFrame(...), and reComparisonFrame(...) refine reviseByValue(...). reReferenceScheme(...) and rescopeClaim(...) change interpretation-bearing values and require an identity check for any published C.2.1 episteme. Witness, evidence-path, result-claim, grounding-relation, Bridge, bounded-use-claim, Card, and stance-note refs change independently; no edit silently rewrites another.

C.16.Q:4.8a - A.6.B boundary classification template for quality-term repair

When a repaired quality statement carries a boundary claim, preserve its A.6.B classification. A local sentence with one recoverable logical job needs no separate Claim Register or publication form. For a reusable boundary account, distinguish:

  • L — qualityTermAscription repair-form skeleton, QualitySense semantics, normal-form admissibility, cross-local routing, and the rule that any F.9.1 stance note remains a separate optional episteme about an already constituted bounded-use claim;
  • A — admissibility conditions for using the ascription in selector, gating, and publication lanes (required qualifiers, witnesses, thresholds, qualification windows);
  • D — publication requirements (lexical firewall, mandatory rewrites, publication duties);
  • E — carrier-anchored evidence and work effects (measurements, traces, critique sheets, probe packs, selector logs).

Where this family is published as a reusable boundary publication, stable L-Q*, A-Q*, D-Q*, and E-Q* claim ids SHOULD be published (or the reused L/A/D/E-classified claim set should be cited by location), and paraphrase drift across quadrants SHALL be avoided. Do not let the bare word quality carry L/A/D/E claim by itself.

C.16.Q:4.9 - Lexical guardrails

In Tech and normative prose:

  • a consequentially ambiguous quality claim MUST resolve to its known endpoint or, when needed, an explicit transitional QualitySense;

  • high-quality, low-quality, quality metric, quality score, quality requirement, model quality, architecture quality, and solution quality cue inspection of the intended claim;

  • quality characteristic MAY appear only as:

    • a source-local term whose cited standard or tradition supplies its meaning, with F.9 used only for a needed semantic correspondence, or
    • a family label immediately rewritten into one explicit U.Characteristic or Q-Bundle;
  • a claim using quality requirement or quality requirements SHALL make the required head and its requirement or acceptance relation recoverable. Use the applicable rule for that claim; a named Characteristic, Q-Bundle head or objective can supply the evaluated content. The phrase itself establishes no requirement or acceptance result;

  • 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 described or evaluated) and, when omission changes meaning, an explicit referencePlane;

  • when quality denotes a QD or NQD selector’s Q head, use QS.UseValue by default. For wording about the reliability of a recorded input, recover what the recording procedure established;

  • 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 the recovered subject rule directly, or A.6.A while the action meaning remains unclear, with source-tradition affordance wording retaining its cited meaning when used;

  • 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.

C.16.Q:4.10 - Progressive elaboration

A transitional ascription can be elaborated as its interpretation becomes clearer. Changed grounds can also require revising or withdrawing earlier content; elaboration is not necessarily monotone:

  1. Select a QualitySense and retain rival candidates while the intended sense remains unresolved.
  2. Name the exact bearer, effective ReferenceScheme, U.ClaimScope, and any meaning-changing Γ_time, reference plane, language of the selected expression, or substrate.
  3. Name the probe or model frame and record any comparison it makes. Give the separate A.19.CPM frame when comparing admitted profiles under a declared comparator, or none otherwise; then name evaluator and U.ViewpointRef independently.
  4. Choose an admissible normal form and identify any separately constituted quality-result claim.
  5. Add exemplars, probes, characteristic heads, bundle members, objective pins, witness refs, and exact A.10 evidence-provenance paths as needed. Cite empirical grounding only through an independently obtaining relation.
  6. If the use depends on cross-local correspondence, resolve exact F.17 cells, the obtaining F.9 Bridge, and the separate bounded-use claim. Add a Card only as optional packaging and an F.9.1 stance note only as optional reader help about that claim.
  7. Preserve any boundary claim and its material dependencies under A.6.B; add stable hooks only when the receiving use needs them.
  8. Never move between sense families, frames, schemes, scopes, result claims, or neighboring relations silently.

C.16.Q:5 - Archetypal Grounding

C.16.Q:5.1 - Tell

If a draft uses quality for an FPF-governed claim without a recoverable sense, make that sense explicit.

A completed ordinary repair. A report says “architecture quality improved,” but its supplied comparison concerns two editions of an architecture description. Both describe the same system and serve the same three decision questions. AD1 supplies the required dependency information for two questions; AD2 supplies it for all three. The same coverage rule is applied to both descriptions. The supported statement is: “AD2 supplies the dependency information for all three declared decision questions; AD1 supplied it for two.” This can finish the wording repair. It asserts no change to the system’s availability or security. If the decision questions change, compare both descriptions against the new question set before repeating the improvement claim. A conforming rewrite publishes either the form for one known endpoint or one explicit qualityTermAscription(...) transitional record with bearer, one QualitySense, effective ReferenceScheme, its probe/model frame and its A.19.CPM frame or none, evaluator and U.ViewpointRef, ClaimScope, admissible normal form, endpointPatternLocator or endpoint source relation, and explicit boundaries among result claim, witnesses, evidence use, empirical grounding, Bridge, bounded-use claim, optional Card, and optional stance note.

C.16.Q:5.2 - Show (Latent fit and control adequacy)

The following pairs make alternative interpretations of each draft inspectable. Use these transitional ascriptions only while selecting the intended reading; once it is known, publish its endpoint form directly.

The examples stipulate their named objects and source relations. Each non-none comparisonFrameRef identifies an A.19.CPM comparison of two admitted profiles under an applicable comparator. Each non-none viewpointRef resolves one E.17.0 viewpoint episteme.

A named result claim is not assessment work, witness refs do not establish an A.10 evidence-provenance path, and neither witnesses nor a result label establish the grounding relation cited beside them. In the model and architecture improvement examples, the cited result claim asserts the improvement under its named comparison frame; the ascription record refers to that claim.

Draft: “The model quality improved.”

Repair A — latent representation line

qualityTermAscription(
  bearerTuple = {Model_v5},
  qualitySense = QS.LatentFit,
  effectiveReferenceScheme = RepLearningScheme_5,
  probeOrModelFrameRef = ProbePack_PP2,
  comparisonFrameRef = LatentFitComparison_CF2,
  evaluatorRef = RepLearningReviewBoard,
  viewpointRef = none,
  normalForm = SignalPack,
  claimScope = U.ClaimScope({RepresentationLearningSlice_RL5}),
  gammaTime = Window_W5,
  qualityResultClaimRef = LatentFitResultClaim_22,
  witnessRefs = {ProbeSeparationRun_22, AliasRiskCard_9},
  evidenceProvenancePathRefs = {LatentFitEvidencePath_22},
  empiricalGroundingRelationRef = EGR_LatentFitResult_22,
  endpointPatternLocator = C.16.Q:4.5,
  admissibleUse = interpret the supplied latent-fit comparison under ProbePack_PP2
)

Here EGR_LatentFitResult_22 denotes a separately established relation between the exact result episteme and exact grounding holon under the governed probe or measurement relations. The run and card alone would not establish it.

Repair B — closed-loop control line

qualityTermAscription(
  bearerTuple = {PolicyModelPair_PM5},
  qualitySense = QS.ControlAdequacy,
  effectiveReferenceScheme = ClosedLoopControlScheme_5,
  probeOrModelFrameRef = Horizon_H × EnvClass_E,
  comparisonFrameRef = ControlBaselineComparison_CF5,
  evaluatorRef = ControlReviewBoard,
  viewpointRef = ControlViewpointRef_7,
  normalForm = Bundle,
  claimScope = U.ClaimScope({ControlDeploymentSlice_7}),
  gammaTime = RunWindow_RW,
  qualityResultClaimRef = ControlAdequacyResultClaim_41,
  witnessRefs = {ClosedLoopTraceSet_41},
  evidenceProvenancePathRefs = {ControlEvidencePath_41},
  empiricalGroundingRelationRef = EGR_ControlAdequacyResult_41,
  endpointSourceRelationRef = ClosedLoopCriterionBundleDefinition_5,
  admissibleUse = interpret the supplied control-adequacy result within Horizon_H and EnvClass_E
)

ClosedLoopCriterionBundleDefinition_5 identifies the control criteria applied over Horizon_H in EnvClass_E. The comparison with the baseline uses the admitted controller profiles and comparator identified by ControlBaselineComparison_CF5.

C.16.Q:5.3 - Show (Preconceptual fit and explanatory merit)

Draft: “Quality matters before definition.”

First recover what remains undefined and how quality is said to affect the work. For one constructed reading, suppose EpisodeNotes_3 states that participants noticed a felt mismatch, used it to revise the problem framing, and only then articulated the criterion for that mismatch. The ordinary repair is: “During PF3, the participants used a felt mismatch to revise the problem framing before they stated the criterion for that mismatch.” Once this is the intended account, the sentence can finish the repair without a transitional record. The records below show partial sense resolutions while the intended claim remains open.

Partial interpretation A — preconceptual fit

qualityTermAscription(
  bearerTuple = {ProblemFramingEpisode_PF3},
  qualitySense = QS.PreconceptualFit,
  effectiveReferenceScheme = FeltFitArticulationScheme_3,
  probeOrModelFrameRef = ExemplarPack_EP3,
  comparisonFrameRef = none,
  evaluatorRef = ReviewerGroup_A,
  viewpointRef = none,
  normalForm = SignalPack,
  claimScope = U.ClaimScope({ProblemFramingSlice_PF3}),
  representationSubstrate = embodied-kinesthetic,
  qualityResultClaimRef = PreconceptualFitClaim_PF3,
  witnessRefs = {EpisodeNotes_3},
  evidenceProvenancePathRefs = none,
  empiricalGroundingRelationRef = none,
  endpointPatternLocator = C.16.Q:4.5,
  admissibleUse = inspect the articulated felt-fit account without treating it as a measured Characteristic
)

Here ExemplarPack_EP3 records the episodes the participants compared and what felt different to them. That is enough to discuss the change in problem framing. The episode notes witness the articulation. No profile comparison or empirical measurement was made.

Partial interpretation B — explanatory merit

qualityTermAscription(
  bearerTuple = {Explanation_N5},
  qualitySense = QS.ExplanatoryMerit,
  effectiveReferenceScheme = ExplanationCriticismScheme_5,
  probeOrModelFrameRef = CriticismBundle_CB4,
  comparisonFrameRef = none,
  evaluatorRef = TheoryReviewPanel,
  viewpointRef = none,
  referencePlane = episteme,
  normalForm = Bundle,
  claimScope = U.ClaimScope({ExplanationReviewSlice_N5}),
  qualityResultClaimRef = ExplanatoryMeritResultClaim_14,
  witnessRefs = {CritiqueSheet_14, CounterexampleSet_2},
  evidenceProvenancePathRefs = {ExplanationEvidencePath_14},
  empiricalGroundingRelationRef = none,
  endpointSourceRelationRef = CriticismBundleDefinitionSource_CB4,
  admissibleUse = compare the stated explanatory-merit heads against the named rivals
)

In CritiqueSheet_14 the panel compares explanations N5 and N4 against the counterexamples. N5 accounts for the response after the input was removed, which N4 predicts should end immediately. This finding concerns that response under the stated conditions. CriticismBundleDefinitionSource_CB4 cites the supplied definition of the explanatory-merit Bundle. Its criticism criteria determine that endpoint; the shared word “Bundle” does not make C.25 the governor of explanatory merit.

This record identifies an explanatory-merit reading. What is to be defined, how that merit affects the work, and in what sense it precedes the definition remain unresolved until the criticism account supplies them. Preserve those parts of the draft; the sense ascription alone does not complete its repair.

C.16.Q:5.3a - Show (System quality and architecture-description fitness)

Draft: “The architecture quality improved.”

Repair A — quality of the system-side bearer

qualityTermAscription(
  bearerTuple = {PaymentPlatform_v4},
  qualitySense = QS.EngineeringQualityFamily,
  effectiveReferenceScheme = PlatformEngineeringQualityScheme_4,
  probeOrModelFrameRef = Q_Bundle_AvailabilitySecurityEvolvability_3,
  comparisonFrameRef = PlatformVersionComparison_CF4,
  evaluatorRef = ArchitectureReviewBoard,
  viewpointRef = ProjectSystemEngineeringQualityViewpointRef_4,
  referencePlane = world,
  normalForm = Bundle,
  claimScope = U.ClaimScope({PaymentPlatformEngineeringSlice_4}),
  qualityResultClaimRef = PlatformQualityResultClaim_8,
  witnessRefs = {AvailabilityReport_8, CouplingCheck_3, EvolvabilityNote_2},
  evidenceProvenancePathRefs = {PlatformQualityEvidencePath_8},
  empiricalGroundingRelationRef = EGR_PlatformQualityResult_8,
  endpointPatternLocator = C.25,
  admissibleUse = compare the stated engineering-quality heads for PaymentPlatform_v4
)

Repair B — quality of the architecture description

qualityTermAscription(
  bearerTuple = {ArchitectureDescription_AD12},
  qualitySense = QS.ArchitecturalDescriptionFitness,
  effectiveReferenceScheme = ArchitectureDescriptionFitnessScheme_12,
  probeOrModelFrameRef = ArchitectureDescriptionProbeFrame_AD12,
  comparisonFrameRef = DescriptionEditionComparison_CF12,
  evaluatorRef = ArchitectureReviewBoard,
  viewpointRef = ProjectArchitectureDescriptionFitnessViewpointRef_12,
  referencePlane = episteme,
  normalForm = Bundle,
  claimScope = U.ClaimScope({ArchitectureDescriptionReviewSlice_AD12}),
  qualityResultClaimRef = DescriptionFitnessResultClaim_7,
  witnessRefs = {CoverageMatrix_4, CorrespondenceCheck_7, ViewConsistencyNote_2},
  evidenceProvenancePathRefs = {DescriptionFitnessEvidencePath_7},
  empiricalGroundingRelationRef = none,
  endpointSourceRelationRef = DescriptionFitnessDefinitionSource_AD12,
  admissibleUse = compare description fitness under the supplied viewpoint and decision questions
)

ArchitectureDescriptionProbeFrame_AD12 is one project-local probe frame: it may cite DecisionQuestionSet_DQ7, an architecture-description result under C.30.AD, structural-view adequacy under C.30.ASV, and the retained U.ViewpointRef members resolved from a constituted E.17.1 catalogue. It is neither a viewpoint-family value nor a substitute for the selected viewpoint.

DescriptionFitnessDefinitionSource_AD12 cites the supplied definition of the description-side Bundle, including decision-question coverage and correspondence soundness. C.25 supplies a Q-Bundle only when its engineering-quality conditions apply; the architecture-description and viewpoint patterns supply their own checks.

The shared evaluator does not collapse the two repairs: their bearers, schemes, probe/model frames, scopes, viewpoint references, result claims, and evidence paths differ.

C.16.Q:5.4 - Show (QD or selector lane)

Draft: “Quality in our QD loop.”

Repair

qualityTermAscription(
  bearerTuple = {Candidate_7},
  qualitySense = QS.UseValue,
  effectiveReferenceScheme = QDUseValueScheme_9,
  probeOrModelFrameRef = CG_Frame_9,
  comparisonFrameRef = none,
  evaluatorRef = SelectorPolicy_P4,
  viewpointRef = none,
  normalForm = Objective,
  claimScope = U.ClaimScope({QDSelectionSlice_9}),
  gammaTime = SelectionWindow_SW,
  qualityResultClaimRef = UseValueResultClaim_9,
  witnessRefs = {ObjectiveCard_9, AcceptanceSpec_4},
  evidenceProvenancePathRefs = {QDSelectionEvidencePath_9},
  empiricalGroundingRelationRef = none,
  endpointSourceRelationRef = ObjectiveDefinitionSource_CG9,
  admissibleUse = interpret the supplied objective value under SelectorPolicy_P4
)

ObjectiveDefinitionSource_CG9 cites the objective definition supplied by CG_Frame_9. C.17 can characterize the candidate’s value under that objective; it does not supply the objective’s definition merely by being named.

C.16.Q:6 - Bias-Annotation

The following biases apply to overloaded evaluative uses of quality in FPF-governed wording.

  • Gov bias: this pattern favors explicit evaluative publication and explicit L/A/D/E hooks, which improves auditability but adds drafting overhead.
  • Arch bias: a transitional record can make unresolved alternatives reusable, but its fields can burden a question already settled by ordinary prose or a known endpoint. Use the lighter sufficient result first.
  • Onto-Epist bias: this pattern distinguishes preconceptual, latent, explanatory, engineering, and selector senses; doing so requires extra lexical work.
  • Prag bias: this pattern defaults QD and NQD uses toward UseValue, which improves selector clarity but can feel narrower than colloquial “quality”.
  • Did bias: this pattern uses repeated rewrites for teaching; the risk is over-formalizing early exploratory language.

C.16.Q:7 - Conformance Checklist (CC-C16Q)

Apply the following conditions to the branch used. A known endpoint follows its own form. Requirements for ascription fields and records apply when the transitional form is used; the semantic distinctions remain relevant wherever they change the claim.

  1. CC-C16Q-1 - Explicit endpoint classification and explicit sense. Every repaired claim makes its subject, intended sense and governing conditions recoverable. Use a known endpoint directly. A transitional qualityTermAscription(...) has an explicit QualitySense and endpoint classification; an adequate ordinary explanation needs no additional record.
  2. CC-C16Q-2 - Exact bearer and arity. The bearer designator or tuple is explicit; description, carrier, evaluator, viewpoint, work, and result are not substituted for it.
  3. CC-C16Q-3 - Exact probe/model and comparison frames. Identify the domain procedure and the basis for any comparison made there. Give the A.19.CPM frame for a comparison of admitted profiles under its comparator, and none when that operation is absent. A missing profile or comparator leaves a claim that requires the operation unresolved.
  4. CC-C16Q-4 - Effective scheme, evaluator, and viewpoint reference. The effective reference scheme is explicit. Evaluator and U.ViewpointRef are separate; a non-none reference resolves one exact viewpoint episteme and grants no conformance, membership, authority, or result.
  5. CC-C16Q-5 - Substrate and referencePlane are declared when relevant. Cross-talk across articulation modes (including preconceptual), representation substrates (including latent-distributed and symbolic-local), or ReferencePlane values world, concept, and episteme is not allowed without explicit substrate and, when omission would change meaning, plane declarations.
  6. CC-C16Q-6 - ClaimScope, slices, and Γ_time are explicit. One U.ClaimScope, its meaning-changing U.ContextSlice members, and any meaning-changing Γ_time are stated; work or publication scope does not substitute for claim scope.
  7. CC-C16Q-7 - Admissible normal form and result boundary. The ascription uses SignalPack, Characteristic, Bundle, or Objective with the corresponding normal-form discipline; any checked object, assessment work, result claim, witnesses, evidence-provenance path, and empirical-grounding relation remain independently identified.
  8. CC-C16Q-8 - No illegal scalarization. Composite senses are not collapsed into one score without an explicit admissible scoring and comparison method.
  9. CC-C16Q-9 - No silent sense rewrite. Any semantic change preserves the distinctions of the declared change lexicon; changing sense, scheme, frame, scope, or neighboring relation silently is forbidden.
  10. CC-C16Q-10 - QD default. When quality denotes the selector’s Q head, use QS.UseValue unless an explicit interpretation applies. Identify the bearer of a claim about the quality of an input, a search procedure or its record.
  11. CC-C16Q-11 - Engineering family discipline. Engineering -ility uses resolve to one explicit U.Characteristic or one explicit Bundle, preferably a Q-Bundle when composite; they do not remain free-floating adjectives.
  12. CC-C16Q-12 - Functional separation. Function or capability claims remain distinct from quality-family claims.
  13. CC-C16Q-13 - Bridge accountability. When cross-local comparison requires semantic correspondence, it resolves exact F.17 cells and cites an obtaining F.9 Bridge plus the exact bounded-use claim when a use is proposed. Source-local description or independent citation of different senses does not require that Bridge. Any optional Card and F.9.1 stance note remain separate; the stance note’s EntityOfConcern is that claim. A stance word, CL, shared label, or loss note establishes none of them.
  14. CC-C16Q-14 - Boundary-claim hook when needed. For a repaired ascription used in a boundary decision, the relevant claims and material dependencies remain recoverable under A.6.B. A separate register or publication form is needed only under its receiving-use conditions.
  15. CC-C16Q-15 - Lexical firewall. The intended sense is recoverable in Tech and normative claims; already adequate endpoint wording and marked metalinguistic discussion need no further ascription.
  16. CC-C16Q-16 - Transitional skeleton is complete. The published skeleton carries bearer position and bearer-kind mismatch repair, sense, effective scheme, exact frames, evaluator, U.ViewpointRef, ClaimScope, qualifier expectations, normal form, result, witness/evidence/grounding discipline, admissible change classes, and cross-local boundaries without minting universal context, frame, evidence, or grounding kinds.
  17. CC-C16Q-17 - Consequential alternatives remain inspectable. If sense selection, bearer facet, or the distinction between the EntityOfConcern being described or evaluated, a description or other episteme, a publication face, and a carrier described or evaluated in its own right is non-obvious, the remaining alternatives are made inspectable before a decision or publication relies on their resolution. An adequate existing explanation can supply this; a separate Candidate-Set Note is optional.
  18. CC-C16Q-18 - Reference resolution is not object substitution. Designators, governed refs, their resolved viewpoint or bearer objects, evaluator, result, frame, scope, grounding holon, and any selected structure remain distinct.
  19. CC-C16Q-19 - Change verbs dock cleanly with A.6.P and A.6.5. retargetBearer(...) and the other declared reference moves are used only for ref retargeting; by-value revisions remain distinct from reference changes; a scheme or scope change triggers claim-identity review; edits to witnesses, evidence paths, grounding, Bridge, bounded-use-claim, Card, or stance-note refs do not silently rewrite one another; and silent retyping is forbidden.

C.16.Q:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomWhy it failsHow to avoid or repair
Magic scalar qualityone number silently stands for several evaluative familiesconflates senses and bearers and ignores scoring legalitypublish the known endpoint or an explicit transitional QualitySense with an admissible normal form
Preconceptual-as-metricfelt fit is presented as if it were already a measured characteristicerases articulation stage and overstates evidencereport the felt mismatch when that answers the question. If a measured indicator is needed, formulate its criterion, justify the proxy and obtain the observation
Engineering adjective driftreliable, maintainable, or high-quality appear with no explicit Characteristic or Q-Bundlehides measurement shape and scoperewrite to one U.Characteristic or one Q-Bundle
Selector ambiguityquality in QD and NQD is left undefinedbreaks comparability and selection semanticsdefault to QS.UseValue unless another objective head is declared explicitly
Model-quality collapselatent fit, explanatory merit, and control adequacy are merged under one phrasedestroys bearer and frame distinctionsstate the distinct claims under their endpoints; use separate transitional ascriptions only while the meanings remain unresolved
Architecture-vs-description collapsearchitecture quality is used with no explicit bearer lanecollapses the system-side bearer into its description, carrier, or publication facepublish the bearer lane explicitly and select QS.EngineeringQualityFamily or QS.ArchitecturalDescriptionFitness
Action-invitation-as-qualityaction invitations are narrated as if they were evaluationsthe rewrite hides action semantics instead of clarifying themstop the Q-rewrite and use the subject rule for the recovered claim or question; use A.6.A only while the action meaning remains unclear; state the claim or question and the participants and conditions its use needs; retain the cited source meaning of affordance when that source-local term is used
Generic-frame collapseone evaluationFrame or context label is expected to supply probe, model, comparison, scope, and scheme semanticshides independently governed choices and makes a changed comparison look like the same claimname the effective ReferenceScheme, probe/model frame, A.19.CPM frame if used, and ClaimScope separately
Embedded viewpointthe record stores a viewpoint-looking value as evaluator or generic contextcollapses reference, viewpoint episteme, evaluator, and resultstore one governed U.ViewpointRef or none; resolve it under E.17.0 and keep evaluator separate
Witness-is-groundinga test report, trace, score, or filled record is cited as empirical groundingpresence of a carrier or result label establishes no direct relationname witness refs and A.10 path separately; cite an exact obtaining EpistemeEmpiricalGroundingRelation or none
Bridge-by-label or stance noteshared quality wording or an F.9.1 stance word is treated as the cross-local relation or use authoritycreates false identity, silent loss, and unauthorized substitutionresolve exact F.17 cells, test and cite the F.9 Bridge, then state the separate bounded-use claim; add a Card only as optional packaging and a stance note only when its EntityOfConcern is that claim

C.16.Q:9 - Consequences

Benefits. The pattern makes a quality statement’s meaning and grounds inspectable across phenomenology, engineering, and search and selection contexts. A transitional ascription keeps consequential alternatives inspectable. Once their meaning is resolved, state the claim in the form supplied by the applicable endpoint.

Trade-offs and mitigations. The pattern adds drafting overhead and can feel heavy in exploratory notes. Mitigation: use an adequate ordinary explanation or known endpoint directly. Restore a missing distinction before relying on it in an evaluation or further claim; use of the Tech register alone does not require the full transitional form.

C.16.Q:10 - Rationale

C.16.Q distinguishes the senses of “quality”:

The word “quality” is not treated as one concept. It is treated as a family of quality-sense ascriptions whose members differ by substrate, articulation mode, bearer, effective scheme, probe/model configuration, comparison configuration, ClaimScope, and admissible normal form.

This lets FPF discuss:

  • Pirsig-like preconceptual fit,
  • representation-learning and neuro-symbolic latent fit,
  • explanation quality in criticism-driven inquiry,
  • architecture-description fitness under a viewpoint,
  • engineering quality families,
  • use-value in open-ended evolution,
  • control adequacy in action loops,

without forcing them into one universal scalar.

It also makes the distributed-vs-local issue explicit:

  • some senses originate in embodied or latent-distributed substrates,
  • some are only publishable as symbolic-local CHR, bundle, and objective forms,
  • and some require an explicit projection from the first into the second.

It also makes the bearer and plane issue explicit:

  • some uses evaluate the EntityOfConcern being described,
  • some evaluate its description under a viewpoint,
  • some evaluate a carrier or publication face,
  • and those uses must not be collapsed without an explicit bearer lane and, when needed, a declared referencePlane.

Semantic drift usually starts at these bearer and plane distinctions; C.16.Q makes the interpretation choices inspectable.

C.16.Q:11 - SoTA-Echoing

The source contributions below address different quality questions. Their common use here is to recover the subject, intended sense and supported conclusion while retaining the distinctions among traditions. Recover the criteria when an evaluation is made.

Source and scopeContribution to quality-term interpretationUse boundary
ISO/IEC/IEEE 42010:2022, Software, systems and enterprise — Architecture description; architecture-description referenceDistinguishes the entity under description from the architecture description and organizes description through viewpoints, concerns and model kinds. This supports separate system-side and description-side evaluations.A description’s fitness does not establish system quality. The standard’s conceptual model is not imported as FPF ontology or as a complete wording-repair Method.
ISO/IEC 25010:2023, Systems and software engineering — SQuaRE — Product quality model; quality-model referenceNamed characteristics and subcharacteristics make engineering quality claims and requirements more explicit. Composite contributions can require a Bundle rather than one scalar.The source list does not automatically supply an adequate FPF evaluation space. A particular claim still needs its Characteristic, Scale or applicable endpoint.
Ford, Parsons, Kua and Sadalage (2022), Building Evolutionary Architectures, 2nd ed.; evolutionary-architecture practiceConcern-specific fitness functions connect architecture change to explicit checks. They help replace rhetorical quality claims with the evaluated contribution.Fitness functions do not define one universal quality value or identify engineering quality, control adequacy and selector value.
Fontaine, Togelius, Nikolaidis and Hoover (2020), Covariance matrix adaptation for the rapid illumination of behavior space; Fontaine and Nikolaidis (2023), Covariance Matrix Adaptation MAP-Annealing; QD selector semanticsQD seeks collections that combine objective performance with diversity under declared descriptors. C.16.Q uses QS.UseValue as the default selector Q head and keeps novelty, diversity and constraints distinct.The objective and archive rules remain those of the search. No unexplained scalar may replace their distinct contributions.
Parr, Pezzulo and Friston (2022), Active Inference; LeCun (2022), A Path Towards Autonomous Machine Intelligence; Friston et al. (2024), Designing Ecosystems of Intelligence from First Principles; model and control researchRepresentation, prediction, planning, uncertainty and task value supply different evaluation questions. QS.LatentFit, QS.ControlAdequacy and QS.UseValue distinguish relevant readings when those are the claims made.A domain label or the phrase “model quality” selects none of these readings by itself. The source frameworks retain their own concepts and premises.
Schoeller (2022), work on Thinking at the Edge and embodied critical thinking; articulation practice and lineageTentative language can clarify felt aspects while remaining responsive to experience. This supports QS.PreconceptualFit in SignalPack form, distinct from phenomenal character itself.Articulating a felt signal does not by itself yield a measured Characteristic. Source episodes and witnesses retain their relation to the claim.
Hansen (2024), Perceiving affordances and the problem of visually indiscernible kinds; Jorba and Lopez-Silva (2024), Mind in action: expanding the concept of affordance; action-oriented recognitionAn apparent quality statement may instead concern an action possibility or invitation. Recover that claim or question under A.6.A when its meaning is unclear, then use its subject rule.A sufficient source-local explanation can finish the recovery. The source term does not create one FPF relation kind or a quality sense; a relation claim requires its own predicate.
Khalifa (2017), Understanding, Explanation, and Scientific Knowledge; reference for an explanatory-merit familyExplanatory understanding and epistemic value can require several explicit merit heads. QS.ExplanatoryMerit keeps that evaluation distinct from engineering performance and selector utility.This reference does not license a universal merit score. The applicable criticism criteria remain explicit.

Scale legality. A numerical quality claim SHALL use the Scale and comparison or aggregation rule required by its meaning. A comparison identifies its comparator set or applicable CG-Spec; a composite score states its admissible aggregation. Neither quality wording nor these source correspondences licenses covert scalarization of bundles, explanations or preconceptual signals.

Source-local and cross-local use. A vocabulary can be described or cited in its own sense. When a proposed use depends on semantic correspondence between different <ReferenceScheme, LocalSenseClaim> bases, resolve the exact F.17 cells and test F.9. The Bridge and bounded-use claim, direction, rule, tolerated loss, polarity, any evidence reliance and any cross-plane representation relation remain separately established. A stance label or loss note supplies none of those relations by itself.

Earlier touchstones such as Pirsig, Popper and Deutsch remain useful for historical lineage and local terminology. Their concepts retain their source meanings. The shared word “quality” supplies a question to clarify, not a general identity across the subjects and practices.

C.16.Q:12 - Relations

  • Lives in: C.16 characterization pattern nest as the quality-term realization of E.10.ARCH and C.16.P.

  • Builds on: E.10.ARCH for shared wording-use restoration architecture; C.16.P for characteristic and scale exits; A.2.6 for explicit scope and Γ_time; A.17, A.18, and C.16 for admissible measurable characteristics; C.25 for engineering Q-Bundle publication.

  • Coordinates with:

    • A.6.P when recovered content is relation construction rather than evaluative characterization;
    • A.6.A to recover an ambiguous action-oriented claim or question, then its subject pattern;
    • C.2.2a, A.16, A.16.1, A.16.2, B.4.1, and B.5.2.0 for language-state positions, early cues, next-use docking, and retreat or reopen; use A.16.0 only when lineage, branch, loss, or an actual responsibility-handoff history itself must be published as an explicit trajectory account;
    • C.2.LS, C.2.4, C.2.5, C.2.6, and C.2.7 for language-state facets;
    • C.2.1 for effective ReferenceScheme, exact result-episteme identity, and optional EpistemeEmpiricalGroundingRelation;
    • A.2.6 for U.ClaimScope and U.ContextSlice;
    • A.19.CPM for a comparison of admitted profiles under its comparator;
    • A.10 for evidence-provenance and bounded reliance;
    • C.17, C.18, and C.19 for selector value, novelty, diversity, and policy;
    • E.17.0 and E.17.2 for exact viewpoint epistemes and U.ViewpointRef; C.30.AD and C.30.ASV for architecture-description and structural-view use;
    • F.9 for exact cross-local Bridge occurrences and bounded-use claims; F.9.1 only for separate optional stance notes about those claims;
    • A.6.B when repaired ascriptions become boundary-bearing.
  • Further distinctions: C.3.3 governs any needed comparison or bridge between distinct endpoint kinds; A.19.CN governs questions of comparability; C.2.P recovers a hidden source or publication use. These questions arise from the claim, not from the shared quality label.

  • Publishes vocabulary through: E.10, F.17, and F.18 when the qualityTermAscription repair-form skeleton, the QualitySense starter set, and the red-flag rewrites become stable shared vocabulary.

C.16.Q:12.1 - Endpoint-first use

This pattern uses endpoint-first assignment rather than universal governance of all quality language. qualityTermAscription(...) remains useful as a transitional repair form, but it is not the required resting place or durable local record kind for every repaired use of quality.

C.16.Q:12.2 - Explicit endpoint selection

Admissible endpoints after repair include:

  • a single Characteristic,
  • a Q-Bundle,
  • an E.21 PatternQualityQBundle, when the bearer is one FPF pattern version and the evaluative claim asks whether the pattern is good enough for a declared reader, use, and scope. In this case, do not assign the claim to general C.25 unless the bearer is a non-pattern engineering quality family,
  • an Objective,
  • an explanatory-merit bundle,
  • a selector-value endpoint.

Quality wording whose intended claim is already recoverable can use the applicable endpoint directly. A known endpoint needs no additional qualityTermAscription(...) record.

C.16.Q:12.3 - What C.16.Q leaves to other patterns

C.16.Q does not define or test articulation-state characteristics, Bridge truth, bounded-use claims, stance-note identity, evidence-provenance, empirical grounding, profile comparison operations, viewpoint resolution, or representation factors. Use A.16, C.2.LS, C.2.4, C.2.5, C.2.6, C.2.7, F.9, F.9.1, A.10, C.2.1, A.19.CPM, E.17.0, or the applicable representation pattern for those questions.

C.16.Q:End

Referenced in the corpus

101 literal mentions in other sections. Read their context to establish the relation.