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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:45:10 UTC

A.6.A:12 - Relations

  • Uses: A.6.P when the recovered content is a relation claim; A.6.REL for its direct predicate and any needed occurrence identity.
  • Builds on: A.3 and A.7 for enactor discipline and EntityOfConcern and Description-episteme plus publication and carrier separation; A.15 for keeping invitation distinct from enactment; A.6.B for boundary claim classification; E.17.0, E.17, and E.18 for viewpoint reference resolution, independent view conformance, and viewpoint publication.
  • Works alongside: C.16.Q for evaluative language; the two are siblings, not substitutes.
  • Coordinates with: C.2.2a, A.16, A.16.1, A.16.2, and B.4.1 for language-state chart positions, admissible moves before post-threshold repair, and retreat when a published recovery result must be reopened; use A.16.0 only when lineage, branch, loss, or an actual responsibility-handoff history itself must be published as an explicit trajectory account; B.5.2.0 for probe-question cases that are still prompt-shaped; C.2.LS, C.2.4, C.2.5, C.2.6, and C.2.7 for language-state facet governance.
  • Must not replace: C.2.3 as the single subject pattern for F.
  • Uses for shared naming: E.10, F.17, and F.18 when an interpretation label or reusable recovery designation needs a shared name.

A.6.A:12.1 - Early cues and recovered meanings

Use this method when the wording can support a useful interpretation or a question that distinguishes alternatives. Earlier cues may remain with A.16.1 or B.4.1. A recovered inquiry can remain open, and a recovered physical claim can return its exact missing rule or fact.

A.6.A:12.2 - Continue from the recovered result

Apply A.6.B when the recovered claim is boundary-bearing and A.15 when a Method, plan or performed Work question is live. Keep an alert-intervention or operator-intervention reading distinguishable from a generic interface cue when human factors, authority or the policy rule change the result. A common invitation record is not a prerequisite.

A.6.A:12.3 - Governance boundary

This pattern may cite an F.9 Bridge and bounded-use claim, an optional F.9.1 stance note, an A.16 articulation-state result, authority-reference fields, or language-state facet characteristics from C.2.LS, C.2.4, C.2.5, C.2.6, and C.2.7; it does not redefine any of them.