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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 10:45:12 UTC

E.10.D2:16 - Repair moves

Use these repairs on live prose; retain old spellings only as quoted source-side trigger wording:

  1. Start with the exact receiving work, decision, comparison, inquiry, preservation, teaching, or publication use and its next unresolved question or action.
  2. Replace DescribedEntity*, EntityOfInterest, EoI, EoIClass, and generic “object under description” wording with the exact EntityOfConcern and its independently governed identity.
  3. Replace local episteme-slot, subject-field, tuple, card, or context-record constitution with the exact C.2.1 ClaimGraph, EntityOfConcern, and effective ReferenceScheme test.
  4. Replace peer-layer I-D-S wording with EntityOfConcern, description episteme, and admitted specification use; specification is not a third peer kind.
  5. Replace a positive source-side DescriptionContext with the named describing use and the exact viewpoint it selects when that selection changes the reading. Keep selection outside episteme identity, conformance, and view membership; do not recreate the rejected tuple under another name.
  6. Replace “the role contains a characteristic space, state relation, or checklist” with a precise claim: the system-role-kind-description episteme characterizes one exact local system-role kind using claims that cite those independently governed objects or relations.
  7. Replace carrier identity with the exact publication form, U.PresentationCarrier, bearing relation, and publication occurrence required by the current use.
  8. Replace ...Spec names lacking checkable claims and a named harness or validation relation with ...Description. Preserve or update the selected viewpoint only when the relying describing use depends on it.
  9. Route permission, evidence, assurance, gate, decision, promise, commitment, work, publication, view, Bridge, retargeting, currentness, and representation claims to their exact direct governors.
  10. Replace “role of this description, source, standard, evidence, or publication” with the exact typed use relation. Use one exact occurrence of a directly declared U.SystemRoleAssignment species only for an independently admitted U.System assigned to one exact local system-role kind; an acting holon is eligible only after that exact entity has independently passed U.System admission for the claim.
  11. Delete mandatory context recursion for descriptions of epistemes; recover the described episteme as EntityOfConcern under C.2.1, including its permitted self-description case.
  12. Stop when the recovered constitution and one needed neighboring relation make the next action clear; do not complete a universal description card.