#Characteristic and Scale Precision Restoration

C.16.P · 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. Characteristic-scale wording repair.

Intent. Recover characteristic, scale, coordinate, score, metric, indicator, threshold, comparison, and scalar-quality wording whose construction is hidden before a reader applies C.16, A.17, A.18, A.19, C.25, C.29, E.21, or another governing pattern.

This pattern is not a metrics-only pattern, not a measurement-method replacement, not a Q-bundle pattern, and not a gate or decision pattern. It repairs overloaded characterization wording so the exact Characteristic, Scale, Coordinate, Value, Score, Unit, ScoringMethod, indicator role, comparison reference or comparator set, proxy role, admissible use, and governing pattern become recoverable.

Builds on. E.10, E.10.ARCH, A.17, A.18, C.16, A.19, C.25, C.29, E.21, F.18, and A.6.P.

Coordinates with. C.16.Q, A.19.ECS, CHR mechanism patterns, G.0, G.5, G.9, C.11, A.10, B.3, A.20, A.21, C.28, A.15, evidence, assurance, gate, decision, causal-use, release, work, benchmark, and publication patterns governing those claims.

E.10.ARCH governing relation. When E.10 encounters metric, score, axis, dimension, feature, property, indicator, strong, weak, robust, level, coordinate, threshold, benchmark, or scalar-quality wording whose characteristic and scale construction is hidden, E.10.ARCH selects C.16.P only until bearer, characteristic, scale, value or score construction, comparison reference or comparator set, threshold rule or reference, proxy relation, admissible use, and governing pattern are recovered. After that recovery, the governing pattern governs its own invariant.

Use this pattern when wording such as axis, dimension, feature, property, metric, indicator, score, strong, weak, robust, level, coordinate, threshold, rating, benchmark, quality coordinate, or architecture score carries a characterization claim but does not yet show the recoverable construction.

#Relations

#Content

#Use this when

Use this pattern when wording such as axis, dimension, feature, property, metric, indicator, score, strong, weak, robust, level, coordinate, threshold, rating, benchmark, quality coordinate, or architecture score carries a characterization claim but does not yet show the recoverable construction.

What goes wrong if missed. A metric becomes a measure without a scale, a score becomes proof, strong becomes a verdict without a characteristic, a level becomes an undefined maturity status, an indicator becomes the thing indicated, or a benchmark result becomes gate passage or release permission.

What this buys. The reader can recover the bearer, characteristic, scale, value, score, unit, scoring method, indicator role, comparison reference or comparator set, threshold, admissible use, and governing pattern before treating a number, adjective, coordinate, or comparison as actionable.

First useful move. Ask which bearer, characteristic, scale, value or score construction is recoverable; then apply C.16, A.19, C.25, C.29, E.21, or the neighboring pattern governing that claim instead of letting the compact word decide.

Not this pattern when.

• If the Characteristic, Scale, value set, scoring method, and admissible use are already recoverable, use C.16, A.17, A.18, or A.19 directly.
• If the claim being made is a Q-bundle, quality-term or evaluative characterization, or pattern-quality coordinate, use C.25, C.16.Q, or E.21 directly after any needed characteristic-scale repair.
• If the claim being made is mathematical-lens use, use C.29.
• If the claim being made is evidence, assurance, gate, work, decision, causal-use, release, benchmark harness, or project-side authority claim, use the governing pattern for that claim after characteristic and scale construction is recovered or blocked.

#Problem frame

Working texts often need compact characterization words. The problem starts when compact words begin to carry comparison, proof, selection, gate, readiness, release, quality, or decision claim without recoverable characteristic and scale construction.

The repair question is:

What characteristic or scale construction is recoverable, and what governing pattern carries the remaining claim?

The recoverable item may be:

• a Characteristic under A.17;
• a Scale, coordinate, value, unit, scoring method, measure, or measurement use under A.18 and C.16;
• a CharacteristicSpace under A.19;
• a Q-bundle under C.25;
• quality-term or evaluative characterization under C.16.Q;
• pattern-quality coordinate use under E.21;
• mathematical-lens use under C.29;
• comparison, threshold, indicator, proxy, benchmark, gate, evidence, decision, or work claim under neighboring patterns governing those claims;
• ordinary prose with no FPF-governed use.

#Problem

How can FPF repair characterization wording without:

• treating metric as a universal measurement kind;
• treating score as proof, readiness, gate passage, release permission, or decision;
• treating axis, dimension, feature, property, or level as a recoverable characteristic by appearance;
• treating strong, weak, robust, high, low, or better as meaningful without a scale and comparison reference or comparator set;
• turning C.16.P into a CHR super-pattern or replacement for C.16, A.17, A.18, A.19, C.25, C.29, or E.21;
• copying first-stage characterization repair lists into every governing pattern.

#Forces

#Solution

Repair compressed characterization wording by producing a characteristic-scale repair note or equivalent local rewrite.

Minimum fields:

