FPF Reference

    A.6.B:10 — Conformance Checklist

    Preface node heading:a-6-b-10-conformance-checklist:8426

    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

    IDRequirementPurpose
    CC‑A.6.B.1 (Atomicity).A conforming boundary text SHALL decompose mixed sentences into atomic claims such that each atomic claim belongs to exactly one quadrant L/A/D/E.Makes L/A/D/E classification unambiguous; prevents contract soup.
    CC‑A.6.B.2 (Quadrant routing).Each atomic claim MUST be classified by the Boundary Norm Square and placed in its canonical stack placement (L→Signature.Laws; A→Mechanism.AdmissibilityConditions; D→Norms/Commitments; E→Evidence/Carriers).Preserves stack modularity and evolvability.
    CC‑A.6.B.3 (Form constraints).L-* and A-* claims MUST NOT contain RFC deontic keywords as operators; D-* claims MUST name an accountable U.Agent or U.Role; E-* claims SHOULD NOT use RFC deontic keywords.Keeps modalities separated and audit‑ready.
    CC‑A.6.B.4 (Explicit references).Where a claim depends on another L/A/D/E-classified claim, that dependency MUST be expressed by explicit ID reference rather than restating the other claim in new words.Prevents paraphrase drift across layers/faces.
    CC‑A.6.B.5 (E‑claim adjudicability).Each E-* claim SHOULD include (a) observation conditions, (b) carrier class/schema reference, and (c) viewpoint/consumer.Makes work‑effects adjudicable rather than aspirational.
    CC‑A.6.B.6 (No gate smuggling).Operational admissibility predicates MUST NOT appear as L-* laws in the signature layer; they MUST be A-* claims in the mechanism layer.Preserves substitution and signature stability.
    CC‑A.6.B.7 (No upward dependencies).L-* claims MUST NOT reference A-*, D-*, or E-*; A-* and E-* claims MUST NOT reference D-*.Preserves layering and prevents hidden coupling.

    Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)