#State-Family Precision Restoration

A.19.SPR · Stable · State-family precision-restoration pattern · Normative unless explicitly marked informative · Part A - Kernel Architecture Cluster

#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: State-family precision-restoration pattern Status: Stable Normativity: Normative unless explicitly marked informative

Plain-name. State-wording repair.

Intent. Recover state, status, posture, readiness, and close state-family wording whose bearer, state frame, value set, admissible use, or receiving FPF pattern is hidden.

This pattern does not define a general Posture kind. It repairs wording that acts like a state-like claim before a reader treats the word as evidence, assurance, gate passage, release permission, source authority, maturity, or work completion.

Builds on. E.10, E.10.ARCH, A.19, A.3.3, C.2.2a, A.16.*, A.10, B.3, A.20, A.21, C.27, C.29, E.17, E.9.DA, E.21, F.18, and project-side administrative, review, dispatch, release or admission, or source-control records when the state-like claim is administrative rather than FPF-content-bearing.

Coordinates with. A.17, A.18, C.16, C.16.P, C.16.Q, A.6.P, C.2.P, C.30.P, E.8, E.19, and E.11.

E.10.ARCH governing-pattern relation. When E.10 encounters state-family wording such as state, status, posture, readiness, stance, currentness, validity, stable, ready, accepted, blocked, candidate, or close compounds whose bearer, state frame, value set, admissible use, validity window, reopen condition, or governing pattern is hidden, E.10.ARCH assigns the repair to A.19.SPR only until those values are recovered or the claim being made belongs to C.2.P, A.10, B.3, A.20, A.21, C.27, C.29, E.9.DA, E.21, A.6.P, A.15, or the project-side administrative, review, dispatch, release or admission, or source-control record.

Use A.19.SPR when state-family wording has FPF-governed use but does not yet say what is in which state, according to which state frame or governing pattern, with which value or classification, for which admissible use.

#Relations

#Content

#Use this when

Use A.19.SPR when state-family wording has FPF-governed use but does not yet say what is in which state, according to which state frame or governing pattern, with which value or classification, for which admissible use.

Typical triggers:

• state, status, posture, readiness, stance, currentness, validity, degraded, accepted, admissible, blocked, candidate, stable, ready, or close compounds;
• local fields such as source posture, evidence posture, assurance posture, publication posture, release posture, validation posture, readiness posture, or support posture;
• precision-looking local fields such as LensUseAdmissibilityValue, dynClaimPosture, or a specification-use label when their bearer, value set, governing pattern, use boundary, or reopen condition is not recoverable.

What goes wrong if missed. A broad state word becomes a miniature hidden ontology. A source gets called "current", "supporting", or "accepted" without a source-use role. Evidence becomes assurance. A publication face becomes gate passage. A lens-use label becomes empirical truth. An external administrative status leaks into pattern prose. A readiness word implies work may proceed without the threshold, evidence path, gate, or decision record that would carry that claim.

What this buys. The reader can recover the state-like claim named by value, the governing pattern, the allowed use, and the blocked adjacent overread before acting on the word.

First useful move. Ask: what bearer has which state-like value under which state frame or governing pattern? If that cannot be answered, demote the wording to ordinary prose, quote-only source wording, a reduced-use cue, or a blocker.

Not this pattern when.

• If the pattern governing the recovered claim and state-like field are already recoverable by value, use that pattern directly.
• If the wording is ordinary prose and carries no FPF-governed use, keep it ordinary.
• If the state-like claim concerns one Characteristic, Scale, coordinate, score, or metric, use C.16.P before state-family repair.
• If the state-like claim concerns source-expression, publication, carrier, or source-use wording, use C.2.P first; return to A.19.SPR only if a state-like claim remains.
• If the claim being made is relation construction, architecture or structure wording, quality-term or evaluative characterization, function-like wording, or naming, use A.6.P, C.30.P, C.16.Q, A.6.F, or F.18 as selected by E.10.

#Problem frame

FPF needs state-like wording. Engineers say that a system is ready, a source is current, an evidence path is incomplete, an assurance claim has decayed, a lens use is admissible, or a pattern is stable. Those compact words are useful when the state frame is declared.

The defect appears when the word substitutes for the frame. Posture is the current visible symptom, but the same failure appears with state, status, readiness, stance, currentness, and similar words. The repair question is:

What state-like predicate is being asserted over which bearer, under which FPF pattern, for which use, and with which blocked overread?

The state-like bearer under repair may be a holon in a CharacteristicSpace, a role-state assertion, a language-state position, a source-use relation, an evidence path, an assurance claim, a publication use, a gate or constraint record, a temporal claim, a mathematical-lens use, a DRR decision-adequacy result, a pattern-quality result, or a project-side administrative, review, dispatch, release or admission, or source-control record. Those are not one kind. They only share the need for a state-like predicate named by value.

#Problem

How can FPF repair state-family wording without:

• defining a general Posture kind;
• replacing one broad word with another broad word such as basis, support, state, or status;
• treating every state-like word as a CharacteristicSpace position;
• treating publication, source, evidence, assurance, gate, decision, work, release or admission, and administrative states as one source, publication, or language-state case;
• duplicating the state-family recovery algorithm inside every governing pattern;
• demoting finite local fields such as LensUseAdmissibilityValue or dynClaimPosture when they are already well-formed, or erasing a real specification use or refinement gate that names its neighboring pattern governing the claim and value set.

#Forces

