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 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:15:10 UTC

A.3.1.MR:11 - SoTA-Echoing

Source line and status, qualified 2026-08-26ContributionFPF adoption
Feldman and Pentland, Routine dynamics: Toward a critical conversation (2022)Separates particular performances from enduring or emergent patterns and keeps variation visible.Adopt the performance/pattern distinction. Repeated Work can support a candidate account without itself becoming the Method.
Stacey et al., Methods as a form of engineering knowledgeDistinguishes descriptive reconstruction from prescriptive method content and shows why the distinction can be difficult to maintain.Adopt the candidate-account rule. Coherent description does not establish Method admission or MethodDescription membership.
Mature process-mining reference: Process Mining Handbook (2022); current exchange-format boundary: OCEL 2.0 semantics and the 2.1 serialization revisionSupplies preparation, discovery, conformance, enhancement, and multi-object event representation capabilities.Adopt as well-scoped evidence Methods. Event extraction, naming, correlation, object identity, encoding, abstraction, windows, and serialization remain modeling choices; mining alone establishes no applicability, intention, authority, tacit contribution, causal value, or Method identity.
Current object-centric recovery alternatives: Adams et al., Defining Cases and Variants for Object-Centric Event Data and Küsters and van der Aalst, OCPQReal event data may relate one event to several objects; selecting one case key or flattening can discard information, while queries and constraints produce use-bounded results.Adopt the anti-flattening consequence. Preserve the multi-object evidence and state the selected grouping, query, or constraint when it changes the candidate account. A graph-shaped execution, query result, or constraint result is still evidence or an episteme, not the reusable Method.
Current FPF C.2.1, A.3.1, A.3.2, and A.15.1Separates episteme identity, Method identity, MethodDescription membership, and performed Work.Adopt directly. Return one truthful candidate-account episteme per candidate and keep all later admissions separate.