FPF Reference

    A.6.P:1 — Problem frame

    Preface node heading:a-6-p-1-problem-frame:12247

    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

    FPF repeatedly encounters a predictable precision failure mode:

    Authors describe a situation with an apparently simple relational phrase:

    • “X is the same as Y”, “X is linked to Y”, “X is synced with Y”
    • “X depends on Y”, “X is grounded/anchored in Y”
    • “X maps to Y”, “X aligns with Y”, “X is connected to Y”
    • “X supports Y”, “X is supported by Y”, “X gives support for Y”

    …but the intended meaning is actually:

    1. Hidden multiarity. The claim requires additional participant positions: scope, time selector, witness carriers, policy, direction or inverse, reference scheme, representation scheme, mediator publication form, or mediator carrier.
    2. Kind elision. The umbrella verb stands in for an unstated set of relation kinds (different invariants; different admissibility; different evidence, source, or authority requirements).
    3. Viewpoint fights. Different stakeholders describe “the same” relation from incompatible viewpoints, creating polarity flips and silent re‑typing.
    4. Unnameable change semantics. Authors say “update/bind/anchor/sync”, but mean distinct semantic change classes (retarget vs revise vs rescope vs retime vs witness refresh).
    5. Regression via prose. Even after ontology repairs, umbrella language re‑enters and collapses distinctions unless structural precision is coupled to lexical guardrails.
    6. Pronominal/metonymic endpoints. Even when the relation verb is fixed, endpoints may be referred to via pronoun‑like or umbrella tokens (or metonymic pointers), so the relation cannot be typed or audited until endpoint facets/kinds are restored from context.

    A.6.P defines a repeatable precision restoration recipe that makes this defect repairable and reusable across additional admitted A.6.x patterns.

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