Practical entries

Preface node heading:practical-entries:616

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

Bring a working question, or use an ordinary occasion to discover what is worth asking. USING-FPF.md explains how to find an individual method or a connected application. The entries below illustrate the range. Search the Table of Contents or ask an assisting agent to compare plausible candidates. If unfamiliar wording or limited access hides what you need, F.1:4.4 explains how to locate passages you can inspect and describe any remaining gap. Stop the lookup when a known source suffices.

The ordinary examples start with one pattern and give any conditions for a later use. You can stop as soon as a result answers your question. A mantra can help you find a missing contribution. The Practical-Use Cards recall connected reasoning explained in the Methods.

A mantra can also reveal a consequential gap before you notice a difficulty. B.5.PI explains how to select one, apply its connections to a case and obtain a question or justified continuation. You can use this inquiry outside a project. A.1.STM applies it to systemic project reasoning and also traces an already noticed difficulty back to the use that gives it significance.

To find which costly or unavailable work deserves improvement, use C.39.WI. Follow one consequential result, compare real alternatives and their complete burden, and distinguish a missing way from an explanation, access, provision or execution problem. The first result can be a warranted improvement undertaking, a retained possibility or a reasoned decision to continue current practice. An already understood, worthwhile and authorized remedy can be performed directly.

When choosing what to investigate, explain or change, or bringing a local result back to that work, use C.39.QR. Identify what could have the property or undergo the change the recipient asks about. A supplied example may give access to that subject. Work out what its use would establish and follow the result through to the original question. Then obtain the missing contribution or settle the qualified result. When the requested contribution is an explanation of a whole subject, C.39.WA develops its organizing grounds and connections and shows how they guide choices about parts. Examples make these operations concrete; varied cases reveal differences within the stated range.

LIVE-WORK-STEERING — Choose the next action while Work is changing

  • Situation: Ongoing Work has an applicable domain Method, but a current fact can change what should happen next.
  • Question: What should the deciding System choose now, who will perform it, and when must they stop or look again?
  • First useful result or blocker: One bounded decision, intended performer, and feedback condition—or a named blocker due to missing or outdated action-guiding information, authority, capability, safety, applicability, or no current Work.
  • Start with: A.15.7.
  • Stop or return: Stop when the action, performer, and nearest return condition are clear. If ongoing Work is blocked by a missing or unsupported performer, support, or continuation-state relation rather than by candidate choice, use A.15.8 to repair that configuration or stop, then return. If Work has not begun, use A.15.2 for intended-work content, A.15.5 for work-entry readiness, or C.11 only when a known chooser must compare an already formed OptionSet.

METHOD-RECOVERY — Explain what reusable way several performances may show

  • Situation: Several observations or records suggest a reusable way, but no Method has been established.
  • Question: What candidate explanation is supported, which rival explanations remain, and which uncertainty can change the intended use?
  • First useful result or blocker: One source-traceable provisional account per candidate with its rival explanations and relevant gaps—or a qualified record-only result. Include a useful distinguishing question when it changes recovery or receiving use; designing or undertaking a study is a separate choice.
  • Start with: A.3.1.MR.
  • Stop or return: Stop at the strongest supported account or lowering result. Continue to A.3.1, or to RMP.10 for a needed empirical programme or RMP.11 for a needed historical inquiry, only when that further use is current.

PROFESSIONAL-RESULT — Use one result from another practice without transferring the decision

  • Situation: A decision needs a legal, safety, tax, privacy, engineering, scientific, or other outside-practice result, but the available source or request names only a title, department, document, approval, provider, or tool.
  • Question: What does the available result support for this decision, and would an obtainable additional contribution warrant its whole acquisition burden?
  • First useful result or blocker: The supported answer with its necessary use limit, a worthwhile bounded result request, or an identified blocker involving the source, Method, capability, authority, access, evidence or applicability.
  • Start with: A.15.9.
  • Stop or return: Finish at the useful answer and its material limit; a remaining gap alone does not require a request. Select acquisition through A.15.9 when its contribution is worth obtaining. The supplier keeps its Method and professional authority; the receiver keeps the receiving decision.

