#Quality-Term Precision Restoration

C.16.Q · Cluster C.IV - Composite & Macro-Scale · Stable · Characterization precision-restoration pattern · Normative unless explicitly marked informative · Part C - Kernel Extension Specifications

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

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

Plain-name. Quality-term precision restoration.

Intent. Provide a reusable discipline for repairing overloaded quality and evaluative-characterization wording in FPF texts.

This pattern lives in the C.16 characterization pattern nest. It rewrites bare evaluative prose either into one explicit endpoint-pattern-governed form or, while endpoint selection is being stabilized, into one transitional quality-term repair form with exact bearer, QualitySense, effective ReferenceScheme, separate probe/model and comparison configurations, evaluator and U.ViewpointRef, U.ClaimScope, admissible normal form (SignalPack | Characteristic | Bundle | Objective), result/evidence/grounding boundaries, reference-plane accountability, and lexical guardrails.

It allows philosophical, neuro-symbolic, control-theoretic, engineering, and open-ended-search uses to coexist without false identity by label. It does not treat quality-term or evaluative characterization as relation construction by default. When the found problem is relation construction, bridge, basedness, action-invitation relation, endpoint mismatch, or another relation-shaped claim, use A.6.P or the relation named by value specialization.

Placement. Part C > C.16 characterization pattern nest > precision-restoration pattern for overloaded quality and evaluative-characterization wording.

Builds on. E.10, E.10.ARCH, C.16.P, C.16, C.25, E.21, A.17, A.18, A.19, A.7, C.2.1, E.8, F.9, and F.18.

Coordinates with. A.6.P for relation-construction exits; A.6.A for action-invitation exits; C.2.2a, A.16, A.16.1, A.16.2, and B.4.1 for language-state positions, admissible moves, early cues, responsibility handoff, and retreat; A.16.0 only when lineage, branch, loss, or handoff history itself needs an explicit trajectory account; B.5.2.0 for an open explanatory probe; C.2.LS, C.2.4, C.2.5, C.2.6, and C.2.7 for articulation, closure, anchoring, and representation-factor facets; C.2.1 for effective ReferenceScheme, result-episteme identity, and optional empirical grounding; A.2.6 for ClaimScope; A.19.CPM for comparison; E.17.0, E.17, and E.18 for exact viewpoint resolution and publication; A.10 and B.3 for evidence and assurance; F.9 for direct cross-local Bridges and bounded-use claims; F.9.1 only for stance overlays on existing Bridge Cards; A.19.CN for comparability governance; and C.3.3 for explicit kind-bridge repair when endpoint kind mismatches appear.

E.10.ARCH governing-pattern relation. When E.10 encounters quality, good, fit, high-quality, quality metric, quality score, quality characteristic, quality requirement, model quality, architecture quality, solution quality, or evaluative -ility wording whose quality sense, bearer, effective ReferenceScheme, probe/model or comparison configuration, ClaimScope, endpoint normal form, or governing pattern is hidden, E.10.ARCH assigns the repair to C.16.Q only until those values are recovered or the claim exits to C.16.P, C.25, E.21, A.6.P, A.6.A, C.29, A.10, B.3, A.20, A.21, C.11, C.2.P, or another direct governor. C.16.Q does not keep evidence, assurance, gate, decision, work, release, relation, action-invitation, mathematical-lens, source-use, or publication invariants after that exit is recoverable.

Non-goal. This pattern does not assert that phenomenal character or qualia, phenomenological preconceptual fit, Pirsig-style dynamic quality and static quality, latent fit in learned representations, explanatory merit, engineering -ilities, QD and NQD selector value, and control adequacy are one concept. Its job is to publish a disciplined evaluative-characterization use across those traditions while preventing false identity by shared label. It also does not assert that every trigger use of "quality" is admissibly repaired by the transitional quality-term repair form: where the repaired statement is primarily about an action invitation under A.6.A, relation construction under A.6.P, or a requirement or commitment over explicit heads, the admissible move is to exit to the pattern governing the recovered claim rather than assigning a quality-term or evaluative characterization.

Use this pattern when wording such as quality, good, fit, high-quality, quality characteristic, quality improved, or an evaluative -ility claim hides which quality or evaluative-characterization use is live.

#Relations

#Content

#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 which quality or evaluative-characterization use is live.

Lowest sufficient use. Keep ordinary praise or quoted source-local wording ordinary when it carries no FPF-governed use. When the evaluative endpoint is already known, prefer a direct endpoint-governed rewrite. Use qualityTermAscription(...) only when transitional ambiguity must remain inspectable. Its core bearer, scheme, frame, scope, evaluator/viewpoint, and result boundaries stay explicit; add optional witness, evidence, grounding, Bridge, Card, overlay, time, plane, and substrate refs only when those branches are live.