#Solution

Repair state-family wording by producing a StateFamilyPrecisionRepair or an equivalent local rewrite.

Minimum shape:

StateFamilyPrecisionRepair:
  triggerSpan:
  boundedTextSpan:
  bearerRef:
  stateFrameOrGoverningPatternRef:
  stateValueOrClassification:
  criteriaOrEvidenceRef?:
  admissibleUse:
  nonAdmissibleOverread:
  validityWindowOrReopenCondition?:
  finalWordingOrBlocker:
  remainingReaderMove:

Use the full shape only when the repair must remain inspectable. A direct rewrite is enough when one sentence names the bearer, state frame, value, use boundary, and governing pattern.

#Recovery sequence

1. Capture trigger and bounded text. Copy the encountered state-family word and the sentence, row, card, or field that uses it.
2. Recover the bearer. Name the item whose state-like value is being claimed: holon, role, source, evidence path, assurance claim, publication face, PublicationUnit, gate record, temporal claim, lens-use card, DRR, pattern version, project-side administrative record, review record, dispatch record, release or admission record, source-control record, or another FPF kind named by value.
3. Recover the state frame or governing pattern. Decide whether the frame is A.19 CharacteristicSpace, A.3.3 dynamics, role-state assertion, C.2.2a language-state chart, A.10 evidence path, B.3 assurance, A.20 constraint or adjudication state, A.21 gate decision, E.17 publication use, C.27 temporal-claim state, C.29 lens-use admissibility, E.9.DA DRR-decision adequacy, E.21 pattern quality, or a project-side administrative, review, dispatch, release or admission, or source-control record.
4. Recover the value set or classification. If a local field remains, list its possible values or the neighboring pattern governing that claim that defines them. If no value set is recoverable, do not keep the state-family head as a field.
5. Recover criteria or evidence only when that claim is being made. Name threshold rule, observation, source currentness, evidence path, assurance tuple, validation regime, gate record, or witness only when the governing pattern for that claim is selected.
6. State admissible and non-admissible use. Say what the reader may do with this value and what adjacent claim remains blocked.
7. State validity window or reopen condition. If currentness, readiness, release or admission, validation, assurance, or administrative state can decay, name what changes the value.
8. Rewrite or demote. Replace broad wording with the state-like field or governing-pattern phrase named by value; otherwise mark quote-only, reduced-use cue, blocked transfer, or incomplete rewrite.
9. Return to the subject pattern. Do not let the repair become the subject Solution unless the pattern is itself about state-family precision restoration.

#Direct governing-pattern assignments

#Retained local field rule

A local ...Posture, ...Status, ...Readiness, or ...State field is admissible only when the text declares:

• field name;
• bearer kind;
• governing pattern;
• value set or declared classification source;
• admissible use;
• non-admissible overread;
• validity window, decay rule, or reopen condition when applicable.

If any of those are missing, either complete them now or rename the field to the phrase or record required by the governing pattern. A narrowing adjective does not count as kind recovery.

#Worked slices

Show, source currentness. "The source posture is good" is not admissible. Repair to: "The source has SourceUseRole = acceptedDecisionSource and SourceCurrentnessStatus = localAcceptedDecision for this DRR use; it does not become evidence, assurance, gate passage, or FPF doctrine by citation."

Show, evidence path. "Evidence posture is incomplete" repairs to an A.10 result: evidence kind, claim and effect, carrier or source path, currentness window, RelianceDisposition, admissible reliance, blocked reliance, and reopen trigger.

Show, publication use. "Publication posture allows decision input" repairs to an E.17 publication use note plus the decision or evidence pattern governing the claim being made. The publication face may orient, expose a source, compare, or carry a candidate input; it does not decide or assure by itself.

Show, mathematical lens. LensUseAdmissibilityValue may stay in C.29 because it names a local finite field for a mathematical-lens use. The field still cannot mean evidence, assurance, release, benchmark superiority, or source authority.

Show, temporal claim. dynClaimPosture may stay in C.27 when its value set and non-overread boundary are present. The value says what kind of temporal claim use is being made; it does not upgrade evidence, authority, assurance, or promise claim.

Show, administrative state. "The release or admission record is ready for release action" belongs in the project-side release or admission, review, dispatch, administrative, or source-control record that carries that state. A pattern body may mention it only as an informative boundary; it must not use that external administrative state as pattern-subject guidance.

#Conformance checklist

#Common anti-patterns

#Relations

#Rationale

The repeated problem is not a bad word. The repeated problem is an untyped state-like claim. FPF needs finite state-like fields, but each field must be over a bearer and a state frame. Placing this pattern under the A.19 neighborhood keeps the general repair near state-space and state-comparability discipline without making semio the home for every status word and without turning E.10 into an omnibus ontology.

The pattern also protects local fields named by value. LensUseAdmissibilityValue and dynClaimPosture are acceptable when their governing patterns declare value sets and boundaries. Specification wording is acceptable only as a Description episteme admitted for specification use or refinement under a specification-granting neighbouring pattern named by value; it is not a reusable posture field. Broad source posture, evidence posture, assurance posture, publication posture, release posture, and administrative forms are not acceptable unless they are repaired into FPF kinds named by value or moved to the project-side administrative, review, dispatch, release or admission, or source-control record that actually governs them.

#A.19.SPR:End

Last Updated: 2026-06-08 — this section last modified in upstream FPF commit 9b1cb920 (github.com/ailev/FPF)