A.6.B:5 — Quadrant specifications

Preface node heading:a-6-b-5-quadrant-specifications:15269

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

The following normative specifications state what each quadrant is for, how it is written, and what it must not contain.

A.6.B:5.1 — Quadrant L: Laws & Definitions

Intent. State truth‑conditional content: definitions, invariants, typing and well-formedness constraints, equational laws.

Adjudication. In‑description: can be checked by inspection, proof, type validation, or model reasoning.

Canonical form. Definition: / Invariant: / predicate‑style constraints using “is / iff / for all”.

Prohibitions.

  • An L-* statement MUST NOT contain RFC deontic keywords (MUST, SHALL, SHOULD, or MAY) as operators inside the law or definition itself.
  • An L-* statement MUST NOT encode runtime gate predicates (those are A-*).
  • An L-* statement MUST NOT assert evidence availability or measurement outcomes (those are E-*).

A.7 EntityOfConcern binding. Identify what the L-* definition, invariant, or typing rule concerns, separately from the episteme carrying the claim. Its EntityOfConcern need not itself be a description and may be Work.

Typical dependence. A-* and E-* claims may reference L-* IDs or canonical locations for vocabulary, metric definitions, and invariants needed for interpretation.

A.6.B:5.2 — Quadrant A: Admissibility & Gates

Intent. Specify when a named action or application is admissible under its governing rule: for example, runtime entry predicates, validity gates, and applicability checks that require context or execution environment. An A-* predicate may consume a separately established result as one input, but it does not create or settle that result. If the sentence uses permission wording, choose its job with the branch in §8.4.1.

Applicability and admissibility. Signature Applicability scopes intended use and bounded context; a mechanism's runtime entry predicates belong in U.Mechanism.AdmissibilityConditions as A-*. If prose says “clients must satisfy the applicability”, first recover whether it means the declared scope or an entry condition. State the generic D-* prescription, or the independently instituted individual duty, separately and reference the condition it requires. Classify that condition as A-* only when it is an entry predicate.

Adjudication. Inspect the declared entry rule and its inputs to establish the A claim. Evaluate that predicate at the named action's entry or stated application point to obtain a particular satisfaction or gate-decision result; report that result separately in E.

Canonical form. Predicate style, e.g.:

  • “A request is admissible iff …”
  • admissible(x) iff P(x) (conceptual form; no particular syntax is required)

Prohibitions.

  • An A-* statement MUST NOT be placed in U.Signature.Laws.
  • An A-* statement MUST NOT use RFC deontic keywords as if it were an agent obligation. (It is a gate predicate, not a duty.)
  • An A-* statement MUST NOT claim that evidence exists (that is E-*) or that someone must enforce the gate (that is D-*).

A.7 EntityOfConcern binding. An A-* claim concerns the admission predicate for a named action or application, not a client's duty to comply with it. Keep that predicate distinct from the episteme carrying the claim.

Required references. If an A-* predicate relies on defined terms or invariants, it SHOULD reference the relevant L-* IDs or canonical locations (or at minimum the signature that defines them).

A.6.B:5.3 — Quadrant D: Deontics & Commitments

Intent. State one atomic deontic claim. A generic prescription states what one policy or other normative episteme requires; it does not create an individual duty bearer or commitment occurrence. A claim that one actual System or separately governed party has that duty instead cites one separately obtaining A.2.8 U.Commitment. When a sentence sounds permissive, use §8.4.1; only its Grant or norm row enters D. Writing the D-* sentence alone neither institutes a relation nor establishes compliance.

Adjudication. For a generic prescription, inspect the normative source, its applicable rule content, scope, and current edition. For an individual duty, apply A.2.8 to the separately obtaining commitment and its actual basis. The wording alone establishes neither obtaining nor compliance.

Canonical form. First choose the route. A generic D claim names the normative episteme and the rule content being stated, without inventing an individual bearer.

An individual-duty D claim names the actual bearer and U.Commitment; a system-role kind or assignment may be a rule ground but is neither bearer nor duty.

A responsibility claim uses an admitted domain responsibility predicate and its actual participants, or returns its missing governor. A permissive-looking word does not by itself select D; use §8.4.1 for the grant route.

Examples:

  • Generic: “APIEntryPolicy-v4 requires covered clients to satisfy A-….” No individual commitment is asserted.
  • Individual: “Actual bearer ClientIntegrator-A has commitment COM-17 to satisfy A-….”