What goes wrong if missed. A broad quality word becomes a scalar verdict, gate, evidence claim, relation, Bridge, action invitation, or bundle by appearance, while the exact bearer, scheme, probe/model configuration, comparison configuration, ClaimScope, quality sense, admissible normal form, and direct governor remain hidden.

What this buys. The reader can recover the exact bearer and interpretation basis, see which probe/model and comparison configurations are active, distinguish evaluator from viewpoint, identify the candidate quality sense and admissible normal form, and take any result, evidence, grounding, Bridge, or relation claim to its direct governor before using the quality word as action guidance.

First useful move. Name the exact bearer, effective ReferenceScheme, probe/model frame, comparison frame or none, and ClaimScope; then choose whether the wording is evaluative characterization, characteristic-scale construction, Q-bundle, pattern-quality coordinate, relation construction, Bridge or stance-overlay use, action invitation, or ordinary prose, and apply the direct governor.

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, use the pattern governing the recovered 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.

#Problem frame

FPF repeatedly encounters a predictable precision failure mode around the token quality:

drafts say:

• “this design has quality”
• “the model quality improved”
• “quality matters before formalisation”
• “quality characteristics”
• “quality in QD and NQD”
• “the world model is higher quality”
• “the explanation is high-quality”

…but the intended meaning is actually one of several different evaluative families, 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 broad evaluative noun hides several non-equivalent evaluative kinds.
• Bearer confusion. The bearer of the evaluation is unclear: record, publication carrier when the carrier itself is 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.

#Problem

How can FPF let working texts keep the communicative convenience of the word quality while preventing category errors when the term crosses:

• phenomenological and epistemological discourse,
• architecture-description fitness discourse and viewpoint-fit discourse,
• representation-learning and neuro-symbolic discourse,
• Popper- and Deutsch-style explanation-and-criticism discourse,
• engineering architecture and quality-characteristic discourse,
• open-ended evolution, NQD, and selection discourse,
• control, world-model, and active-inference discourse,
• ecological affordance discourse, including source-tradition affordance cases that must leave quality-term restoration for A.6.A or another action-invitation governing pattern?

#Forces

• Breadth vs precision. “Quality” is attractive because it is broad; that same breadth makes it unsafe at boundaries.
• 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 term may begin as a felt signal and later become a bundle, proxy set, or objective.

#Solution

Stable repair frame > Sense Family > Slots > Normal Form > Change Lexicon > Guardrails

#Trigger rule

A use of quality is in scope for C.16.Q when any of the following holds:

• the token quality or high-quality or low-quality appears in Tech or normative prose;
• a boundary statement relies on “quality” for admission, selection, explanation, comparison, assurance, or requirement-setting;
• different traditions are compared using the same word quality;
• a draft introduces quality metric, quality score, quality characteristic, quality requirement, model quality, architecture quality, solution quality, or quality in QD without a declared sense;
• the occurrence is intended to carry more than one of: evaluative fit, measurable characteristic, bundle, utility, or optimization objective.

#Operational repair sequence

When the trigger fires, follow the E.10.ARCH recovery order specialized to quality-term or evaluative characterization:

1. Capture the trigger span. Copy the trigger phrase using quality or a red-flag derivative such as high-quality, quality metric, quality characteristic, or model quality.

2. Recover the bearer and publication lane. Name the bearer and the relevant A.7 lane or kind: EntityOfConcern being described, description, episteme or publication face, carrier when the carrier itself is evaluated, pattern, model, policy, explanation, candidate, architecture description, work result, relation, action loop, or ordinary prose.

3. Recover interpretation locality and reconstruct candidates. Recover the effective ReferenceScheme, exact probe/model frame, separate A.19.CPM comparison frame or none, U.ClaimScope, evaluator, and U.ViewpointRef or none. Then enumerate plausible senses and candidate endpoint-governing patterns or exact endpoint source relations. If the occurrence is decision-bearing, publication-bearing, or cross-local, record these alternatives in a short quality-term Candidate-Set Note before selecting the repair.

4. Exit when the claim being made is not quality-term or evaluative characterization. If the occurrence is primarily action invitation, relation construction, bridge, basedness, endpoint mismatch, evidence, assurance, gate, work, decision, causal-use, release, mathematical-lens use, characteristic and scale construction, or source-use, do not assign a QualitySense. Apply A.6.P, A.6.A, C.16.P, C.29, C.2.P, or the pattern governing the recovered claim.

