A.6.C:8 — Common Anti-Patterns and How to Avoid Them

Preface node heading:a-6-c-8-common-anti-patterns-and-how-to-avoid-them:12106

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

Anti-patternWhy it failsRepair
Interface-as-promiser (“the API promises…”)Epistemes and publication carriers are descriptions; they do not commitRecover the exact policy and generic prescription, or name the actual duty bearer and separately obtaining U.Commitment when an individual duty is claimed. Keep any assignment as a rule ground and the API, signature, or interface description as a description episteme or publication carrier.
Guarantee-without-substrateThe word hides whether the claim is semantic, deontic, an entry condition, or observed or evaluatedClassify semantic law as L, a generic prescription or claim about an exact individual commitment or current grant as D, an entry predicate as A, and an observed or evaluated claim as E; use A6-AW-* for permission-looking wording.
SLA smuggled into lawsMixes governance with semantics; breaks substitution reasoningPut SLA targets as D claims referencing L-defined metrics and E evidence
Gate written as obligationConfuses admissibility predicates with deontic claimsWrite the predicate as A; write a generic prescription or separately instituted individual duty as a D→A reference.
Work-result-evidence bundle“The delivered work and its log prove acceptance” makes one phrase carry occurrence, result, transfer, evidence, and verdictName the A.15.1 Work first; then use one A.15.1:4.6 row for each current result, delivery/transfer, evidence, or acceptance claim. Omit absent rows.
Face-level paraphrase driftA face silently changes a claim's object or quadrantCite the canonical claim ID, direct object, and selected A6-AW-* row rather than restating it
Cross-scale contract collapseCommitments, grants, and conflict findings at different scales are treated as one D claimKeep commitments and current grants as separate D claims; classify the permission conflict finding as E through A6-AW-CONFLICT; use mediation only under its subject pattern

Last Updated: 2026-09-03 — upstream FPF commit b999972c (github.com/ailev/FPF)