FPF Reference

    Four direct starts when a familiar phrase hides the object

    Preface node heading:four-direct-starts-when-a-familiar-phrase-hides-the-object:481

    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

    These are four independent disambiguation routes before card-key comparison, not extra cards or steps. Use only the route matching the current sentence; each one returns a direct-pattern result or an exact blocker, then stops.

    • “We need to refer to the relation that actually holds.” Name the exact participants and direct relation, then open the pattern that owns it. A readable assertion is the smallest result when later work only needs to know that it obtains. Use A.6.REL only when history, comparison, another relation, or an operation application must distinguish one occurrence from another; apply the direct identity rule before naming or referencing it. Stop when the receiving use can use the assertion or individuated occurrence. If a participant, current fact, predicate, identity rule, or direct governor is missing, return that exact blocker. If exact recovery finds no current direct relation for the claim, exit to A.6.RCD; a row, edge, label, file, report, or identifier creates no occurrence.
    • “Project, process, or case wording hides what this decision is about.” Open A.15.6. Recover an actual project as qualifying composite U.Work; a process concern as one U.Method, exact A.22-selected U.Structure, or TransformationFlowStructure; or a case as one affected referent or claim plus only the governed change history and closure basis needed now, with one later use kept outside the closed case. The smallest result is that direct subject and bounded claim, or the exact missing basis. Stop when they answer the decision. If systemhood of the recovered entity still matters, exit to A.1.SCR. Treat target system as an ordinary cue for the exact project system-of-interest question. Keep intended systems, plan or decision designation, actual work-to-system facts, role interpretation, and role assignment separate; a project suffix, plan, team, dashboard, or case file identifies none of them.
    • “A bounded context was named or drawn, but its model-use organization is unclear.” Open A.1.1. Recover the exact model edition, use locus, and smallest direct applicability, assigned-Work use, or coherence relation first. Select optional BoundedModelUseStructure under A.22 only when the joint organization changes the decision and exact constituents, obtaining relations, applied constraints, and one selection-use frame are present. Stop at that relation or structure; otherwise return the exact missing discriminator. It is not a holon, subsystem, team, label, scheme, scope, viewpoint, view, representation, or diagram. Context Mapping is a U.Method and a cross-context organization needs its own selection. If the question is whether an episteme conforms to a viewpoint, exit to E.17.0.
    • “We have problem-side material, but may not have an actual problem.” Open C.22.PFR only for an obtaining ProblematicForRelation: one exact actual-condition occurrence plus one exact criterion-applicability occurrence whose selected input is actually adverse for the named entity and use. The predicate, applicability occurrence, assessment, assertion or reliance, ProblemCard, modal concern, and solvability or continuation claim stay separate. Stop with the ordinary actual-problem sentence or the exact missing condition, applicability, adverse input, or governor. If the need is a reviewable problem-side formulation, exit to C.22.2. One card may describe no actual PFR; selecting a method changes current solvability or continuation, not PFR participants, obtaining, identity, or the adverse condition.

    Last Updated: 2026-08-03 — upstream FPF commit 9dd92159 (github.com/ailev/FPF)