5. Select one explicit quality sense. Pick one QualitySense token and state why rival senses were rejected in this local context.

6. Emit an endpoint-explicit or transitional rewrite. Rewrite the sentence either into one explicit endpoint-pattern-governed evaluative form (Characteristic | Q-Bundle | Objective | ExplanatoryMeritBundle | selector-value endpoint) or, while endpoint choice is still being stabilized, into one explicit qualityTermAscription(...) transitional repair form with exact bearer, effective ReferenceScheme, probe/model and comparison frames, evaluator and U.ViewpointRef, U.ClaimScope, normal form, result boundary, and separate witness/evidence/grounding and cross-local qualifiers.

7. Classify boundary-bearing consequences. If the repaired statement is used for admissibility, commitments, publication, evidence-bearing decisions, gates, release, or work, apply the governing pattern instead of letting quality carry the required claim by itself.

#Transitional repair frame: evaluative classification anchored by qualityTermAscription(...)

C.16.Q stabilizes the ambiguity cluster by treating every in-scope quality statement as explicit evaluative content under one effective ReferenceScheme and named direct endpoint governor, not as a bare adjective, generic context field, or evidence-bearing result by implication.

qualityTermAscription(...) is the canonical transitional quality-term repair form when the endpoint choice is not yet fixed. It is not the universal resting place, not a relation kind by default, and not a shadow endpoint source.

Entry into C.16.Q presupposes enough articulation explicitness to name the bearer, effective scheme, probe/model frame, comparison frame or explicit none, ClaimScope, and at least one candidate evaluative 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 exact neighboring result or reliance claim they bear on.

The transitional form is:

qualityTermAscription :=
{
  bearerTuple: exact bearer designator(s),
  qualitySense: QualitySense,
  effectiveReferenceScheme: U.ReferenceScheme,
  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?,
  representationSchemeRef?: U.RepresentationScheme ref,
  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,
  bridgeCardRef?: exact F.9 Bridge Card ref | none,
  bridgeStanceOverlayRef?: exact F.9.1 overlay ref | none,
  endpointGoverningPatternRef?: exact direct pattern ref,
  endpointSourceRelationRef?: exact direct source or publication relation ref,
  admissibleUse,
  nonAdmissibleUse
}

effectiveReferenceScheme, probeOrModelFrameRef, comparisonFrameRef, and claimScope are explicit even when the comparison value is none; no generic context or frame slot owns their semantics. A probe or model frame remains the exact domain-local probe/model configuration. A comparison frame resolves the applicable CG-Spec, comparator edition, comparison scope, reference plane, and interval under A.19.CPM; it is not a universal Frame kind.

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, Card, or F.9.1 overlay only when each independently exists. At least one of endpointGoverningPatternRef and endpointSourceRelationRef is required.

So the sentence "X has quality" is never accepted as a terminal form. It must be rewritten either into an explicit endpoint-pattern-governed evaluative form or into this transitional repair form with its interpretation-bearing and neighboring-object boundaries declared.

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 what kind of evaluative characterization is being made while the endpoint source, governing 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.

#Polarity discipline (bearer-centred; no silent inverse)

qualityTermAscription is bearer-centred. Tech and normative prose SHALL keep the evaluated participant in the bearer position and SHALL publish evaluatorRef and governed viewpointRef separately, using none when either is absent.

• “Architects rate the system highly” rewrites to qualityTermAscription(bearerTuple={System}, evaluatorRef=ArchitectureReviewBoard, viewpointRef=none, …).
• “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, the wording SHALL be rewritten into the bearer-centred form (or publish an explicit inverse form under the pattern governing the recovered claim that governs it).

#Endpoint-first discipline

When the admissible endpoint-governing FPF pattern or explicit endpoint source reference is already known, the endpoint-pattern-governed evaluative form SHOULD be published directly, and qualityTermAscription(...) SHOULD remain only when preserving the transitional ambiguity is itself informative. qualityTermAscription(...) is therefore a transitional characterization record, not a shadow endpoint source.

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.

#Core construct: QualitySense

Every in-scope use SHALL resolve to an explicit QualitySense token.

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 evaluative normal forms for the sense. defaultNormalForm names the primary evaluative 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 a separate A.19.CPM comparison configuration must be named. bridgePolicy can require F.9 recovery or forbid silent reuse, but it cannot establish a Bridge. If the quality ascription is published, route publication face, form, unit, carrier, and rendering questions to E.17, E.8, or the publication pattern governing the claim.

#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:

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.