NAMING — Give one identified thing a usable name

  • Situation: One already identified thing needs understandable wording; later use may also require a stable, reusable name.
  • Question: Does ordinary wording suffice, or which durable name preserves the thing and avoids misleading alternatives?
  • First useful result or blocker: Use ordinary wording when it suffices. Return a local NameCard only when reuse needs a durable name. If the wording or name cannot be settled, identify what is missing about the thing, use, reader group, scheme, sense or candidate evidence.
  • Start with: F.18 when the name must become durable. For one-off wording, keep the ordinary phrase and use the thing's direct pattern only if its meaning is unclear.
  • Stop or return: Stop without a card when ordinary wording answers the need; otherwise stop at the local naming settlement. Return when the thing, use, readers, scheme, or likely misunderstanding changes.

SYSTEM-RECOGNITION — Test systemhood only when it changes the decision

  • Situation: A decision may change if one identified entity is a System, while the same noun may instead name Work, a Method, capability, episteme, structure, or another subject.
  • Question: What decision depends on treating that entity as a System?
  • First useful result or blocker: Return to the non-system claim at issue; recognize or reject the System reading; or name the missing construction fact or test.
  • Start with: A.1.SCR.
  • Stop or return: Stop at that result or the identified blocker.

TIME — Determine what a timing claim establishes

  • Situation: Someone needs to explain how something changed, interpret a deadline or rhythm, or act on a trend or an aging result.
  • Question: Which subject, interval and time relation does the work depend on? If it concerns several contributions, how do their timing and connections affect the result?
  • First useful result or blocker: An interpreted state, rate, history or timing consequence, with the grounds it needs. A missing reference time, observation or dependency can leave a stronger conclusion open.
  • Start with: C.27 for the reach of the claim and C.27.TA for the windows, rhythm, cadence or currentness it depends on. Use G.11 when a change of basis may require refreshing an earlier result.
  • Stop or return: A supported reading can settle the question. If the recipient needs to explain a change or keep the work on time, carry that reading into the explanation or the way of working.

CAUSAL-USE — Explain an outcome or derive an intervention consequence

  • Situation: Someone wants an explanation of what happened, an estimate of what an intervention would change, or an assessment of a causal claim.
  • Question: Which outcome is at issue, for whom and when? Could different mechanisms account for the same observations while giving different explanations or consequences?
  • First useful result or blocker: A supported causal answer, a consequence conditional on the stated mechanisms, or the missing evidence or premise that would distinguish the live alternatives.
  • Start with: C.28 to establish what the observations and assumptions warrant. Use C.28.CM to construct or challenge an explanation and C.28.MR to derive the consequence of changing a mechanism.
  • Stop or return: An assessment can finish by establishing the limits of the evidence. When asked to explain an outcome or forecast an intervention’s effects, use the assessment to develop the explanation or forecast. Carry out the intervention if its performance is also commissioned.

MEASUREMENT — Make a number interpretable before relying on it

  • Situation: A proposed measurement needs a model, or a reading, score, rating or dashboard value needs interpretation before comparison or decision.
  • Question: What claim or model is needed, and which subject, Characteristic, Scale and rule give it meaning? For a measurement, how does the procedure produce an indication, and what can be inferred under its applicable unit, calibration, time and uncertainty conditions?
  • First useful result or blocker: A usable measurement relation or an interpretable attributed value with the uncertainty and use conditions its claim requires, or the missing contribution. A claim of performed measurement retains its observation and Work grounds.
  • Start with: C.16 for a measurement claim; C.16.P while the value's meaning is ambiguous; A.17/A.18 for a Characteristic or Scale question; A.19.CPM for comparison.
  • Stop or return: Stop when the model or value supports the present use. Return when its subject, governing rule, measurement conditions or use changes.

