FPF Reference

A.6.P:1 — Problem frame

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

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”

…but the intended meaning is actually:

  1. Hidden multiarity. The claim requires additional participant positions (scope, time selector, witness carriers, policy, direction/inverse, reference scheme, representation scheme, mediator artefact).
  2. Kind elision. The umbrella verb stands in for an unstated family of relation kinds (different invariants; different admissibility; different evidence burdens).
  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 future A.6.x patterns.