#Required slots for a conforming qualityTermAscription

A conforming qualityTermAscription SHALL make explicit:

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

2. QualitySense. Name the intended evaluative family.

3. Effective ReferenceScheme. State the effective U.ReferenceScheme by value so every designator and local sense in the ascription is interpretable. A generic context label or a representation scheme is not a substitute.

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. Name the exact A.19.CPM-governed comparison configuration separately, including the effective comparator and comparison scope when a comparison is made. Publish none when the ascription proposes no comparison; do not let the probe/model frame silently select one.

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. Freshness, qualification, and evidence-decay windows remain in their exact evidence, capability, or currentness lanes rather than being smuggled into 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 scheme and substrate when relevant. Keep the effective reference scheme distinct from any representation scheme, viewpoint-specific decoding convention, or embodied-kinesthetic, latent-distributed, symbolic-local, or hybrid substrate. Name each when omission changes interpretation.

11. Witnesses, evidence use, and empirical grounding. Name exact exemplars, probes, measurements, bundle members, tests, traces, closed-loop performance carriers, or other witnesses. If an evidence-provenance path is relied on, cite its exact direct relations under A.10. 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 only when it obtains, and cite a Card or F.9.1 stance overlay only when independently present. State an exact endpoint-governing pattern or endpoint source relation, the admissible use, and nearest non-admissible use rather than letting quality or a stance token carry them.

#Normal-form discipline

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

The normal forms in this section are endpoint or evaluative forms. 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 endpoint-governing publication pattern named by value.

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,
• explicit warning that the signal is not yet a Characteristic unless an admissible proxy is later declared.

QNF-2 - Characteristic. Use only when the sense is truly 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.

#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 named by value, relation, or claim, then the pattern governing the recovered capability, method, work, role, A.6.M module-interface, architecture, mathematical, evidence, assurance, gate, decision, or release claim whose primary EntityOfConcern, bearer, relation record, or characteristic-space construction is recovered.
• A statement about how well, how safely, how robustly, or how maintainably it does so belongs to 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.

#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 two quality senses have different interpretation bases, first resolve both exact F.17 SchemeSenseCell values and test the direct F.9 Bridge predicate. Scheme difference, shared spelling, an analogy, a loss note, or a quality record establishes no Bridge.

If the Bridge obtains, cite its exact occurrence. State any proposed comparison, substitution, operationalization, or projection as a separate F.9 bounded-use claim with direction, rule, tolerance, polarity, and effective ReferenceScheme; then apply A.10 or B.3 only for the reliance branch that is actually live. A Bridge Card remains optional reusable packaging. Only when such a Card already exists and a compact interpretive gloss has practical value may C.16.Q cite one F.9.1 stance overlay:

• localRename — read the card as near-renaming within its declared local boundary; it does not establish cross-local identity.
• operationalizes — read the target as a procedural or measurable aid over the Bridge; it does not establish work, implementation, permission, or use suitability.
• partialAnalogy — read the declared correspondence as partial; it does not license substitution.
• projection — read the target as a deliberate reduction of the source reading; the separate bounded-use claim carries its rule and tolerated loss.
• nonEquivalent — block equivalence and silent substitution; the overlay alone does not assert Disjoint, a negative obtaining claim, or an evidence score.

These tokens are F.9.1 annotations over an existing Card, not Bridge kinds, direct relations, result claims, or substitutes for loss notes and bounded-use claims.

Examples:

• QS.PreconceptualFit and QS.LatentFit are usually only candidates for partial correspondence. If their exact F.17 cells are cross-local, test an F.9 kind such as Partial-overlap; do not infer identity from the partialAnalogy gloss.
• 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.
• Using QS.PreconceptualFit to choose engineering measures is a proposed operationalization or projection use. Name the actual Bridge, the separate use rule and loss tolerance, and the direct measurement or characterization result.
• Relating QS.EngineeringQualityFamily to QS.UseValue is normally a directional, loss-bearing proposed use under a declared CG-frame, not identity and not permission to substitute one score for the other.
• QS.ExplanatoryMerit and QS.UseValue remain non-identical unless an exact F.9 Bridge obtains; an F.9.1 nonEquivalent overlay may help read an existing Card but cannot replace the Bridge finding.
• Pirsig-style dynamic quality may locally cue QS.PreconceptualFit or sometimes QS.LatentFit. Within one exact interpretation basis this may be a local rename; across bases it needs exact F.17 cells and F.9 treatment. 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, and losses separate and must name which description-fitness heads, if any, are proposed to proxy which system-side characteristics.

#Change lexicon

