E.21:4.3a - Precision-restoration profile

Before assigning the coordinate table, apply the whole-span precise-language reading in F.19 and record one PrecisionRestorationProfile summarizing its quality effect. F.19 governs the reading, repair, and local revalidation; E.21 consumes their result for its existing coordinates. The reading asks which governed object, claim, relation, and reader use the sentence, table, section, or repeated content family serves in the pattern of concern.

Use F.19’s evidence-selection and coverage conditions for recoverability. Name the kind of basis and its material reading conditions in EvaluationEvidenceBasis; use checkedLoci for the text and relations it actually covers. A clean profile retains those qualifications. If F.19 requires an actual reading that is missing, the dependent recovery claim lacks that basis. Apply E.21:4.3’s missing-evidence rule to the affected coordinates and identify the missing judgement. Distinguish this evidence gap from a wording defect established by reading the text.

Use this compact shape:

PrecisionRestorationProfile:
  overallEffect: <clean | boundedLocal | lowersCoordinates | repairBeforeUse>
  checkedLoci: <sections, rows, cases, and relations checked>
  affectedCoordinates: <coordinates lowered or protected>
  repairProposal?: <actual repair or blocker and its locus>
  kindRestorationCheck?: <when a changed FPF-governed expression can alter meaning: pre-repair and proposed post-repair object, kind, relation, current ontic slot, relation position, use relation, claim kind, admissible use, and scope; preserved | split | intentionally changed by accepted decision | blocker>

The diagnostic fields below are optional. Retain a field when its finding, restoration choice, or bounded evidence changes the quality result; a clean result needs no separate clean entry for each field. Fuller profiles use the same field meanings. When a receiving form needs an explicit untriggered kindRestorationCheck disposition, it may use not triggered, ordinary prose, or no FPF-governed phrase changed with the checked locus; this is optional detail in E.21.

The scalar is the strongest quality effect that any layer requires: clean, bounded local repair, coordinate lowering, or repair-before-use. Classify a new symptom under the relevant diagnostic layer or restoration locus and apply its effect to existing E.21 coordinates. F.19 settles ordinary whole-span language questions. Open E.10, E.10.ARCH, or F.18 for an unresolved word, head, or name problem; for hidden candidate ontics and ontic-vs-description-vs-publication boundaries, use E.24.CD, E.24.PUB, or the concrete pattern content that defines or constrains the disputed object; claim, relation, evidence, Work, decision, assurance, publication, or pattern-application problems return to the pattern content that defines, constrains, or tests the disputed item. A pattern reference locates the content whose concrete contribution the evaluation uses. Exact predicates and ClaimGraph identity are required only when the evaluated claim or named reliance needs them. E.21 consumes only the result: which coordinates fall, which stay protected, and what repair would make the quality claim true. The mgdaColdReaderRecoverability layer asks whether a reader without the DRR, campaign notes, or evaluator memory can recover the object, kind or ordinary status, relation or claim position, admissible use, next exact assertion when one is needed, and next concrete defining, constraining, or checking contribution. If a repair replaces a specific phrase with object, item, value, relation, record, condition, basis, material, or unqualified specialization and the reader cannot recover what specializes what, which relation is live, or which assertion or concrete pattern contribution is required, this layer is not clean.

When this layer finds a hidden candidate ontic or publication-form confusion, the E.21 result records only the quality effect and affected coordinates. Candidate detection, ontic placement, slot-relation design, and publication-boundary repair remain with E.24.CD, E.24.PUB, or the concrete pattern whose content defines or constrains the affected object. The kindRestorationCheck is required when a changed FPF-governed expression can alter the meaning-bearing object, kind, relation, current ontic slot, relation position, use relation, claim kind, admissible use, or scope. It records those live values before and after the proposed repair, then names the concrete contribution when another pattern defines, constrains, or tests the affected kind, relation, claim, or position (A.6.0, A.6.5, A.6.P, C.29, A.15, E.24.CD, E.24.PUB, E.10.ARCH, or another relevant pattern). Every value that can drift receives an explicit preserved, split, intentionally changed by accepted decision, or blocker disposition. When no such risk is present, F.19’s ordinary local revalidation is sufficient and the profile omits this field. The underlying slot, ontic, publication-form, and mathematical-lens rules remain with their subject patterns. A lexical replacement is not a repair when it only removes a trigger word, substitutes one umbrella for another, narrows a graph or method into a work sequence, widens a work occurrence into a method, turns a publication form or evidence source into the object itself, or otherwise changes kind, current ontic slot, relation position, use relation, or claim kind without an accepted decision. If the kind, current ontic slot, relation position, use relation, or claim kind cannot be recovered, the profile is at least lowersCoordinates; if the proposed repair would change one of them and no accepted DRR or concrete defining, constraining, or checking pattern content justifies that change, the result is repairBeforeUse or holdForArchitectureDecision.

When the profile is not clean, lower every affected coordinate named by the profile. Do not hide a present precision-restoration issue only in EntityOfConcernPrimacyAndSemioBiasResistance, and do not raise the result through related-pattern-boundary praise, projection evidence, or “correct but true” guards when those materials compete with the pattern’s own EntityOfConcern, first useful move, practitioner action, practical delta, or next useful action.