A.6.C:7 — Conformance Checklist
Preface node
heading:a-6-c-7-conformance-checklist:16365
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
A boundary description conforms to A.6.C iff it satisfies all items below:
-
CC‑A.6.C‑1 (Four questions, atomic answers). When contract-like wording leaves a consequential ambiguity, the text SHALL answer only the applicable four-question branches with atomic claims. Each asserted object and its subject predicate SHALL remain separately recoverable. Classify each claim through A.6.B and identify the defining pattern when its rules govern that claim. Where a conclusion about an order depends on several undertakings or acts, the account states which connection the governing terms require and the grounds for applying it, or identifies the connection that remains open.
-
CC‑A.6.C‑2 (No agency to epistemes). When a dated act or individual commitment is claimed, the text MUST identify its capable actual participant and MUST NOT substitute an API/interface label, description, publication carrier, kind, or assignment for that participant's basis. Ordinary metonymy may remain when its participant and relation are locally recoverable.
A generic prescription SHALL name its normative source and applicable content without inventing an individual bearer.
An individual duty or commitment SHALL name its actual bearer and separately obtaining
U.Commitment; an assignment may appear only as an instituting rule's applicability ground. -
CC‑A.6.C‑3 (Classify contract-language statements via A.6.B). When contract-language leaves a consequential ambiguity, its unpacked statements SHALL be atomic L/A/D/E claims. In that unpacking, permission-looking wording SHALL select one A.6
A6-AW-*row; A.2.8.PER membership alone MUST NOT set the quadrant. -
CC‑A.6.C‑4 (Promise content ≠ Work discipline). A statement about one dated Work SHALL name the A.15.1 occurrence. A result, production, change, delivery/transfer, evidence or acceptance statement SHALL use its own direct object and shall not be inferred merely from Work. Promise-content language remains about
U.PromiseContent. When service or access-like wording occurs in a relied-on boundary claim, recommendation, decision, gate, assurance, publication, or reuse and hides the concrete subject, participant, predicate, kind, permission, Work occurrence, or next subject question, the text SHALL recover that hidden choice through E.10 L-SERV and A.6.P:4.11a, then state the assertion under the recovered predicate with its pattern locator. Quoted, historical, illustrative, and harmless ordinary wording remains outside this recovery rule; an actualU.PromiseContentreferent still uses the head phrase promise content, not bare service. -
CC‑A.6.C‑5 (Evidence hook for operational guarantees). When a “guarantee” expresses an operational claim, the text SHALL state the E claim’s predicate, object, relevant scope or window, and what establishes it or remains missing. Name Work, evaluation or observation when the claim depends on it. If required grounds are missing, retain the claim as unresolved; report a negative result only when the grounds establish it.
For evidence use, the text SHALL keep the grounds required by receiving reliance recoverable under §4.1, question 4; use A.10 when a replayable account is needed and identify carriers or observation conditions when they affect the claim or use.
-
CC‑A.6.C‑6 (No second contracts via faces). MVPK faces MUST NOT add new boundary claims; they publish only the existing canonical L/A/D/E claims under E.17. Informative commentary may explain those claims without adding boundary semantics. An asserted
U.Viewseparately requires E.17.0 conformance. -
CC‑A.6.C‑7 (RFC‑keyword discipline inside faces). Each MVPK face sentence containing a BCP-14 keyword MUST cite its classified claim ID or canonical location, direct object, and selected
A6-AW-*row when permission-looking. Only norm/grant claims cite D; gate claims cite A; exercise and evaluated findings cite E. -
CC‑A.6.C‑8 (Obtaining is not representation). A
PublishorApproveutterance, a document, carrier, or record does not by itself institute or prove aU.CommitmentorGrantedPermissionRelation@Context. The obtaining predicate and cited context policy decide whether the relation obtains.A Claim Register row may assert or support reliance on it only when the row names the occurrence, predicate,
SubjectPatternLocator, participants, scope/window, and current evidence required by that use.For a commitment, the row cites its rule-required actual instituting basis and policy; for a strong grant, it cites the actual instituting speech act and policy. The row alone does not create the relation.
When the grant occurrence is the row's direct object,
directObjectDesignationSHALL be aU.RelationRefconstrained toGrantedPermissionRelation@Context; an entity reference,ClaimAddress, display label, or arbitrary identifier cannot fill that branch.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)