#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 exact receiving 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 basis, proxy role, admissible use, and receiving 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, exact evidence, assurance, gate, decision, causal-use, release, work, benchmark, and publication patterns.

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 characterization force 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 characterization force 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 basis, threshold, admissible use, and exact receiving 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 exact neighboring pattern 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 live claim is a Q-bundle, quality/evaluative characterization, or pattern-quality coordinate, use C.25, C.16.Q, or E.21 directly after any needed characteristic-scale repair.
• If the live claim is mathematical-lens adequacy, use C.29.
• If the live claim is evidence, assurance, gate, work, decision, causal-use, release, benchmark harness, or project authority, use the exact pattern for that claim after characteristic/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 force without recoverable characteristic and scale construction.

The repair question is:

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

The live object may be:

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

#Problem

How can FPF repair characterization wording without:

• treating metric as a universal measurement object;
• 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 basis;
• 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 receiving 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?:
  comparisonBasis?:
  thresholdBasis?:
  proxyDistortionRisk?:
  exactReceivingPattern:
  repairedWordingOrDemotion:
  admissibleUse:
  nonAdmissibleUse:
  remainingReaderMove:
  disposition:

Use the full note only when the repair must remain inspectable. Use a local rewrite when one sentence clearly states the characteristic/scale construction and exact receiving 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, DRR, architecture description, structure, model, method, work result, publication, candidate, relation, decision option, evidence path, or another exact FPF kind.
3. Recover the construction. Decide whether the trigger means Characteristic, Scale, coordinate, value, score, unit, scoring method, indicator, threshold, comparison basis, proxy, Q-bundle, mathematical lens, gate, evidence, decision, or ordinary prose.
4. Select direct exact pattern when possible. If C.16, A.17, A.18, A.19, C.25, C.29, E.21, or another exact pattern is already recoverable, use it directly.
5. Repair hidden characteristic/scale construction. When construction is hidden, recover the minimal needed set: characteristic, scale, value set, score, unit, scoring method, indicator role, comparison basis, threshold basis, admissible use, and non-admissible use.
6. Exit adjacent claims. Evidence, assurance, gate, work, decision, causal-use, release, benchmark, publication, or authority claims go to exact receiving patterns.
7. State remaining reader move. 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

#Exact receiving-pattern exits

#Refresh and reopen conditions

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

• a new exact characteristic, scale, evaluation, benchmark, proxy/indicator, gate/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 C.16.P:8;
• J.4 entry projection changes the first practical entry for hidden characteristic/scale wording;
• a receiving pattern starts copying first-stage metric/score/axis/strong/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 redirect the first-stage row. It is not to preserve old exits as history.

#Worked cases

#Reduced SoTA row

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/proxy boundaries, scale and scoring method fields, gate/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.

#Conformance checklist

#Common anti-patterns

#Related patterns

• E.10 catches hidden characteristic/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/evaluative characterization wording.
• E.21 governs pattern-quality evaluation characteristic spaces.
• C.29 governs mathematical-lens adequacy.
• Exact evidence, assurance, gate, work, decision, causal-use, release, benchmark, and publication patterns govern their own claims.

#C.16.P:End

Last Updated: 2026-05-31 — this section last modified in upstream FPF commit 16cd3138 (github.com/ailev/FPF)