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 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:25:20 UTC

C.32.MWA:11 - SoTA-Echoing

The sources below make complementary contributions; none is used as authority for the whole Method. The pattern composes only the bounded moves stated in the table, and the final row keeps current FPF distinctions authoritative.

Source lineContribution and limitDecision and transfer into this pattern
ISO/IEC/IEEE 42010:2022, current architecture-description standardDistinguishes the architecture of an entity from an architecture description and supports concerns, viewpoints, model kinds, and correspondences. It explicitly does not specify an architecting Method and is not a system or practice ontology.Adopt narrowly: keep subject, architecture, description, view, and correspondence distinct. Reject: treating standard conformance or a view set as the practice architecture. Carried into actions 2, 4, and 5 and CC-MWA-3/5/6.
Grootenboer and Edwards-Groves, The Theory of Practice Architectures (2024), and Olney and Wood, learning-design practice study (2023)Current practice-research line showing that professional practice is shaped across multiple sites and material-economic, cultural-discursive, and social-political arrangements. It gives a strong empirical antidote to procedure-only accounts, but its three media are one theory’s selected structures rather than universal FPF kinds.Adopt: multi-site, enabling/constraining, and empirical-practice attention. Adapt: recover the actual Method, Work, subject, description, capability/provider, and cultural relations needed by the case. Reject: importing the three media as a mandatory universal view set. Carried into Forces, Grounding, action 4, and the limited-scope bias.
Alter, Work System Theory (2013), established work-system lineProvides a practitioner-readable way to examine participants, activities, information, technologies, products/services, customers, environment, infrastructure, and strategy together rather than reducing work to IT or a process chart. Its fixed framework is valuable for recognition but does not distinguish every FPF Method, Work, description, capability, and cultural relation.Adapt as recognition lineage: start from useful Work and its result and look beyond one technical structure. Reject: treating the nine elements as a complete or mandatory practice ontology. Carried into Problem frame, actions 1–2, and obtaining cases.
Bartolomei et al., Engineering Systems Multiple-Domain Matrix (2012), with DSM/DMM lineageOrganizes source-side node classes in diagonal blocks and relation types within and between those classes in off-diagonal blocks; it supports tagging, storing, retrieving, and analyzing engineering-system information. It is engineering-modeling lineage, not current authority for practice ontology, and its source categories are not universal FPF kinds.Adopt as lineage: make the source-side class and relation type visible when several structures are compared. Adapt: recover each exact receiving relation or correspondence, state what it preserves and loses, use ordinary prose first, and add a matrix only when it helps the decision. Reject: row alignment, matrix membership, or visual clustering as a world-side relation. Carried into actions 3–7 and the layout/model anti-patterns.
Current FPF A.3.1, B.1.5, A.15.1, A.22, B.2, C.30, C.30.AD, C.30.ILC, C.32, C.32.MLAO, and C.36Supplies the maintained distinctions among Method, performed Work, selected-structure identity, whole reidentification, architecture, description, conflict, candidate synthesis, moved residual, and cultural change.Adopt and compose: these patterns provide the exact tests used by the eight actions. C.32.MWA adds the obtaining/prospective discriminator, several-structure synthesis, conditional product comparison, and one readable result; it does not redefine the neighboring kinds or relations.

Recheck these source uses when a newer applicable architecture-description standard, practice-architecture synthesis, work-system method, or multi-domain technique changes the practical move, or when unlike cases show that the eight actions no longer preserve a decision-relevant structure at proportional effort.