fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 87008–87021

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:40:10 UTC

E.10:0.5 - Optional wording-repair note

Use these fields only when a receiving review or decision needs an inspectable wording-repair note:

  1. BoundedTextSpan: the exact sentence, row, section, pattern version, DRR slice, or project text deliberately using FPF-governed terms, pattern references, relation names, or conformance claims under repair.
  2. TriggerSpan: the word or phrase that carries possible FPF-governed use.
  3. SelectedInterpretation: one applicable repair-path classification from this closed value set—ordinary no FPF-governed use, local head repair, register repair, morphology repair, context-word recovery through E.10.D1, learning-word recovery through E.10.LRN, interest-or-curiosity recovery through E.10.INT, bare-role meaning recovery through E.10.ROLE, relation-like precision restoration, episteme precision restoration, publication precision restoration, source-use relation or source-ref target recovery, durable naming, or not-triggered false positive.
  4. FinalWordingOrBlocker: the accepted local wording, the result returned by the selected repair or pattern, or the blocker that remains.
  5. StopBackToSubstance: once the final wording or blocker is written, return to the domain question that made the phrase matter. Further lexical classification is non-use unless another phrase still hides an FPF-governed claim.

SelectedInterpretation retains that closed value set. If none of its classifications fits the current subject-specific repair, use the selected subject pattern’s own result instead of silently extending the lexical form.

When a wording-repair note needs formal fields, record one plainIntent before the technical fields. Use E.10.ARCH for the fact, declaration, report, or representation branch only while that distinction remains unresolved. Keep triggerSpan, boundedTextSpan, selectedInterpretation, LEX.TokenClass?, register, USM.Scope?, EntityOfConcern and Description-episteme boundary and specification use?, patternRef?, and finalWordingOrBlocker; add patternRef only when pattern identity changes the result. Add an exact assertion, predicate, or ClaimGraph only when the current claim or a named later use depends on that identity. Otherwise name the concrete object and the ordinary claim. Do not use slotOrUsePosition as a union field for actual participants, A.6.5 SlotSpec values, participant designations, or representation places.