Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 14:50:08 UTC

A.6.A:4.1a - Optional recovery note

When a receiver needs a reusable account of the repair, a note may contain:

trigger and source context
recovered statement or question
receiving use
participants and conditions that determine the result
subject rule and supporting sources, or the exact missing basis
material rival interpretations and their disposition, when needed
detector, viewpoint, representation and publication details, when relevant
next subject result or return, when one is needed

This is a way to express the result. It neither declares a common relation kind nor supplies an obtaining predicate. For an actual relation claim, its participants, direction, applicability, evidence requirements and same/new rule come from that relation’s direct governor. Recover ref-backed participants and by-value content under A.6.5 when the note itself is changed.

Omit fields that do not change interpretation or use. A sufficient sentence remains a complete result. A particular receiving publication can require more structure under its own conditions; that requirement does not become a universal prerequisite to wording recovery.

Viewpoint and view discipline. When viewpointRef is present, effectiveReferenceScheme is also explicit and the reference resolves under that scheme to one exact independently admitted U.Viewpoint episteme. view is a separate optional value: it names one independently identified C.2.1 episteme that already has U.View membership only because exact E.17.0 EpistemeViewpointConformanceRelation(view, viewpoint) obtains for at least one admitted viewpoint. The selected viewpointRef need not be the viewpoint to which an optional view conforms unless the record explicitly claims that relation. Including viewpointRef or view in a recovery note establishes neither U.Viewpoint nor U.View dependent-kind membership; it only cites already established objects. Detector, viewpoint selection, view membership, viewing construction and publication remain separate.

A sentence such as “X affords Y” needs repair when its intended action, participants or basis remain hidden for the receiving use. For a recovered relation claim, apply A.6.REL; for a recovered question, preserve the question. Earlier cue content may remain a cue pack, RoutedCueSet or another appropriate expression.

Interpretation and enactment. The menu label records a candidate reading of the wording. It does not identify an occurrence or establish that different interpretations have one relation kind. A proposed action is not an actual U.Work or a U.WorkPlan. When the result selects a Method for enactment, name the exact independently admitted U.Method; any methodDescriptionRef remains a separate source episteme. Use A.15.2 for intended-work planning and A.15.1 for actual Work. Route an already returned result or Work consequence through A.15.1 §4.6 or its direct result/measurement governor: distinguish the application result binding, returned value, any independently established evaluation Work, and a result episteme when one is needed. A Work-to-result claim needs its own declared domain predicate; a missing predicate returns the named gap while leaving an independently established application binding usable.

A.7 boundary note. When the site affects interpretation, distinguish an EntityOfConcern-side participant, a Description episteme participant and any non-claim-bearing site kind. Name a participating publication face, publication form, carrier or rendering separately under A.7. An optional note may use siteClassification and publicationOrCarrierParticipation for these distinctions; ordinary wording can express them too.

Separation note. detector and invitedEnactor are not synonyms. When both matter, they SHALL be published separately.

Enactor note. When the recovery result names an actual would-be enactor, that enactor SHALL resolve to a U.System or to a role assignment whose holder is a U.System. An episteme, description, publication face, or carrier may participate in the site, but not as the acting bearer.

Episteme non-agency note. If the site is a Description episteme, any later enactment still occurs through carriers, acted-on systems, or both; the description itself never acts.