Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:10:10 UTC

A.6:2 - Problem

The following confusions change the interpretation or use of a boundary claim:

  1. Laws vs admissibility. Authors encode runtime gate predicates as “laws”, or write invariants using RFC‑style deontic verbs, blurring “what is true or defined” with “what is allowed to be applied”. FPF separates these: admission predicates use the canonical source of their governing rule, including A.6.1 for mechanism applications; they do not belong in U.Signature.Laws. Common mistake #0 — Applicability ≠ Admissibility (informative): Signature Applicability scopes declared admissible use and bounded context; it is not a runtime entry gate. A mechanism’s runtime entry predicates belong in U.Mechanism.AdmissibilityConditions as A-*. Such a predicate may consume the direct object selected by one A6-AW-* row as input, but it neither creates that object nor proves gate passage. 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. Either branch can reference the A-* gate by ID or canonical location without becoming the gate.

  2. Admissibility vs deontics. MUST, SHOULD, MAY, and authority-looking words do not reveal whether a statement is a duty, one A6-AW-* permission branch, or an entry predicate. Classify the claim by its job; neither the word, selected subject pattern, nor kind of direct object decides the quadrant.

  3. Contract talk category errors. If “the interface promises…” leaves a consequential ambiguity about the claim or its participant, use A.6.C to recover it before treating the wording as an agency error. Use A.2.3 for promise content, A.2.9 for the instituting speech-act Work, A.2.8 and A.2.8.PER for the commitment or grant, and A.15.1 only to identify the dated Work occurrence. An application result, production, delivery/transfer, acceptance, and evidence use each follows its own row in A.15.1:4.6 and is omitted when that claim is absent. F.18 only names recovered terms when durable naming is current.

  4. Effect claims without an actual occurrence. A description, diagram, log or metric can state or support an effect claim. Establish the actual occurrence under its subject pattern. Use the Work conditions in 4.1 when a dated Work is claimed; natural, spontaneous or formal change can use A.3.4 without a Work claim. Name any observation used as evidence and obtain the support needed by the receiving use through A.6.B:5.4.

These confusions can defeat substitution behind a stable signature: an implementation change may unexpectedly alter a hidden gate, duty or evidence requirement. Make each applicable constraint recoverable under its own claim.