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

Preface node heading:a-6-b-5-2-quadrant-a-admissibility-gates:15293

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

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).


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