A.6.C:4.2 — Classification recipe into A.6.B (L/A/D/E)
Preface node
heading:a-6-c-4-2-classification-recipe-into-a-6-b-l-a-d-e:16164
What this page is
This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.
Methodology
Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.
Content
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 and conditions → classify by the claim.
- Put meanings, invariants, and metric definitions for what is promised in L (
L-*in signature laws and definitions). - Recover what “eligible”, “covered” or “valid iff” means. A definition or declared scope remains L; an admission predicate for a named action or application is A; a finding that a particular case meets the conditions is E. A duty concerning those conditions is a separate D claim.
- Put meanings, invariants, and metric definitions for what is promised in L (
- Governance and permission-looking claims → claim-specific quadrant.
- Put a generic contract, SLA, protocol, or policy prescription in D as a claim about its normative source and applicable rule content. Put an individual-duty claim in D only when it cites a separately obtaining
U.Commitmentunder 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, admission predicate → A, and an actual A.21GateDecisionResult, exercise, evaluated finding/conflict, or source observation → E. Split a predicate and an actual gate result into separate atomic claims. Cite the 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 relevantA-*claim by ID or canonical location (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, aCommitmentAssertionmay carry that reference.
- Put a generic contract, SLA, protocol, or policy prescription in D as a claim about its normative source and applicable rule content. Put an individual-duty claim in D only when it cites a separately obtaining
- Performed Work → E (did it happen?).
- Result or consequence → E when current (what else happened?).
- Use the one applicable
A.15.1:4.6predicate and subject assertion for the returned value, production, change, evaluation result, delivery/transfer, or acceptance claim; cite the pattern that defines or constrains that claim.
- Use the one applicable
- Evidence → E when relied on (how can the claim be used?).
- State the target claim and the independently established evidence-use or other direct support relation, including its polarity and limits. Use A.2.4 for first-use classification and A.10 when a replayable source-to-use account is needed. Keep the grounds required by the receiving use; identify carriers and observation conditions when they affect that claim or use.
Keyword placement rule (canonical claim set).
Within the canonical L-, A-, D- or E-classified claim set, BCP-14 keywords are statement operators. Classify the claim through A.6.B: a generic prescription or an independently instituted duty, recommendation-as-duty or prohibition enters D. When MAY, OPTIONAL or authority-looking wording is ambiguous, use the A.6 A6-AW-* branch. If its object or meaning remains unresolved, retain it as bounded source wording with that uncertainty; marking it informative does not settle the claim.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)