C.39.MC:11 - SoTA-Echoing
| Source line and comparison use | Retained or adapted contribution | Boundary and practical consequence |
|---|---|---|
| Gottschalk, Yigitbas, Nowosad, and Engels, Continuous situation-specific development of business models, online 2022, journal issue 2023; an implemented contemporary SME comparator. | Adapt continuous interaction between supplied knowledge, situation-specific composition, and enactment. | Their repositories, fragment metamodel, and business-model case do not establish FPF Method parts or a universal process. C.39.MC uses direct Method/result identities and can stop without repository or structure construction. |
| Hoppenbrouwers and colleagues, Agile Service Development: A Rule-Based Method Engineering Approach, 2011; historical declarative/agile SME anchor. | Retain rules and constraints as an alternative to prescribing one complete development route. | Declarative and on-the-fly Method Engineering are prior ideas, not novelty claims here. Each current continuation still needs its facts and an acting/deciding System. |
| Christopher Alexander, The Origins of Pattern Theory, OOPSLA 1996 address published in 1999; historical lineage. | Retain context-sensitive use of a connected pattern language and the contribution of generative order. | Pattern order can be meaningful without being a universal Work sequence. This tradition supplies neither current FPF identity nor a claim that causality disappears. |
| Stacey and colleagues, Methods as a form of engineering knowledge, 2025; recent engineering-knowledge comparator. | Retain explicit how-to knowledge together with the knowledge needed to interpret and use it. | Their treatment of Method knowledge does not settle FPF’s world-side Method/episteme boundary. It supports exposing the needed knowledge and result, not importing a definition by vocabulary. |
| Current E.11.PUA/PUR, A.15.7, A.22.CGUS, A.3.1/B.1.5, and A.3.1.QM, C.32.MWA.PP, B.1.5.CM, A.3.2.DE, C.37.MP; direct working comparators. | Reuse pattern use and result reuse, live choice, potential/current continuation separation, Method identity/composition, and professional result contracts. | The new contribution is limited to the question-to-result return and situation-delta localization across Method-development uses. If direct use supplies that same result more cheaply, take the direct exit. |
These sources support a bounded synthesis, not a claim that this construction invented continuous or pattern-based Method Engineering. Reopen the affected source or action when a current alternative supplies the same result with less reconstruction, a source change alters a load-bearing distinction, or use evidence reveals a missed dependency or unnecessary burden. Claims of human or AI superiority require their own comparative evidence.