A conforming quality-term repair publication SHALL narrate changes with a stable change lexicon aligned to A.6.P:

• declareQualityTermAscription(...) — create a new explicit quality-ascription record.
• withdrawQualityTermAscription(...) — retire a prior record.
• retargetBearer(...) — retarget the evaluated 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 without manufacturing 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 Card, overlay, or bounded-use claim by implication.
• assignToGoverningPattern(...) — make a semantic move to a non-quality governing pattern; never edit in place silently.

A silent sense rewrite is a breaking semantic change. If the ascription ceases to mean “quality ascription” at all, use assignToGoverningPattern(...) rather than pretending the same record survived unchanged.

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, Card, and overlay refs change independently; no edit silently rewrites another.

#A.6.B boundary classification template for quality-term repair

When a repaired quality statement becomes boundary-bearing, classify it explicitly:

• L — qualityTermAscription repair-form skeleton, QualitySense semantics, normal-form admissibility, cross-local routing, and the rule that any F.9.1 stance remains an optional overlay over an existing Bridge Card;
• 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.

#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; the text SHALL rewrite them into explicit requirement-use, source-use, gate, commitment, acceptance-spec, characteristic, Q-Bundle, objective, or publication-use claims or relations named by their direct governing patterns over one named U.Characteristic, one Q-Bundle head, or one explicit 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, episteme or 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; it SHALL exit to A.6.A or another action-invitation governing pattern, 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.

#Progressive elaboration

C.16.Q permits monotone elaboration:

1. Select a QualitySense and retain rival candidates while ambiguity is live.
2. Name the exact bearer, effective ReferenceScheme, U.ClaimScope, and any meaning-changing Γ_time, reference plane, representation scheme, or substrate.
3. Name the probe or model frame and the separate comparison frame or explicit none; 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 cross-local correspondence is live, resolve exact F.17 cells and F.9 Bridge truth before adding an optional Card or F.9.1 stance overlay; keep the bounded-use claim separate.
7. If the repaired sentence is boundary-bearing, emit L/A/D/E hooks rather than letting quality carry them implicitly.
8. Never move between sense families, frames, schemes, scopes, result claims, or neighboring relations silently.

#Archetypal Grounding

#Tell

If a draft says quality, the draft has not yet named the evaluative family. A conforming rewrite publishes either one explicit endpoint-pattern-governed evaluative form or one explicit qualityTermAscription(...) transitional record with exact bearer, one QualitySense, effective ReferenceScheme, separate probe/model and comparison frames, evaluator and U.ViewpointRef, ClaimScope, admissible normal form, exact endpoint-governing pattern or endpoint source relation, and explicit boundaries among result claim, witnesses, evidence use, empirical grounding, Bridge, Card, and stance overlay.

#Show (System lane)

The identifiers below denote distinct objects. Each comparisonFrameRef resolves its exact A.19.CPM configuration; 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.

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}), Γ_time = Window_W5, qualityResultClaimRef = LatentFitResultClaim_22, witnessRefs = {ProbeSeparationRun_22, AliasRiskCard_9}, evidenceProvenancePathRefs = {LatentFitEvidencePath_22}, empiricalGroundingRelationRef = EGR_LatentFitResult_22, endpointGoverningPatternRef = C.16 )

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}), Γ_time = RunWindow_RW, qualityResultClaimRef = ControlAdequacyResultClaim_41, witnessRefs = {ClosedLoopTraceSet_41}, evidenceProvenancePathRefs = {ControlEvidencePath_41}, empiricalGroundingRelationRef = EGR_ControlAdequacyResult_41, endpointGoverningPatternRef = C.25 )

#Show (Episteme lane)

Draft: “Quality matters before definition.”

Repair A — preconceptual or phenomenological line qualityTermAscription( bearerTuple = {ProblemFramingEpisode_PF3}, qualitySense = QS.PreconceptualFit, effectiveReferenceScheme = FeltFitArticulationScheme_3, probeOrModelFrameRef = ExemplarPack_EP3, comparisonFrameRef = ExemplarContrastFrame_ECF3, 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, endpointGoverningPatternRef = A.16.1 )

The explicit none values matter: episode notes are witnesses to articulation, not automatic provenance or empirical grounding.

Repair B — explanatory line qualityTermAscription( bearerTuple = {Explanation_N5}, qualitySense = QS.ExplanatoryMerit, effectiveReferenceScheme = ExplanationCriticismScheme_5, probeOrModelFrameRef = CriticismBundle_CB4, comparisonFrameRef = RivalExplanationComparison_CF4, 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, endpointGoverningPatternRef = C.25 )

