fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 82273–82286

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:15:10 UTC

E.4.PFAD:5.7 - Candidate recognition before product form

These cases apply the same contribution comparison at a carrier- or count-shaped entry.

Incoming materialPreliminary comparisonFramework result
A MethodDescription for composing recommendations covers a receiving question and authority, qualified supplier results, alternative formation, a declared comparison, a bounded recommendation, later-choice separation, and affected-premise refresh.Compare those contributions with current framework content. Use the file, MethodDescription, and broad title to locate candidate contributions; planned or unavailable pattern content leaves the corresponding contribution unresolved.Keep the architecture comparison open until exact current contributions support an outcome; select an owner from those contributions.
One long-mantra Card keeps several recurring problem–move–result contributions, material relations, representative cross-use, a plausible field, and a refresh boundary in attention.Treat the Card and mantra as evidence and run the same exact subtraction as for a larger carrier set.Apply the unchanged field-scale test; the Card is one carrier for its evidence.
A practitioner working in one professional role combines contributions from several current DPFs and FPF.Recover the role meaning and the exact contributions. Every action, result, return, and refresh duty is carried, and no coherent independent remainder or distinct field promise survives.Reuse the cross-DPF composition, with a role-centred view when needed; no new DPF is warranted.
One composite Method or local procedure has several ordered steps for one recurring problem/result family.Keep the Method, MethodDescription, carrier, Work, and listed steps distinct. The contribution remains one recurring problem/result family at Method scale.Return the smallest exact non-framework result or stop; use the cheap exit when no later-used architecture consequence remains.