Canonical assertion (recommended; lintable). Use a CommitmentAssertion only when an individual-duty claim must be reused or audited. It concerns one separately obtaining U.Commitment and makes explicit:

  • entityOfConcernRef, resolving to one U.Commitment occurrence, and the D-* claim ID;
  • exactly one actual bearer branch: dutyBearerSystemRef or dutyBearerPartyRef;
  • non-empty dutyReferentRefs and any actual counterparties;
  • the A.2.8 DeonticModalityToken, scope, and validity window;
  • the current constitutive policy, individualizing rule, and actual instituting basis required by that rule; and
  • evidence-claim or carrier references only when the receiving reliance or adjudication needs them.

The assertion states and supports a claim about the relation. Fields, publication or evidence have a constitutive role only when the identified rule requires that contribution and its subject pattern's test is satisfied.

Prohibitions.

  • A generic D-* statement MUST NOT invent an individual bearer or commitment; name its normative source and rule content.

    An individual-duty D-* statement MUST NOT use “the system, service, interface, or specification” as a vague subject; name the actual duty-bearing system or separately governed party and U.Commitment, with an assignment only when the constitutive rule uses it as a ground.

    Use A.6.C when ambiguity in promise, utterance, approval, guarantee, or agreement-like boundary wording changes the claim's interpretation or use.

  • A D-* statement MUST NOT give a referenced L-* or A-* predicate a different meaning. It MUST reference that predicate by ID or canonical location when its meaning depends on it; a faithful explanation may accompany the reference.

  • A D-* statement MUST NOT represent a duty, commitment, or grant as a law or assert that writing the claim alone makes it obtain.

A.7 EntityOfConcern binding. A generic D-* claim episteme concerns the normative rule content it states. An individual D-* claim concerns the duty, commitment, or grant named by its content and does not substitute for that object. When permission wording is live, the branch in §8.4.1 names the subject pattern and the obtaining or non-obtaining test.

Required references.

  • If a D-* claim states a prescription or duty to comply with a gate, it MUST reference the relevant A-* ID(s) or canonical location(s).
  • If a D-* statement is meant to be auditable, it SHOULD reference the E-* claim(s) that provide evidence and the carrier classes involved.

A.6.B:5.4 — Quadrant E: Work‑Effects & Evidence

Intent. State an actual occurrence, evaluated finding, observed condition or evidence-support claim. Settle it from the actual work, evaluation, observation, or carrier conditions required by its predicate.

Adjudication. From actual work, evaluation or observation under the claim’s subject predicate. A record can support that judgment through its evidence relation; its presence alone does not settle the claim.

Canonical form. Write the ordinary result first, then make recoverable only what settles it:

  1. the predicate and object that the claim concerns;
  2. the participants, work or evaluation occurrence, scope/window, comparison frame, and other conditions required by that predicate; and
  3. the evidence or source-use relation when the receiving use needs that support; identify the supporting carrier only when carrier identity matters to that use. A carrier may support the claim but does not create the work, effect, or finding.

When permission wording is current, use the branch in §8.4.1 for the occurrence or finding, its failure test, predicate, and subject-pattern locator; do not repeat that subject-question catalogue here.

Prohibitions.

  • E-* statements SHOULD NOT use RFC deontic keywords; they report adjudicable results rather than obligations.

  • An E-* statement MUST NOT hide a gate predicate; gate predicates are A-*.

  • For a claim about a particular dated Work, first recover each actual performer through A.13 and let A.15.1 independently admit the Work. Ordinary metonymy is usable when the capable performer remains recoverable; an interface, record or publication does not supply a performer merely by being named.

    Add an A.2.1 assignment reference and F.6 only when this claim or its receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither the assignment nor the performer. Missing or failed F.6 alone does not overturn independently admitted Work.

    If the attribution finding questions a premise consumed by Work admission, recheck that premise and the dependent claims. If a duty or commitment is also claimed, express it separately in D-*.

A.7 EntityOfConcern binding. An E-* claim episteme concerns the work effect, evaluated finding, evidence relation, or carrier condition named by its predicate. A record or carrier is a separate object and becomes the concern only when its existence or condition is itself the claim.

Required references.

  • If the result depends on an entry predicate, the E-* statement SHOULD reference the relevant A-* claim. If it depends on an actual gate decision, reference the separate E-* claim about that A.21 decision result.
  • If another object is needed to settle the predicate, reference that object's subject pattern without importing its quadrant.
  • If evidence is used for reliance, recover the independently established support or evidence-use relation and its basis. Use A.2.4 for the first evidence-use or status-use classification; use A.10 when the source-to-use account must remain replayable, and G.6 when an addressable provenance path is needed. Carrier presence alone is not support.

Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)