MATHEMATICAL-MODELING — Obtain a useful consequence from a representation

  • Situation: A working question needs a mathematical construction, or a proposed representation may omit something that changes the answer.
  • Question: Which situations must the answer distinguish? Choose quantities, objects and relations that preserve those differences. If several representations contribute, how do their results fit together, and which conditions must hold in the same case?
  • First useful result or blocker: A calculation, bound, construction, obstruction or distinguishing observation, with its interpretation; alternatively, the missing relation or operation.
  • Start with: C.29:4.1. Use an adequate local equation or algorithm directly when no representation question remains.
  • Stop or return: Stop when the consequence answers the present use. Return when a changed assumption, lost distinction or execution condition changes that consequence. Validate correspondence to a phenomenon when the intended reliance requires it under C.29:4.5a.

When the direct pattern is already known, open it: E.11.PFP for framework publication, E.11.DSG for the DPF Suite Reference when a question spans several DPFs, A.15.6 when project, process, or case hides the subject, A.1.1 for model-use organization, C.22.PFR for an actual-problem claim, and A.6.REL for an obtaining relation.

METHOD-CONSTRUCTION — Construct, connect and change methods for practical use

  • Situation: Relevant methods or operations exist, but their joining, explanation or adaptation is still missing for the work you need to do.
  • Question: How can I obtain the result, make the way usable by another practitioner, and change it without losing independently useful parts?
  • First useful result or blocker: One explained candidate way or connected account, its supported conditions and selective return after change; alternatively, the missing operation or basis.
  • Start with: C.39:4 supplies the general construction. Use a sufficient existing Method directly and stop. No framework authorship or pattern format is required.
  • Stop or return: Stop when the intended use has its adequate explanation. Reopen connections affected by changed conditions; retain independent uses whose conditions still hold.

For example, a corrected recording with a qualified movement–sound mismatch bound of 2.5 ms over the receiving interval meets the 3 ms tolerance for movement analysis and the 8 ms tolerance for viewing. Tightening the analysis tolerance to 2 ms reopens that branch without invalidating viewing. C.39:5.3 develops the preparation, its independent professional premises and that return. If the result must become a framework explanation, E.4.CM:5.4 shows the additional public-content and pattern-form decisions.

WORK-OPPORTUNITY — Find a useful continuation before proposing change

  • Situation: Work meets its present requirements, or you have useful material but no settled question about what to change.
  • Question: What result could matter here, and is finding or proposing another way worth the work it creates?
  • First useful result or blocker: A supported local possibility, a question worth resolving, a missing contribution you can identify, or continuation of the present work.
  • Start with: Use C.40 for material whose useful result is still open; C.39 when the result is known but its obtaining way is missing; C.11.DUA when a proposed change needs a value-and-burden judgement. Use adequate domain reasoning directly.
  • Stop or return: Stop at that first result, including no worthwhile advice. Reopen affected conclusions when their conditions change; existing obligations remain in force.

Start with a bounded piece of available work: for example, replay an order queue using its durations and delivery conditions, or compare how two recipients use the same result. Try a supported variation of an operation, order, contribution or use; say which consequence it could change. A different word or an unusual observation is a lead, not a diagnosis. If the needed way is absent, construct and explain a local operation or identify the basis it lacks.

Before proposing that variation, distinguish the larger work performed through the action from later work that uses its result. Use B.1.5.EW to recover unclear connections between the action, its constituents and the larger work, and B.1.5.RS when replacing the action can affect another use. Follow a later result handover separately when it can change the proposal. Stop following the connections when further detail cannot change this continuation on the available basis.

Compare with continuing as at present. Thinking, obtaining evidence, explaining the advice, deciding and making the change can burden different people and resources. Include already committed work and other proposed changes in the same interval: two worthwhile changes can exceed shared capacity together. DUA supplies this comparison and returns to C.11.CRC when a finite comparison is missing. Offer only the result whose contribution warrants that burden; explain its decisive conditions in the recipient's working language. A useful local answer can end the inquiry.

