Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

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:40:10 UTC

E.4.CM:11 - SoTA-Echoing

Working question and selected answer. How should a framework author turn available methods into a public explanation that readers can combine and adapt without inventing the essential connections? The selected answer is the FPF construction in §§4.1–4.7: recover the receiving use, establish the actual participants and relations, develop missing joins, preserve independently useful branches, and test changed conditions while keeping each claim connected to its grounds. The resulting Method or explanation can be original even when its ingredients are known.

The serious method-engineering alternative constructs or configures a situational method from reusable units, with requirements and evaluation guiding adaptation. Wilke et al., Method Engineering — a Systematic Literature Review on Scopus Base, §§2–5, compares definitions and approaches including assembly and configuration; its Scopus search of August 2022 is bounded evidence of that repertoire, not proof of one universal ontology or the best answer today. OMG Essence 2.0 beta 2, §§7.3–7.4, 9.3.2.12/.15 and 9.4, is a serious concrete comparator: a common language and kernel support coherent Methods composed from Practices, recursive Practice composition, adaptation, and composition with conflict resolution. Its activities can be sequential, parallel or conditional.

Ralyté, Koutsopoulos and Stirna, Verification, validation, and evaluation of modeling methods: experiences and recommendations, §§2–4.1, 4.8 and 6.3, separates assessment purposes: construction correctness, fit to requirements and practical worth. It also covers problem and requirements analysis, evidence suited to development maturity, parts, method base, whole method and supporting provision. Its modeling-method cases and recommendations do not validate FPF or settle FPF participant kinds.

Cash, Daalhuizen and Hekkert, Evaluating the efficacy and effectiveness of design methods: A systematic review and assessment framework, §§2.1–2.5 and Table 1, supplies a different test: follow the evidence connecting a method’s motivation, nature, development, content and claims. Its focus is design methods involving human activity or interaction; its study assesses reported evidence in selected design journals from 2020 (§3). It does not establish a universal method-development procedure or assess the whole method market (§§5.1–5.2).

The two treatments overlap in needs, content and outcomes. VVE distinguishes what an assessment seeks to establish; the evidence chain makes the grounds and alignment of the proposal inspectable. A positive trial can answer a bounded use question while leaving a need claim, development choice or wider effect unsupported. E.4.CM therefore combines the three assessment questions with explicit claim grounding in §4.6 and the checklist. §§4.1 and 4.3–4.4 develop the need and connections; §4.6 links their grounds to the conclusions drawn. This combination helps locate which premise or instruction must change when an assessment fails.

Question that could change the answerDisposition and consequence in this Method
Definitions and terminology: what are the reusable units?Adapt the sources’ explicit unit and composition accounts. In §4.1 recover what each unit denotes before transfer; use A.3.1 and B.1.5 for the FPF Method and constituent claims. Reject equating a fragment, chunk or Essence Practice metaclass with an FPF submethod by name. E.10 governs the ordinary synonym choice.
Requirements and context adaptation: what makes a selected combination useful here?Adopt adaptation from the receiving need. §§4.1 and 4.3 already develop inputs, conditions and joins; §5.4 changes one receiving tolerance while preserving another use. A new domain label alone changes no Method.
Assembly, tailoring, configuration and evolution: what may change?Adapt the constructive repertoire rather than requiring one assembly pipeline. §§4.2–4.3 distinguish joining complementary operations, integrating overlap, guarded alternatives and returns; §§4.4 and 4.7 preserve a sufficient existing construction and reopen affected connections. §5.4 separates developing a Method from enacting it and keeps independent Methods plural.
Implementation, training and support: what must be available to use the method?Adopt attention to the complete usable arrangement. §§4.1 and 4.6 expose preparation, tools, assistance and recurring burden. Reject tool availability or expert-supported success as proof of an independently usable Method. Tool implementation and capability development themselves remain with their direct suppliers.
Assessment purposes and evidence: what is being established, and what supports it?Adapt together VVE’s three assessment purposes and Cash et al.’s chain of grounds. §4.6 connects need, proposal, development decisions, content and claims to their support; the checklist tests those connections. Reject a final successful trial as support for every earlier or broader claim, importing Cash et al.’s method taxonomy as FPF kinds, and making one empirical-study hierarchy govern mathematical, conceptual and human-use claims alike.
Part, method-base and whole quality: where can adequacy fail?Adapt the distinction in §4.6 and its checklist: a good part, searchable repertoire and adequate whole support different claims. Reject their automatic aggregation and any universal common metamodel imported from one method-base approach. Check the actual join and receiving result, as §5.4 does.

Why this construction is selected for the question. A direct route through existing descriptions is cheaper when it supplies the missing connection, as §5.1 shows. A common method-engineering model can be useful when the receiving project needs its compositional conventions and tooling. Neither a reading route nor transferring the source’s unit model by itself establishes the receiving FPF composition, result-use and Work claims. This is a transfer limit, not a claim that Essence cannot describe the case or accept additional rules.

The studio case in §5.4 gives the bounded difference. The mathematical correction remains valid at the marks; the interval-wide warrant is separate. Tightening analysis from 3 ms to 2 ms defeats one receiving use, while 8 ms viewing remains available. The account identifies the connection to redevelop without making analysis and viewing parts of preparation, repeating unaffected work, or asserting empirical success. C.30.ASV:4.5a makes the relevant structure choices reusable. The selection concerns this conceptual construction. Claims about comparative effectiveness or learning cost need evidence from those uses.

The accepted cost is explaining and maintaining those consequential relations, with reusable detail left at its supplying owner. Reopen when a directly usable treatment supplies the same connections with less reconstruction, an applicable current rival changes the construction or evaluation question, a constituent or receiving condition changes, or an actual use exposes a missing rule, support need or moved burden. A better supported answer at lower total burden should replace this one.