A.6.C:2 — Problem
Preface node
heading:a-6-c-2-problem:16071
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
How can an author write (or repair) contract-language so that:
- Act and commitment claims name compatible participants, without mistaking an interface description for the actual interface or its bearer,
- Governance claims are distinguishable from permission-looking gate, exercise, evaluation, conflict, and source claims by the job of each atomic statement rather than by A.2.8.PER membership,
- Operational “guarantees” become adjudicable by recovering the claim, the facts its predicate requires, and the grounds for any receiving reliance; the answer may be a supported result or an unresolved claim with its missing basis,
- Multi-view publication (MVPK faces) does not create a parallel contract object or another canonical claim set by paraphrase drift?
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)