COMMUNICATION-FOR-USE — Make communication useful, then learn from what happens

  • Situation: A report, model, message, or answer seems clear, but its intended use and evidence are unclear, including whether its producer can use it later.

  • Question: Who should understand or do what with it, what evidence is enough, and what should change if that use is not achieved?

  • First useful result or blocker: A supported decision to keep or repair it, change prerequisites or a future use, or stop, with evidence, causation, and permission limits.

  • Start with: Use A.2.9 to evaluate the communication against what its recipient should understand or do. Distinguish the act of communicating from its wording and medium, and interpretation from response, later action, world change and causal contribution.

    Choose the repair by its object: A.6.3.CR for wording, A.6.3.RT for representation, A.6.3.NAR for narrative, E.17.EFP for explanation or E.24.PUB for publication. Use A.10, C.28 or C.11 when you need to establish evidence, causation or a comparison of repair options, respectively. A repair may change prerequisites, medium, interaction or future use. Check authority, consent and admissibility separately.

  • Stop or return: Stop when the named use has enough support or a blocker is explicit. Preserve the earlier intended use when interpreting the response; revise a future use when warranted. Response or silence alone proves neither meaning, success, causation, authority, consent, nor permission.

RESULT-TO-NEXT-MOVE — Route an obtained result to the next probe or option

  • Situation: A DPF or project calls something information gain, learning progress, or novelty, or has articulated a result from an earlier cue, and wants to use it to choose the next probe or option.
  • Question: What result actually exists, and which downstream question, if any, is current?
  • First useful result or blocker: The obtained result plus the first needed reliance disposition, characterization, possibility-space claim, configuration-relative comparison, ChoiceResult, or missing basis.
  • Start with: Name the obtained result and use its direct pattern. Use E.10.LRN when learning hides the result; separate ambiguous claims and return each to its direct pattern. Continue to A.10 only for actual reliance, C.17/C.18 only for characterization or space change, C.11.CRC only for a missing finite realizable-configuration comparison, and C.11 only for a live choice.
  • Stop or return: Stop when the present question is answered. Observations, objectives, and characterizations retain their identities. Route the result articulated from a cue through its direct pattern; if its A.16.1 cue pack remains current as a source or provenance, retain it separately.

ACTUAL-TEMPORAL-STRUCTURE — Recover what actually obtains before testing coordination

  • Situation: A cycle, onset list, trace, notation, or geometry is called rhythm, but may be a prescription, representation, Method unfolding, or account rather than what obtains.
  • Question: Which subjects and relations support the selected structure, what grounds it, and is a coordination trial useful now?
  • First useful result or blocker: A supported temporal claim, or the missing bearer, relation, observation or ground. Establish an A.22-selected structure or a separately identified C.2.1 account when the receiving use needs it. Keep future specifications and representations separate. For a selected coordination trial, add direct relations, conditions, observations, and next decision or stop.
  • Start with: Begin with the changing subjects and the temporal claim needed for their use; C.27.TA supplies its conditions. Use A.3.4 or A.15.1 for a needed change or Work claim, A.22 when the organization requires a selected structure, and C.2.1 when its account needs separate identity. Preserve the distinctions among structure, account, future specification, representation, Method unfolding and Work. For coordination, name bearers and direct relations. Only when a trial can change the decision and warrants its burden, compare feasible interventions, try one within bounds, observe, then decide or stop. Open specification, representation, decision, causal, trial or domain patterns as their questions arise.
  • Stop or return: Stop when answered. Return when bearer, relation, constraint, grounding, intervention, or use changes; domain Methods stay in DPF.

CONSEQUENCE-BEARERS — Find omitted Systems before closing a decision

  • Situation: A change may reach a System outside the project, or someone needs to know how far an existing finding extends.
  • Question: Which Systems may be affected, and does the recipient need one possibility, the complete set within stated bounds, or a decision about several Systems together?
  • First useful result or blocker: A qualified finding the recipient can use. A supported possibility may justify retaining an alternative. A rule that decides inclusion for the entire domain can establish a complete class or an empty list. To return a named list, recover its members’ identities. A bound on joint demand may settle a shared limit. State what remains open.
  • Start with: Use A.1.CSD to recover the focus, decision, criterion and intended scope. Vary the surrounding use and the distribution of a reported total. Keep established relations, possible paths and actual changes distinguishable. Use A.1.SCR for a material question of systemhood and the direct domain method for any needed measurement, comparison or causal claim.
  • Stop or return: Return a useful account with its material limit; it may change or hold open the named decision or investigation. Reopen when the focus, configuration, horizon, whole, relation support, bearer, observation, or receiving use changes.

