FPF.Reference:16.8.5 - Architectural Rationale and source comparison
Preface node
heading:fpf-reference-16-8-5-architectural-rationale-and-source-comparison:1783
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
Situational Method Engineering (SME) contributes situation dependence and deliberate construction of reusable ways of working. This arrangement keeps both premises. It selects one profile in which patterns expose problems, forces, actionable contributions and useful relations, while Method identity and composition remain separately governed. The reuse unit is therefore not indiscriminately a source slice: it can be an independently qualified smaller Method, a description contribution or a neighboring non-Method answer.
This explains the distinct production results. Recovery must remain faithful even when allocation later rejects a proposal. Description comparison must not be replaced by either a cross-use representation profile or a judgment of Method worth. Language architecture must make material relations useful without creating parthood. Reconstruction must be able to find a missing contribution before a contradictory maintained claim and its owner are already known. A.3.1.DR, F.0.2.MA, C.37.CF, E.8.ML and F.0.2.RC keep these differences actionable.
The following sources supply questions and alternatives for comparing this profile:
Alexander et al.'s A Pattern Language (1977) supplies the historical problem-first, connected-guidance idea. Minsky's frame account (1974) connects situation knowledge, expectations and adaptation. The architectural analogy drawn here concerns those knowledge-use roles. Declarative and case-management approaches, including CMMN 1.1, remain operational comparison targets, not the ontology adopted by this language.
The selected arrangement uses Core's general qualification, architecture, representation and assurance Methods. Their shared use does not establish a separate discipline or require another framework. A domain framework would need a different justified field promise. A prose-only synthesis remains a serious lower-maintenance option; a fixed route remains legitimate under stable conditions. Reopen the arrangement choice when current supply removes a distinct result, reconstruction fails for a promised use, source conditions change, or the maintenance burden defeats the practical gain.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)