Practical-Use Cards
Preface node
heading:practical-use-cards:760
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
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.TUfor application construction.B.5.RCandB.5.RAsupply construction and argument recovery,A.6.3.RTan operative expression, andC.29.1result transfer. UseC.39for 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.MPCto connect available contributions and select the missing one.C.29constructs mathematical correspondence;C.29.1tests result transfer;C.29.2constructs computation;C.29.3connects 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.30for an architecture question,C.30.ADfor its description,C.32orC.32.PADfor a design choice, andC.32.P2Sto 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; useE.23.CDI,E.23, orC.36only 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.0to choose a viewpoint for the reader's work or check view conformance. UseE.17.1/E.17.2for reusable bundles,A.6.3.RTfor representation changes,C.33for structure,E.17.ID.CRfor comparing sources andC.30.ADfor 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.DUAfor a demand's contribution or feasibility;C.38for incomplete ways; otherwiseA.19.ECS,C.18,C.19,G.5orC.11for the current question. For costly commitment, select the current check inA.10,B.3,A.20,A.21,C.28,C.11orA.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.1to preserve cues,B.4.1to direct inquiry,B.5.2.0to frame a question about explanations andC.22.2to formulate a ProblemCard. UseC.22.PFRto 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, andE.23as 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; useE.10for unresolved FPF wording, andF.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.2for source comparison. UseC.18,C.19orG.5for options. For framework authoring, develop the practitioner’s explanations underE.4.DPF. UseE.4.PFADfor a product choice andE.9for 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, andC.13; useC.11,C.32.PAD, the direct relation pattern, orA.22only 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)