Practical-Use Cards

Each card offers an optional route for extended work. Use the keys to find cards. Choose a card by the situation and intended result, then use the contributions that work requires. Finish when the result answers the question. If it supplies one premise or identifies a missing contribution, establish what remains to reach that answer.

UNFAMILIAR-THEORY - Make an unfamiliar theory usable

  • Situation: A theory offers a useful construction or result, but you cannot yet assemble and interpret its application to your question.
  • Question: How can you obtain the needed consequence and use it?
  • First useful result or blocker: An interpreted result for the situation or class the question concerns, or the missing operation, premise or correspondence that directs the next contribution.
  • Mantra: Begin with the question the theory is to answer. Relate its objects and rules to the particular situation or to the class of situations at issue. Use the construction or argument that establishes the needed consequence. If the representation changes, compare the corresponding operations. Carry the consequence back to the question and identify what it settles.
  • Start with: B.5.TU for application construction. B.5.RC and B.5.RA supply construction and argument recovery, A.6.3.RT an operative expression, and C.29.1 result transfer. Use C.39 for a missing way.
  • Stop or return: An adequate supplied result can enter where needed. Stop when its interpreted consequence answers the question. If a premise changes, follow its effect instead of repeating unaffected work.

PHYSICAL-RESULT - Connect physics, mathematics and computation

  • Situation: A team needs to connect its physical, mathematical and computational work to answer a physical question.
  • Question: Which contribution is needed to answer the physical question?
  • First useful result or blocker: A physically interpreted result, a proposed realization, or an identified gap in the physical account, computation or execution.
  • Mantra: Start with what you need to explain, predict or change. Choose the physical state and relations the answer depends on. Interpret the argument or computation in those terms. For an actual event, establish what its conditions and evidence warrant.
  • Start with: B.5.MPC to connect available contributions and select the missing one. C.29 constructs mathematical correspondence; C.29.1 tests result transfer; C.29.2 constructs computation; C.29.3 connects it to an executing system. Use the relevant physical knowledge for the laws and mechanisms.
  • Stop or return: Reuse ready contributions. Finish when the result meets the commission. A model can answer an explanation or design question. If a working implementation or a new run was ordered, complete that work under the agreed conditions. For a question about an earlier run, use sufficient evidence about that run. Reopen contributions whose changed conditions affect their use.

Expansion for PHYSICAL-RESULT

Divide the work. Give the next participant the result, what it denotes and the assumptions needed to use it. For the robot in B.5.MPC:5.1, the physical contribution supplies the motion model; the mathematical contribution relates distance to motor increments; the computational contribution produces an integer command and its rounding bound; the realization contribution checks what that command makes the controller do. People and AI agents can take these contributions according to their capabilities.

Use A.3.3 to construct a missing state account and C.16 for a needed measurement relation. These are dependencies between results. A ready model or computation can be reused at its point of need. Slip may call for revising the motion model; numeric overflow may require another command representation; a timing change may require a different execution arrangement. A calculated displacement remains conditional on the model until actual motion is established.

ARCHITECTURE — Carry an outside need through structure and feedback

  • Situation: Someone needs to understand how a whole is organized, choose a workable structure, or change what happens in use.
  • Question: What must the architecture explain, establish or make possible in the recipient’s work?
  • First useful result or blocker: A grounded account of the relevant connections, a justified design choice, or the missing condition that changes the answer.
  • Mantra: Start from the effect or question. Identify the whole, its relevant constituents and their connections. Trace how they produce the property in question. Compare arrangements when a choice is open. For a change, follow the work through to its agreed result.
  • Start with: C.30 for an architecture question, C.30.AD for its description, C.32 or C.32.PAD for a design choice, and C.32.P2S to carry a need through architectural change.
  • Stop or return: Give the requested explanation or grounded choice. For a change, establish what was commissioned: installation, capability under agreed conditions, or actual use.

