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

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:35:20 UTC

A.6.C:4.2 — Classification recipe into A.6.B (L/A/D/E)

After unpacking, classify each atomic statement using the Boundary Norm Square as defined normatively in A.6.B (quadrant semantics + form constraints + cross‑quadrant reference discipline). A.6.C does not redefine L/A/D/E; it applies them to contract-language as follows:

  • Promise content → L/A (promise semantics + eligibility).
    • Put meanings, invariants, and metric definitions for what is promised in L (L-* in signature laws and definitions).
    • Put “eligible, covered, or valid iff …” predicates as A (A-* admissibility or gate predicates), not as deontic obligations.
  • Governance and permission-looking claims → claim-specific quadrant.
    • Put a generic contract, SLA, protocol, or policy prescription in D as a claim about its exact normative source and applicable rule content. Put an individual-duty claim in D only when it cites an exact separately obtaining U.Commitment under A.2.8; do not use a completed record as the relation.
    • For authority-looking wording, select one A.6 A6-AW-* row: norm/grant → D, mechanism entry predicate → A, and an actual A.21 GateDecisionResult, exercise, evaluated finding/conflict, or source observation → E. Split a predicate and an actual gate result into separate atomic claims. Cite the exact A.2.8.PER object only where that row requires it; the selected subject pattern or kind of direct object does not choose the sentence’s quadrant.
    • If a generic prescription or individual duty requires satisfying or enforcing a gate, its D-* claim MUST reference the relevant A-* ID(s) (D→A).
    • If reliance on either D branch needs evidence, cite the relevant E-* claim or evidence-use relation (D→E); for the individual branch, a CommitmentAssertion may carry that reference.
  • Performed Work → E (did it happen?).
    • Name the exact A.15.1 Work occurrence and its performer, Method, extent, and containing System. Add an assignment reference and F.6 only when the claim or a receiving use consumes precise assignment-bound attribution; do not add an output or delivery field.
  • Result or consequence → E when current (what else happened?).
    • Use the one applicable A.15.1:4.6 predicate and exact subject assertion for the returned value, production, change, evaluation result, delivery/transfer, or acceptance claim; retain its pattern only as a locator.
  • Evidence → E when relied on (how can the claim be used?).
    • Name the exact A.10 path, observation conditions, and carrier for the Work or consequence claim being supported. Keyword placement rule (canonical claim set). Within the canonical L-, A-, D-, or E-classified claim set, BCP-14 keywords are statement operators, not ontology or quadrant selectors. MUST, MUST NOT, SHOULD, and SHOULD NOT enter D for a generic prescription or, when separately instituted for an actual bearer, an individual duty, recommendation-as-duty, or prohibition. MAY, OPTIONAL, and authority-looking synonyms trigger the A.6 A6-AW-* branch: a current norm or grant enters D, a mechanism entry predicate enters A, and an actual A.21 GateDecisionResult, exercise, or evaluated finding enters E. If the wording does not expose the branch and direct object, rewrite it or mark it informative.

A helpful rewrite rule:

First recover what “allowed” asserts by selecting one A.6 A6-AW-* row. Put only the current norm/grant in D, the entry predicate in A, and an actual A.21 GateDecisionResult, exercise, or evaluated finding in E; cite each direct object and source. The word and A.2.8.PER membership select neither quadrant nor obtaining.