A.6.B:1 — Problem frame

Preface node heading:a-6-b-1-problem-frame:15186

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

Boundary descriptions routinely mix four distinct claim families: definitions are written as obligations, runtime gates are hidden inside laws, governance talk is assigned to “the interface”, and operational-result “guarantees” are asserted without the actual Work, evaluation, or observation needed to settle them. This makes substitution unclear and leaves apparent auditability without claims that can be adjudicated.

The classification connects the strata already distinguished in FPF: Signature and Mechanism; the EntityOfConcern, claim-bearing episteme and carrier; and views under viewpoints. It lets a reader identify each claim, how it is settled and which other claims its use depends on.


Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)