#How to Use This Repository

Preface node heading:how-to-use-this-repository:712

#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

Start with the practical-use card that recognizes the current project question. If several fit, compare their situations, first-result differences, and stop or return conditions before inspecting the selected direct pattern.

Use the Preface for the cross-cutting ideas and the repeated-use explanation. Use the Table of Contents when you already know the pattern family or need a search-oriented overview. Use the direct pattern body for the governed Solution. Once one direct pattern is current, use E.11.PUA to follow its Solution: identify the smallest independently governed result usable now, or stop and name the missing direct basis. Name a receiving use only when an actual continuation or later reliance is current. Use E.11.PUR only when a named receiving use needs an addressable applicability finding, recommendation, coordination, or ordering relation. Use extended cases when the compact card and direct pattern are not enough.

If you use an AI assistant, attach or index FPF-Spec.md and ask for plain-language project help first. Let internal pattern names enter the conversation only when they make the reasoning more precise.

A good first prompt is:

You have the FPF specification as a file.
Help me with this current project question:
[short project description and question]

Use plain language for engineer-managers.
Compare the relevant semantic practical-use cards when several fit:
ARCHITECTURE, WORKING-DOCUMENTS, OPTION-COMPARISON,
PROBLEM-SHAPING, IMPROVEMENT, COSTLY-ACTION, TIME,
CAUSAL-USE, DESCRIPTION-USE, NAMING, WORDING,
MATHEMATICAL-MODELING, SOTA-PORTFOLIO, DPF-AUTHORING,
or SYSTEM-IN-CONTEXT.

Then inspect the selected direct pattern and give:
- the current EntityOfConcern and practical question;
- the pattern and Solution selected under the current condition;
- the exact kind of first useful result and how its direct pattern would identify it or make its relation obtain;
- the exact method, plan, dated Work, transformation, evaluation, decision, or other governed use-object that result would answer;
- the relation, application binding, or supported local claim that would make it the result for that object;
- what it lets us do next, but only if that continuation is current;
- the exact missing governor or information when no truthful result can yet be promised;
- where to stop or return when a stronger claim becomes current.
Keep comparison conversational unless a named receiving use relies on an addressable record.
Do not turn the card into a whole-project plan.

Last Updated: 2026-07-29 — upstream FPF commit 2ada4136 (github.com/ailev/FPF)