#A.6.P:2 — Problem

Preface node heading:a-6-p-2-problem:12269

#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 FPF represent and evolve “relations in prose” that are structurally richer than they appear, so that:

• the relation kind is explicit and reviewable,
• missing positions can be made explicit without semantic drift,
• changes to the relation can be narrated with stable semantic change classes,
• multi‑view publication can exist without creating multiple incompatible relation specifications, and
• cross-Context or cross-plane reuse cannot silently assume “sameness by label”?

---

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