Decide Whether FPF Fits
Preface node
heading:decide-whether-fpf-fits:875
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
Use FPF when more explicit distinctions or connections would help keep the work coherent. Typical signs:
- several teams, experts, tools, or AI agents share reasoning about the same work;
- the real-world test is slow, expensive, noisy, risky, or politically hard to repeat;
- different readers need different reports, dashboards, explanations, or decisions about the same underlying work;
- names, roles, responsibilities, options, evidence, or quality criteria are starting to blur;
- the team needs a current view of possible approaches, not just one recommendation;
- a decision is small enough to make now but important enough to leave a durable reason.
When the task is small, feedback is fast and cheap, the vocabulary is stable, the decision will not be reused or audited, and a quick answer is enough, use that answer directly. Use only the framework guidance the question needs.
FPF can help people who need to keep work understandable across boundaries, including:
- engineers and systems engineers working with complex products or operations;
- researchers building claims for inspection or reuse by others;
- platform and AI teams coordinating humans, models, tools, and approvals;
- safety, assurance, compliance, and regulatory leads who need visible evidence and responsibility boundaries;
- managers and product leaders comparing options, budgets, risks, and delivery promises without hiding trade-offs.
Examples of use include:
- Human-only: use it as a writing and review discipline for meetings, notes, decisions, and technical documents.
- Mixed team: use it to keep specialists, managers, safety leads, and AI assistants aligned around the same work.
- AI-assisted: attach or index the specification, ask for plain-language project help first, and use pattern names only when they make the answer easier to check.
FPF can help with the evidence and decision questions that remain as AI becomes more capable. AI can generate fluent options quickly, but projects still need to decide what counts as evidence, which option is being compared, who may rely on an answer, when a claim is stale, what remains a guess, and what work is authorized. FPF helps make those boundaries explicit before the answer is used.
Core ideas in plain language:
-
first name the project object under concern; FPF calls it a holon when its actual construction supports treatment as a whole with parts and as a possible part of a larger whole; use
A.1to check a candidate; -
local teams may use local meanings; boundary-crossing work makes the translation relation explicit;
-
the project object itself, its description, a dashboard about it, a decision about it, and the work done to change it are not the same;
-
architecture is structure of that holon or project object in a context, not the diagram, document, approval, or plan about it;
-
serious architecture work can move from problem pressure to candidate structures, selected structures, decisions, method and work, actual structures, and feedback;
-
when the current question is which reusable way of doing changes, produces, derives, selects, controls, or preserves the project object under stated conditions, inspect
A.3.1 U.Method; -
to decide whether setting up and applying a selected apparatus, such as a model, is worth the cost for one use, inspect
C.19.2; it tests the bounded application against the required result and guarantee. UseC.39when a missing obtaining explanation must be developed, orC.40when usable material needs variation and examination. UseC.18for archive or front claims, andC.11when two or more eligible alternatives make a local choice current; -
when a clear engineering claim leads to an incorrect conclusion about action, identity, dependence, whether a relation obtains, responsibility or projection, inspect
A.7.1; when current FPF uses produce incompatible consequences for the same receiving claim and scope, inspectA.7.2. The latter can expose an unresolved incompatibility rather than produce one reconciled answer; -
when an accepted C.22.2
ProblemCardepisteme must remain usable while the project selects a method, prepares or performs work, interprets a result, branches, stops, or returns after a changed assumption, inspectE.18.1 P2W Problem-to-Work Carry-Through; it traces what each result establishes for the accepted problem. When several results must serve one decision, obtain the grounds for using them together from the practices that supply and use them. Return the supported conclusion to that decision. -
when relations or constraints change what can happen next, use
E.18.3. Start with the continuation someone needs to judge. Identify what could make it possible, block it or leave it open. The proposed connection between two states can answer how a transition is designed. To establish feasibility or an actual passage, use the conditions or evidence required for that claim. A continuation that depends on several participants also needs the relation among them. Follow up the missing condition, occurrence rule or fact when it changes the answer.Use A.22/E.18 qualification when the named use depends on the identity and qualification of the unfolding organization as an E.18.3 structure. Add a separate demonstrative-slice claim only if that use needs it. When no branch, connection or constraint affects the continuation question, an ordinary route description suffices.
-
keep several options alive until the comparison is clear enough to choose;
-
say what "better" means before optimizing or scoring;
-
make trust depend on evidence, freshness, scope, and intended use;
-
publish different views for different readers without changing the underlying claim;
-
when explaining or reordering selected source structure, including narrative rendering, state what is preserved, deliberately coarsened, abstracted, omitted or lost, and when the reader must return to the source. Establish any stronger claim under the pattern that governs it;
-
use mathematics or formal models when they clarify what structure is preserved, what is lost, and what can be checked;
-
build domain or local FPF-grounded frameworks as dependents of FPF Core, not as silent rewrites of the Core.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)