CharacteristicScaleRepairNote:
  triggerSpan:
  boundedTextSpanOrPublicationUnit:
  bearer:
  candidateConstruction:
  recoveredCharacteristic?:
  recoveredScale?:
  recoveredCoordinate?:
  recoveredValue?:
  recoveredScore?:
  unit?:
  scoringMethod?:
  indicatorRole?:
  comparisonReferenceOrComparatorSet?:
  thresholdRuleOrReference?:
  proxyDistortionRisk?:
  governingPatternRef:
  repairedWordingOrDemotion:
  admissibleUse:
  nonAdmissibleUse:
  remainingReaderUse:
  disposition:

Use the full note only when the repair must remain inspectable. Use a local rewrite when one sentence clearly states the characteristic and scale construction and governing pattern.

#Recovery sequence

1. Capture the trigger. Copy the exact word or phrase and the sentence that uses it.
2. Recover the bearer. Name what is being characterized: holon, pattern, design-rationale record, architecture description, structure, model, method, work result, publication, candidate, relation, decision option, evidence relation, or another FPF kind named by value.
3. Recover the construction. Decide whether the trigger means Characteristic, Scale, coordinate, value, score, unit, scoring method, indicator, threshold, comparison reference or comparator set, proxy, Q-bundle, mathematical lens, gate, evidence, decision, or ordinary prose.
4. Select direct governing pattern when possible. If C.16, A.17, A.18, A.19, C.25, C.29, E.21, or another governing pattern is already recoverable, use it directly.
5. Repair hidden characteristic and scale construction. When construction is hidden, recover the minimal needed set: characteristic, scale, value set, score, unit, scoring method, indicator role, comparison reference or comparator set, threshold rule or reference, admissible use, and non-admissible use.
6. Separate adjacent claims. Evidence, assurance, gate, work, decision, causal-use, release, benchmark, publication, or authority claims are governed by their direct patterns.
7. State remaining reader use. Say what the reader can now compare, measure, score, block, or assign to a neighboring pattern. If the result is type-correct but gives no action or recognition reason, the repair is incomplete.

#Trigger split

#Adjacent Claim Governance Named by Value

#Refresh and reopen conditions

Reopen or narrow C.16.P when current pattern-language ecology changes the first characteristic and scale entry:

• a new characteristic named by value, scale, evaluation, benchmark, proxy or indicator, gate or decision, mathematical-lens, quality, OEE, NQD, or publication pattern can receive one row directly;
• current best-known practice changes comparability, proxy-risk, threshold, measurement, scoring-method, or benchmark-harness discipline adopted in the SoTA-Echoing section;
• README, ToC, E.11, retrieval, or local Problem-frame entry cues change the first practical entry for hidden characteristic and scale wording;
• a governing pattern starts copying first-stage metric, score, axis, strong, or indicator trigger lists that belong here;
• C.16.P begins to act as a metrics catalog, maturity scheme, or CHR super-pattern rather than a wording-use repair pattern for hidden construction.

The refresh action is to remove, narrow, or reassign the first-stage row. It is not to preserve stale routing language as history.

#Archetypal Grounding - Worked cases

#Bias-Annotation

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

Benefits. C.16.P gives a first-stage repair point for overloaded characterization words, so receiving patterns do not need to copy long trigger lists. It makes the next governing pattern visible before a number, adjective, level, score, metric, or benchmark result is treated as actionable.

Trade-offs. Some compact phrases become longer because the bearer, characteristic, scale, threshold, proxy, or governing pattern must be named. The gain is that measurement, quality, mathematical-lens, evidence, assurance, gate, decision, and causal-use claims do not hide inside one scalar word.

Stop condition. Stop using C.16.P once the characteristic-scale construction and the governing pattern are recoverable. The repaired claim then belongs to C.16, A.17, A.18, A.19, C.25, C.29, E.21, or the neighboring pattern named by value.

#Rationale

The rationale for C.16.P is narrow: compact characterization wording is useful, but FPF cannot let compact words decide the kind of claim. The pattern restores the bearer, characteristic, scale, value or score construction, proxy relation, threshold rule, admissible use, and governing pattern before the text is allowed to support measurement, comparison, assurance, gate, decision, causal-use, benchmark, or mathematical-lens work.

#SoTA-Echoing

Current measurement, quality, proxy-risk, and comparison practice distinguishes characteristics, scales, measures, scores, indicators, thresholds, comparability, proxy status, and decision use. FPF adopts this line only where it changes examples, non-comparability boundaries, indicator and proxy boundaries, scale and scoring method fields, gate and comparison exits, or conformance checks.

This row blocks scalar verdicts without declared scale and admissible use. It does not import metric lists, maturity-status schemes, or external scoring traditions as FPF ontology.

#Relations

• E.10 catches hidden characteristic and scale wording and selects this pattern only when construction is hidden.
• E.10.ARCH defines the shared wording-use recovery order and applicability row.
• A.17, A.18, and C.16 govern characteristics, scales, values, measures, and measurement use.
• A.19 governs characteristic-space construction.
• C.25 governs Q-bundles.
• C.16.Q governs quality-term or evaluative characterization wording.
• E.21 governs pattern-quality evaluation characteristic spaces.
• C.29 governs mathematical-lens use.
• Exact evidence, assurance, gate, work, decision, causal-use, release, benchmark, and publication patterns govern their own claims.

#C.16.P:End

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