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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:25:20 UTC

E.18.1:4.3 - Direct-relation distinctions that change the branch

P2W carries a returned value or stop; it does not restate the neighboring pattern’s internal test. Keep a local distinction here only when it changes which question the reader asks:

  • Lens or declaration? Ask whether the current use judges a mathematical representation or declares a signature. Split the claims when both are present; the first-use case in 4.2 shows the difference.
  • Mechanism or method? Ask whether the claim concerns a law-governed operation application or a reusable way of doing. A shared noun supplies neither; split the questions and use the Relations map once for each current claim.
  • Change or timing? Ask whether the claim concerns an actual bounded change, a temporal aspect such as an interval or cadence, or the adequacy of a temporal claim for one use. A timestamp or a before-and-after picture supplies none of those answers.
  • Work, change, or their connection? Identify the dated U.Work occurrence and actual U.Transformation separately, then ask whether a work-to-change claim is current. Apply the pattern that defines or tests that claim, or the applicable A.6.RCD route, and carry only its positive or negative result or exact blocker. Shared timing does not answer the question. The BuildOps and Pump 14 slices in 5.1 show a positive result; Pump 14 also preserves an earlier missing-governor stop without copying the result’s proof.
  • Approved, ready, released, or permitted? State which result is being sought: a gate decision, permission result, work-entry-readiness result, release U.Work occurrence, or subject-release relation. Apply the pattern that answers that question and carry its result or blocker; authorization is not a result type.
  • Result or production? Let A.6.P.WMR separate the concrete result questions. Open A.15.PROD only for a production-work, entity-inception, or production-completion question; its returned claim or blocker stays separate from work, change, delivery, acceptance, and release.

For every other exceptional object, state the relation-specific question and consult the canonical map in Relations. A label, diagram, note, plan, trace, or familiar noun can trigger that question but cannot answer it.