PRACTICE-ARCHITECTURE — Connect methods with their use, support and development

  • Situation: Understanding or changing a practice requires connecting the Methods, Work and arrangements that supply their results.
  • Question: What makes the methods work together, and which connections can change while the practice still delivers?
  • First useful result or blocker: An account of how the practice holds together, a workable design, or a missing connection that affects the requested result.
  • Mantra: Follow the needed result across contributions. Distinguish operations of the same Method, results supplied by other methods, and Work that uses them together. Trace what would sustain the result after a replacement the practice allows. For an actual performance, follow the contributions that were used.
  • Start with: C.32.MWA; use E.23.CDI, E.23, or C.36 only when the decision raises the corresponding question.
  • Stop or return: Return the explanation, design or finding about practice that the recipient needs. Reopen the connections affected when contributors or conditions change.

WORKING-DOCUMENTS — Make a document support its intended uses

  • Situation: A document is requested, but its label does not reveal the use it must support.
  • Question: Do you need to check one view, reuse related views, show the same subject differently, see enough structure, compare named sources, or use an architecture description in a decision?
  • First useful result or blocker: A checked view, a reusable viewing approach, another presentation of the subject, an account of sufficient or missing structure, a source comparison, the architecture-description result needed now, or the specific obstacle to obtaining it.
  • Mantra: Start from each recipient’s work. Choose the claims, relations and form it needs. One account can serve several users. Compare the relevant features on a common basis. For joint operation, check that the conditions can hold together. For rival accounts, trace what follows under each. Distinguish the document, its subject, decisions and performed Work.
  • Start with: E.17.0 to choose a viewpoint for the reader's work or check view conformance. Use E.17.1/E.17.2 for reusable bundles, A.6.3.RT for representation changes, C.33 for structure, E.17.ID.CR for comparing sources and C.30.AD for architecture descriptions.
  • Stop or return: Stop when the requested uses have the accounts or decisions they require. Return when a use or the content changes.

OPTION-COMPARISON — Keep unlike option results distinct

  • Situation: Labels such as build, buy, reuse, provider, internal, outsource or AI need comparison; uncertainty blocks costly commitment; or advice demands costly or infeasible work.
  • Question: Do you need to form complete ways, compare or retain candidates, govern a pool, prepare options for another chooser, choose now, or repair an evidence demand?
  • First useful result or blocker: A sufficiently developed set of ways to obtain the same result, comparison or retained set, pool rule, prepared OptionSet, ChoiceResult, usable advice, answer to the blocking question or exact gap.
  • Mantra: Establish what the chooser must obtain, the alternatives in the commission and their conditions of use. Develop a label into a complete way when the comparison needs it. Compare like contributions on a common basis. For joint commitments, check that the promised results and their resource demands fit together. Keep worthwhile variants and consequential uncertainties visible. Return when a changed premise matters to the choice.
  • Start with: C.11.DUA for a demand's contribution or feasibility; C.38 for incomplete ways; otherwise A.19.ECS, C.18, C.19, G.5 or C.11 for the current question. For costly commitment, select the current check in A.10, B.3, A.20, A.21, C.28, C.11 or A.15.5.
  • Stop or return: Stop at the present question's result.

PROBLEM-SHAPING — Formulate the problem the work needs

  • Situation: A difficulty or opportunity has appeared. A colleague wants it investigated or has commissioned a particular result.
  • Question: Whose work is affected, under what conditions, and what would count as addressing the difficulty or realizing the opportunity?
  • First useful result or blocker: A formulation the recipient can use, a signal worth keeping, a question that distinguishes explanations, or the information still needed.
  • Mantra: Start with what the recipient is trying to accomplish. Trace the observation to the condition that matters for that work. Consider another interpretation of the same observation. What would change the problem or its criterion of improvement? Give the supported formulation. If only a signal is established, identify what could connect it to the problem.
  • Start with: A.16.1 to preserve cues, B.4.1 to direct inquiry, B.5.2.0 to frame a question about explanations and C.22.2 to formulate a ProblemCard. Use C.22.PFR to establish whether the conditions for a particular subject actually violate the criterion that applies to it.
  • Stop or return: A cue can complete a request to report what was noticed. Return the formulation to the work it was meant to support. If a deliverable has already been agreed, use the formulation to guide its production.

