FPF.Reference:1.1 - Four ordinary starts before a PatternID
Preface node
heading:fpf-reference-1-1-four-ordinary-starts-before-a-patternid:1097
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
Sometimes the obstacle is not choosing among pattern titles. A familiar phrase already hides the subject that the next claim needs. The four direct starts below are independent: use those needed by the current question and stop when its answer suffices.
- “We need to refer to the relation that holds, and perhaps to tell one episode from another.” Name the actual participants and state the relation in ordinary language, using the participant meanings, obtaining predicate and applicability needed to make that statement accurate. If a readable assertion that the relation obtains is enough, stop there. Only when later history, comparison, another relation, or an operation application must distinguish repeated occurrences should an agent use
A.6.RELwith the relation's same-versus-new-occurrence rule and return one recoverably individuated occurrence. If exact recovery finds no current direct relation for the needed claim, use theA.6.RCDmissing-basis disposition; missing participants, facts, predicate, identity rule, or establishedmissing-governorresult remain explicit blockers. - “The project, process, or case report no longer tells us what the decision is about.” Use
A.15.6to recover the subject. An actual project is one qualifying compositeU.Work; a process question concerns one reusableU.Method, one exact selectedU.Structure, or oneTransformationFlowStructure; a case follows one exact affected referent or claim through only the change history and closure basis needed now, while naming one later use that remains outside the closed case. When a source says target system, recover whether it means the product System of an extended enterprise under A.1.STM:4.1. Use system-of-interest for that role in the resulting English account. Keep an intended future system in a plan or description, and keep plan or decision designation, actual work-to-system facts, system-role-kind interpretation, and system-role assignment as separate claims. Stop when the direct subject and bounded claim answer the decision; if systemhood of the recovered entity still matters, the neighboring exit isA.1.SCR. - “Someone drew or named a bounded context, but we do not yet know what organization the decision may rely on.” Use
A.1.1to identify the model edition and the place or entity about which it is used. Recover the relation needed for the decision: where the model applies, how it is actually used in assigned Work, or whether a concrete expression agrees with the model's fixed content. Select the optionalBoundedModelUseStructureunderA.22only when their joint organization changes the decision and its exact constituents, obtaining relations, applied constraints, and named selection-use frame are all present. Otherwise stop at the direct relation or state the missing discriminator. The selected organization is a Structure rather than a holon; its model, participants and descriptions remain distinct.Context Mappingremains aU.Method, and a cross-context organization needs its own selection. If the real question concerns an episteme under a viewpoint, the neighboring exit isE.17.0. - “We have a problem card, assessment, or serious concern, but do not know whether an actual problem exists.” Use
C.22.PFRto check whether an actual condition is adverse under the predicate applicable to the named entity, scope, and interval. An obtainingProblematicForRelationrelates one exact actual-condition occurrence and one exact criterion-applicability occurrence whose selected input is actually adverse for that entity and use. A predicate, applicability occurrence, assessment, assertion, evidence posture,ProblemCard, forecast or modal concern, and current-solvability or continuation claim remain different objects. Stop with the supported actual-problem or non-adverse-condition judgement, or the exact missing condition, applicability, adverse input, or governor. If the useful object is instead reviewable problem-side formulation, the neighboring exit isC.22.2. One card may describe no actual PFR, and selecting a method changes current solvability or continuation, not the PFR's participants, obtaining, identity, or adverse condition.
Ordinary bounded use can remain conversational. Create candidate, fit, recommendation, closure or provenance records only when a named receiving use needs them. Such needs may include addressable comparison history, transfer between participants, automation, audit, durable reuse, delayed or expensive feedback, or costly reversal. The semantic schemas are reference models, not user-interface forms or serialization instructions.
The first useful result is one subject entity or obtaining relation under its defining or testing content and current basis. In ordinary use, name it in domain language; add a predicate, identity rule, assertion, pattern locator, ClaimGraph, or Method only when that distinction changes the truth, next action, stop, or named reliance. The selected pattern id locates action- or judgement-guiding content. The result may be a changed physical or clinical state, a capability, an episteme, a relation, dated U.Work, or another value. A note, measurement, dashboard, or card is the result only when producing that episteme was the intended result.
Keep three activities distinct: selecting a pattern, using its guidance to obtain a subject result, and later work that uses that result. Each can have its own result. Selection may remain a conversational judgement or, when later reliance needs it, produce a fit finding, recommendation or selected-candidate episteme.
The agent doing the work uses the selected pattern’s guidance to act or make a judgement. Identify a separate Method only when the Solution describes one and the current claim depends on its identity. Claims about a performer, assignment or dated Work require their own direct basis.
The subject result exists, or its relation obtains, according to its direct predicate, identity or occurrence rule, applicability, and case facts. A positive durable or reliance-bearing account additionally needs the appropriate current assertion and direct support. That result may later be used as an input, tool, context, constraint, or other needed participant in downstream subject Work without becoming the result of that later flow. Treat those positional words as ordinary cues, not relation kinds: name the source position, dependent-use position, and relation occurrence that the claim needs.
With no direct relation kind or predicate, return missing-governor; with undecided facts, keep the relation open; when the case fails the obtaining predicate, assert no occurrence; with an obtaining occurrence but a missing required endpoint binding, return missing-endpoint-binding.
Across these flows, a U.System may select, construct, refine or describe a U.Method, and plan dated work when preparation is current. If the account asserts a particular dated U.Work occurrence, first recover its exact performer through A.13 and let A.15.1 independently admit the Work. Stop there for a Work-only account. Only when the account or receiving use also consumes precise assignment-bound attribution should it name the covering assignment occurrence and its declared U.SystemRoleAssignment species, retain every identity-bearing participant, check holder equality with the already recovered performer, and establish the F.6 relation. Missing or failed F.6 attribution alone leaves independently grounded Work intact and lowers only the attribution. Recheck any consumed A.13/A.15.1 premise invalidated by the same finding and its dependent conclusions.
Public and project epistemes can guide that line. Use E.18 to recover each TFS-local position; use E.18.NET only when independently identified TFS values must be treated together as a network.
A quick three-way test is: same TFS, different valuation; one parent-relative internal portion, subflow; independently identified TFSs, network. A valuation assigns values under E.18 while the same A.22 selection O/R/C/F is retained; replacing a selected actual application or relation occurrence first reopens that identity. A subflow resolves its selected positions and internal relation occurrences in one parent TFS, retaining all required participants. A TransformationFlowStructureNetwork selects independently identified TFS or nested-network members together with exact obtaining relation occurrences whose participants are bound across their positions. DesignRunTag stays local to one exact position binding in one TFS; it is never a network-wide phase label. Use E.18 for a valuation or subflow, and E.18.NET for a network.
Repeat this use as the project changes: ask the current question, compare when needed, inspect a direct pattern description, use its action- or judgement-guiding content, retain the exact subject result and direct basis—or a stop when that basis is missing—and reconsider when a stronger claim, changed basis, or unresolved relation becomes current. Recover a separate Method identity only when the Solution describes one and the current claim depends on it.
A mantra is Plain didactic wording for a repeatable working reminder. It can help the reader find a consequential question before a difficulty is felt, recognize a relevant situation, recall a useful contribution and find the pattern that supplies it. A local mantra keeps one bounded result, often one pattern's contribution, in attention. A long mantra keeps connected reasoning across several areas of knowledge in attention: its questions, grounds, mutually constraining answers, alternatives and returns. It may connect several patterns or several relevant contributions within a larger account. The developed explanation makes those connections understandable; the short formula recalls them. A.6.P's reminder to recover a relation, its participants and its defining ClaimGraph is local; A.1.STM's map from outside use to recursive builders is long. Phrase length does not decide the scope.
A suitable mantra can open inquiry at an ordinary work occasion. Apply its connected questions to a current or possible case and examine whether the answers and conditions suffice for the intended use. B.5.PI:4.2.1 develops this selection, comparison and return: retain a useful answer, turn a consequential gap into a question, or preserve a cue while its meaning is unknown. A noticed difficulty can lead to the same grounds through inquiry. A.1.STM supplies the systemic project application; another inquiry can finish without a project frame.
For a group of jointly used patterns, a long mantra can be read as a compact statement of how their subject knowledge fits together. Readers need to understand why an answer constrains another, which answers must hold together, and what changes when a premise fails. A useful explanation may therefore need substantial connected prose as well as direct returns to full pattern bodies. Its phrases may address the patterns through their Problem frame or Problem, or through their Solution. A question can recall what remains unresolved; an action phrase can recall how to obtain the needed result. Both can point to the same pattern use. For example, these two formulations recall the same contributions to the report-review inquiry developed in §16.1:
Use whichever formulation the intended reader can recognize and apply. A pattern whose title names a difficulty can still be recalled through its Solution. Wording such as “find what the trial establishes” can state both the difficulty and the action intended to resolve it; clarify the difference only when it changes the next useful action.
A long mantra may arrange its contributions as a logical unfolding that makes their dependencies easy to follow. Preserve the order of justification required by the supplying Method: A.1.STM first considers receiving use, then moves from the system boundary to the larger whole and the joint functioning of its parts at the operating time. That account grounds the system's contribution before construction and creation are considered. Other Methods retain their own questions and relations. A selected happy path can help, but it is not the whole reasoning structure: material alternatives, shared constraints and returns remain part of the developed account.
This order constrains the reasoning used to justify a choice. The initial point of attention and the planned or performed Work order have their own grounds. Enter where the needed result is absent, stale, disputed or unsupported. Reuse an adequate result, return when its conditions change, and stop when the intended result is available. On a diagram, name the teaching use and the omitted branches or returns that matter to its intended use; return to the fuller account when those omissions can change the choice. A customer-journey mantra, for example, may show one route to useful product use while omitting a return from an agreed purchase to securing missing operating support.
Keep this reminder, the possible continuations it describes, a work plan and the observed work history distinct. A.22.CGUS applies when the underlying structure has the required constituents, relations, constraints, local loci and potential continuations; a shown traversal of a qualified structure may then be a DemonstrativeUnfoldingSlice@Context. Qualification concerns that structure, not whether its labels are questions or solution phrases. Ordinary local and long mantras require no formal CGUS qualification. Use A.1.STM when the difficulty concerns the system-thinking long map; use E.10.MOVE only when wording about a mantra move still hides the intended contribution or claim.
A pattern body is a pattern episteme containing its Solution, boundaries, checks, action- or judgement-guiding content and the definitions or constraints it asserts. It is a U.MethodDescription only when that membership is established and the distinction matters to the use. A claim about a project remains a separate subject assertion. Readme and Table of Contents references point to the relevant pattern passages and published term rows.
This reference explains how FPF’s practical uses fit together. It condenses, omits or defers individual pattern details, source publications, the history of their use and many relation records. When a decision depends on a claim explained here, consult the relevant pattern for the claim, its conditions and the omitted detail.
Use the Readme for ordinary examples, Practical-Use Cards and direct pattern locators. Use the Table of Contents to find a known pattern family or obtain a search-oriented overview. Read the pattern’s Problem frame and Solution. Recover a specific predicate, ClaimGraph or Method only when the current claim, action or named reliance needs that distinction.
The following Parts organize the published material for lookup. Kernel membership follows the defining content of universal meta-concepts wherever their patterns supply it. Other content can develop a method or state a constitutional requirement.
- Part A introduces foundational distinctions and their uses: holons, contexts, system-role kinds and assignments, capabilities, methods, work, time, scope, signatures, architecture, characteristics, measurement, comparison, and foundations for choosing from candidate sets.
- Part B gives transdisciplinary reasoning, emergence, evidence, assurance, trust, canonical reasoning, creativity, problem-side records and cues, and bridge discipline.
- Part C develops general patterns for characterization, measurement, mathematical modeling, architecture, temporality, causality, option portfolios, quality, problem shaping and precision restoration.
- Part D keeps ethics, conflict, and multi-scale value questions visible where they are live.
- Part E states FPF’s pillars and guard rails and gives guidance on pattern form, lexical precision, descriptions and publication, transformation-flow structures for carrying results through work, admission, review and design rationale.
- Part F gives unification and naming: local meaning units, concept sets, bridges, term sheets, local-first naming, and technical prose repair.
- Part G gives state-of-the-art work, option portfolios, option selection, benchmarks, shipping, evidence, bridges, dashboards, and refresh disciplines for reusable domain work.
- Supporting publication units can carry glossaries, expanded cases, annexes or other material when the pattern body is not enough.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)