#Show (Architecture description lane)

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 = TEVB_ArchitectureViewpointRef, 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, endpointGoverningPatternRef = C.25 )

Repair B — quality of the architecture description qualityTermAscription( bearerTuple = {ArchitectureDescription_AD12}, qualitySense = QS.ArchitecturalDescriptionFitness, effectiveReferenceScheme = ArchitectureDescriptionFitnessScheme_12, probeOrModelFrameRef = ViewpointBundle_TEVB × DecisionQuestionSet_DQ7, comparisonFrameRef = DescriptionEditionComparison_CF12, evaluatorRef = ArchitectureReviewBoard, viewpointRef = TEVB_ArchitectureViewpointRef, referencePlane = episteme, normalForm = Bundle, claimScope = U.ClaimScope({ArchitectureDescriptionReviewSlice_AD12}), qualityResultClaimRef = DescriptionFitnessResultClaim_7, witnessRefs = {CoverageMatrix_4, CorrespondenceCheck_7, ViewConsistencyNote_2}, evidenceProvenancePathRefs = {DescriptionFitnessEvidencePath_7}, empiricalGroundingRelationRef = none, endpointGoverningPatternRef = E.17.2 )

The shared evaluator and viewpoint reference do not collapse the two repairs: their exact bearers, schemes, frames, scopes, result claims, and evidence paths differ.

#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 = ArchiveComparatorFrame_9, evaluatorRef = SelectorPolicy_P4, viewpointRef = none, normalForm = Objective, claimScope = U.ClaimScope({QDSelectionSlice_9}), Γ_time = SelectionWindow_SW, qualityResultClaimRef = UseValueResultClaim_9, witnessRefs = {ObjectiveCard_9, AcceptanceSpec_4}, evidenceProvenancePathRefs = {QDSelectionEvidencePath_9}, empiricalGroundingRelationRef = none, endpointGoverningPatternRef = C.17 )

#Bias-Annotation

Lenses tested: Gov, Arch, Onto-Epist, Prag, Did. Scope: Universal for 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: this pattern prefers one stable transitional ascription record over free-form philosophical prose, which improves reuse but can feel rigid in exploratory notes.
• Onto-Epist bias: this pattern refuses to collapse preconceptual, latent, explanatory, engineering, and selector senses into one concept; that increases honesty at the cost of 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 is intentionally teachable through repeated rewrites; the risk is over-formalizing early exploratory language.

#Conformance Checklist (CC-C16Q)

A text or pattern conforms to C.16.Q iff:

1. CC-C16Q-1 - Explicit endpoint classification and explicit sense. Every in-scope use resolves either to one declared endpoint-pattern-governed evaluative form or to one declared qualityTermAscription(...) transitional record with a QualitySense and explicit endpoint classification.
2. CC-C16Q-2 - Exact bearer and arity. The evaluated 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. The domain-local probe or model frame and the separately governed comparison frame or explicit none are stated and reviewable; neither is a generic semantic-owner field.
4. CC-C16Q-4 - Effective scheme, evaluator, and viewpoint reference. The effective U.ReferenceScheme 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 between preconceptual, latent-distributed, symbolic-local, and ReferencePlane values world, concept, and episteme is not allowed without explicit substrate and, when live, 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 uses the declared change lexicon; changing sense, scheme, frame, scope, or neighboring relation silently is forbidden.
10. CC-C16Q-10 - QD default. In search, selection, or NQD practice, quality resolves to QS.UseValue unless overridden explicitly.
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. Cross-local comparison resolves exact F.17 cells and cites an obtaining F.9 Bridge. Any bounded-use claim, optional Card, and F.9.1 overlay remain separate; a stance, CL, shared label, or loss note establishes none of them.
14. CC-C16Q-14 - Boundary-claim hook when needed. If a repaired ascription is used for admissibility, commitment, publication, evidence-bearing decision, or adjudication, the downstream L/A/D/E claims and direct governors are explicit.
15. CC-C16Q-15 - Lexical firewall. Bare quality is absent from Tech and normative prose except as quoted and marked metalinguistic discussion.
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 - Candidate-Set Note is used when ambiguity is live. If sense selection, bearer facet, or A.7 lane or kind (EntityOfConcern being described, description, episteme or publication face, or carrier when the carrier itself is evaluated) is non-obvious, the text records a short Candidate-Set Note before decision-bearing or publication-bearing use.
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 use their declared verbs; a scheme or scope change triggers claim-identity review; edits to witnesses, evidence paths, grounding, Bridge, Card, or overlay refs do not silently rewrite one another; and silent retyping is forbidden.