IMPROVEMENT — Define better before repeating change

  • Situation: A team wants to improve something but has not agreed what better means or how the changed version will be checked.
  • Question: Which evaluation question, characteristics, scales, changes, and comparison make improvement reviewable?
  • First useful result or blocker: One evaluation question, current assessment, bounded change, before-after comparison, or the missing use, evidence, scale, or trade-off.
  • Mantra: Name the entity, current state, and use that better must serve. Frame the question before choosing metrics; select characteristics, scales, and protected trade-offs; assess the current state; compare candidate changes; make only the supported change; evaluate it on the same basis; continue, stop, or change direction from that result.
  • Start with: E.22, A.19.ECS, C.16, and E.23 as their questions become current.
  • Stop or return: Stop at the first missing prerequisite or useful comparison. Reopen when the entity, use, evidence, or scale changes.

WORDING — Repair language without replacing the project question

  • Situation: A load-bearing sentence hides the subject, relation, kind or use, or invites a false inference.
  • Question: What should the reader understand and do, and which distinctions matter for that use?
  • First useful result or blocker: One plain repaired sentence, direct clarification, local naming result, or the missing subject, sense, test, or reader use.
  • Mantra: Recover the ordinary project sentence first. Name what it is about, what it claims, and who must use it; add ontological distinctions only where they change truth, understanding, or action; choose a durable name only when later use needs one; rewrite in plain technical language; check that a reader without private context can recover the intended claim and action; retain a guard only under F.19's full grounded-contribution test; return to the domain task.
  • Start with: F.19; use E.10 for unresolved FPF wording, and F.18, F.0.1, F.9, or the subject's direct pattern only when needed.
  • Stop or return: Stop when the reader can understand the claim and carry out its intended use.

SOTA-PORTFOLIO — Compare approaches that could answer your question

  • Situation: Your team needs to know what competing approaches can establish and where each applies.
  • Question: What can the sources already answer, and what work remains?
  • First useful result or blocker: A comparison linking each claim to its source, edition, evidence and limits. State where the claims can be compared, what remains disputed and which part of your question is open.
  • Mantra: Fix the inquiry and freshness needed. Compare claims, methods and grounds. Keep consequential disagreements. Use the comparison if it suffices. For a remaining need, consider reuse, a contribution, another product or maintained guidance. If a DPF or LPF is warranted, develop and test its patterns and revisit them as evidence or use changes.
  • Start with: G.2 for source comparison. Use C.18, C.19 or G.5 for options. For framework authoring, develop the practitioner’s explanations under E.4.DPF. Use E.4.PFAD for a product choice and E.9 for its decision record when needed.
  • Stop or return: Stop at the comparison when it answers the commission. For a usable practice or framework, carry the grounds into its construction and check what the practitioner can do. Recover a source construction lost in translation through FPF.Reference:16.5.

SYSTEM-DELIMITATION — Separate parts, selected boundary, and crossings

  • Situation: One System is recognized, but a decision mixes its parts and assembly with a chosen boundary, external participants, and relations that cross it.
  • Question: Which facts, use-relative choice, crossings, and selected structure answer the decision?
  • First useful result or blocker: One exact part or assembly fact, boundary choice, crossing relation, selected structure, or missing participant, predicate, constraint, or use.
  • Mantra: Start with the recognized System and decision. Recover parts and assembly as facts; keep external participants outside the part list; choose a boundary only when alternatives matter; name every crossing by its own relation; select a joint structure only when organization changes the decision; reopen when identity, facts, use, crossings, or constraints change.
  • Start with: B.1.2, A.14, and C.13; use C.11, C.32.PAD, the direct relation pattern, or A.22 only when needed.
  • Stop or return: Stop when the result answers the decision. If system recognition is unresolved, return to A.1.SCR.

Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)