A.6.B:5.2 — Quadrant A: Admissibility & Gates
Intent. Specify when a mechanism application is admissible: 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.
Common mistake #0 — Applicability ≠ Admissibility (informative). Signature Applicability scopes intended use and bounded context; it is not a runtime entry gate. Runtime entry checks and admissibility predicates belong in U.Mechanism.AdmissibilityConditions as A-*. If prose reads “clients must satisfy the applicability”, separate the A-* gate from either a generic D-* prescription or, when independently instituted, an individual duty linked to that gate.
Adjudication. In‑work: evaluated at mechanism entry (or operationally at the point the mechanism is applied).
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 inU.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 isE-*) or that someone must enforce the gate (that isD-*).
A.7 EntityOfConcern binding. An A-* claim concerns the mechanism-entry
predicate: what the mechanism admits, not a client’s duty to comply with it.
Keep that predicate distinct from the episteme carrying the claim.
Required references (explicit). 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).