#Common Anti-Patterns and How to Avoid Them

#Consequences

Benefits. This pattern makes evaluative language auditable across phenomenology, engineering, and search and selection contexts. It also makes subsequent wording repair easier because the repair is carried by one explicit quality-term repair form plus endpoint governing-pattern assignments rather than by ad hoc prose rules.

Trade-offs and mitigations. The pattern adds drafting overhead and can feel heavy in exploratory notes. Mitigation: allow bare quality in Plain commentary during exploration, but require repair before the term enters Tech and normative, boundary, selector, or assurance use.

#Rationale

C.16.Q makes one strategic move:

The word “quality” is not treated as one concept. It is treated as a family of evaluative ascriptions whose members differ by substrate, articulation mode, bearer, effective scheme, probe/model configuration, comparison configuration, ClaimScope, and admissible publication 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 false 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.

That is exactly where semantic drift usually starts; C.16.Q turns that drift into an auditable design choice.

#SoTA-Echoing

Evidence binding note. If the selected authoring environment maintains a SoTA Synthesis Pack for evaluative language, architecture-quality vocabularies, selector and objective semantics, world-model evaluation, or embodied and preconceptual articulation, this section SHALL cite its ClaimSheet IDs, CorpusLedger entries, and BridgeMatrix rows and keep the adoption statuses below consistent with those IDs. Otherwise, use the table below as the current source-use and source-currentness record for this pattern revision, not as a generic seed list.

This section follows the required structure: claim > practice > source use and currentness > source > alignment > adoption status. C.16.Q aligns with contemporary practice across architecture-description standards, software-quality standards, evolutionary architecture, QD search, active-inference and world-model research, phenomenology and TAE, source-tradition affordance work, and philosophy of explanation, while adding one explicit FPF move: the overloaded token quality is repaired into direct endpoint forms, with qualityTermAscription(...) available as a transitional record carrying exact bearer, QualitySense, effective scheme, separate probe/model and comparison configurations, ClaimScope, admissible normal form, and direct-owner refs while endpoint assignment remains open.

Source-use convention. Current-best source use means the row is used as the best-known current line for the narrow effect named in the alignment cell. Current-standard and reference-only use means an official standard supplies a useful distinction but does not by itself solve C.16.Q's quality-term restoration question. Current-practice reference use means the source family records a widely used current practice that C.16.Q adapts. Lineage and local-gloss material means the row helps recognition or terminology only. Rejected import states what C.16.Q refuses to import as FPF ontology.

Short alignment notes.

Architecture-description practice. ISO 42010 is a current-standard reference for not collapsing the selected system or other entity under description into its description. C.16.Q adopts that guardrail and adds lexical discipline: a draft may not say architecture quality without publishing which bearer lane is under evaluation and whether the evaluation is description-side or system-side.

Engineering quality practice. ISO 25010 gives a mainstream current-standard reason not to leave quality as a free noun: contemporary quality work is organized around named characteristics and subcharacteristics that are specified, measured, and evaluated. C.16.Q adopts that explicit-head discipline, but adapts it by assigning composite cases to Bundle or Q-Bundle and by treating quality requirement(s) as requirements over explicit heads rather than as self-standing nouns.

Evolutionary-architecture practice. Fitness functions treat architecture-relevant concerns as continuously monitored heads tied to change and governance, not as one mystical scalar. C.16.Q adopts that operational spirit, but adapts it by keeping engineering-family evaluation, control adequacy, and selector value distinct and by forbidding function and quality-family collapse.

QD and NQD practice. Modern QD work is explicit that search returns a collection of solutions that are high with respect to an objective and diverse with respect to declared measures. C.16.Q therefore adopts the default rewrite of selector-context quality to QS.UseValue in Objective form and rejects any rewrite that silently blends novelty, diversity, constraints, and utility into an unexplained scalar.

World-model and active-inference practice. Contemporary world-model and active-inference work uses generative and predictive models for perception, planning, learning, and action, which makes evaluation inherently multi-factor: latent representation quality, model evidence or predictive adequacy, policy adequacy, and task and objective value are not one thing. C.16.Q adapts this by separating QS.LatentFit, QS.ControlAdequacy, and QS.UseValue, and by requiring effective schemes, separate probe/model and comparison configurations, ClaimScopes, and witnesses for each ascription.

Phenomenology and TAE practice. TAE-style work treats a felt sense as something that can be clarified and worded progressively, with tentative language that stays responsive to lived experience. C.16.Q adopts this progressive-articulation stance by giving QS.PreconceptualFit an admissible SignalPack form and by keeping QS.PhenomenalCharacter separately available when the experienced character itself, not action-guiding fit, is the topic.

Action-invitation boundary. Recent source-tradition affordance work emphasizes that affordances can be perceptually experienced as action possibilities that position or invite the agent to act. C.16.Q uses that insight only as a governing-pattern boundary cue: when the trigger use of quality is really action-invitation talk, the text should use assignToGoverningPattern(...) into A.6.A or another action-invitation governing pattern rather than forcing a QualitySense or qualityTermAscription(...).

Explanation practice. Contemporary philosophy of explanation keeps explanatory understanding and epistemic value distinct from engineering performance or utility maximization. C.16.Q adapts this by publishing QS.ExplanatoryMerit as its own evaluative family, typically Bundle-shaped, and by rejecting hidden scalarization into “high-quality explanation” without explicit heads.

Scale legality. The rows above do not license free arithmetic on the word quality. Whenever C.16.Q operationalizes engineering heads, selector objectives, or control adequacy numerically, it SHALL bind the comparison to an explicit ComparatorSet, CG-Spec, or declared aggregation policy and SHALL reject covert scalarization of bundles, explanations, or preconceptual signals.

Cross-local and plane note. This section states alignment and non-identity only. Any actual reuse of a quality vocabulary, selector head, or viewpoint-bound family across different <ReferenceScheme, LocalSenseClaim> bases SHALL resolve two exact F.17 cells and cite an obtaining F.9 Bridge. The proposed use, direction, rule, tolerated loss, polarity, evidence reliance, and any cross-plane representation relation remain separately governed; a stance overlay, CL, loss note, shared label, or plane policy makes none of them obtain.

Historical-lineage note. Earlier touchstones such as Pirsig, Popper, and Deutsch remain useful as lineage and local-gloss resources, but C.16.Q does not use them as formal SoTA anchors here because E.8 requires post-2015 primary sources for Architectural patterns unless the row is explicitly lineage or local-gloss material.

This SoTA alignment backs the pattern’s central move: quality is not one universal evaluative noun. In contemporary practice, the relevant work is already distributed across explicit characteristics, objectives, viewpoints, world-model criteria, explanatory virtues, felt signals, and action invitations; C.16.Q makes that distribution first-class and auditable.

#Refresh and reopen conditions

Reopen or narrow C.16.Q when any of these current-pattern-language conditions becomes live:

• a recurring quality or evaluative family appears that is not covered by the current QualitySense starter set and cannot be treated as an existing endpoint-pattern-governed form;
• a new endpoint governing pattern can govern a class of uses that currently require transitional qualityTermAscription(...);
• A.7, C.2.P, C.2.1, or bridge-policy vocabulary changes the admissible lane, EntityOfConcern, publication-face, carrier, or ReferencePlane wording used by this pattern;
• current best-known practice changes a QualitySense, normal-form boundary, action-invitation boundary, scale-legality boundary, or source-use and currentness row used in C.16.Q:11;
• README, ToC, E.11, retrieval, or local Problem-frame first-entry cues change for quality, characteristic, action-invitation, architecture-description, selector, or explanation wording;
• subject patterns begin copying quality trigger lists, QualitySense rows, or transitional repair-form slots that belong in this first-stage quality-term precision-restoration pattern.

The refresh action is to remove, narrow, or redirect the affected row or exit. Do not preserve a stale QualitySense, endpoint exit, lane wording, or source row as historical compatibility text.

#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 or another action-invitation governor when the trigger invites action; 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, responsibility handoff, and retreat or reopen; use A.16.0 only when lineage, branch, loss, or 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 facet governance; 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 comparison; 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, U.ViewpointRef, and architecture-description use; F.9 for exact cross-local Bridge occurrences and bounded-use claims; F.9.1 only for stance overlays over an existing Bridge Card; and A.6.B when repaired ascriptions become boundary-bearing.
• 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.

#Language-space refactor note

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.

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

Bare quality in Tech prose should therefore be banned or rewritten immediately under an explicit endpoint-governing FPF pattern or explicit endpoint source reference. If that endpoint source is already known, qualityTermAscription(...) need not remain in the published normal form.

#Endpoint-governance boundary

This pattern does not govern articulation-state characteristics, direct Bridge truth, stance-overlay identity, evidence-provenance, empirical grounding, comparison operations, viewpoint resolution, or representation factors. Those remain governed by 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, and the exact representation pattern.

#C.16.Q:End

Last Updated: 2026-08-04 — upstream FPF commit 67092138 (github.com/ailev/FPF)