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:25:05 UTC

B.1.5:11 - SoTA-Echoing

These rows answer the B.1.5 practice question: how to decide and expose order-sensitive Method composition without mistaking descriptions, Work, event records, or construction diagrams for the composite Method.

Current practice answerPublished source basisB.1.5 adoptionRejected shortcut
Current workflow, case, decision, process-mining, and object-centric event-log practice separates process models from event logs, telemetry, and resource records.A.15:11 — OMG CMMN 1.1 (2016) and OMG DMN 1.5 (2024); A.15.1:13.1 — OCEL 2.0 Specification (2024) and OpenTelemetry Specification 1.58.0.Adopt and adapt. Adopt the model, decision, occurrence, log, and telemetry separations; adapt them by requiring exact candidate and part Methods, methodPartOf, and separately grounded Work because a review must distinguish modeled composition from what happened.Reject. A workflow notation, event log, trace, or telemetry span is neither the composite Method nor proof of Method parts or dated Work.
Typed functional, scoped-effect, protocol, and workflow-composition practice treats composition as constrained by interfaces, preconditions, intended results, handlers, scope, and admissible order.A.3.1:11 — Gogioso et al., “Constructor Theory as Process Theory” (2023); Bosman et al., “A Calculus for Scoped Effects & Handlers” (2024); Matache et al., “Scoped Effects as Parameterized Algebraic Theories” (2024).Adapt. Use preconditions, intended-result meanings, scope, order, typed joins, adapters, and failure routes as concrete tests of the whole-forming claim because a composition label alone cannot show that one reusable whole action works. Use A.6.RCD’s lightest sufficient disposition for each resulting claim.Reject. A type signature, handler calculus, process-theory description, edge label, or source-material description alone does not identify a Method part, admit a relation kind, or ground dated Work.
Scoped software semantics makes operation declarations, handler scope, and boundary behavior explicit without supplying a general Method-identity rule.A.3.1:11 — Bosman et al., “A Calculus for Scoped Effects & Handlers” (2024), and Matache et al., “Scoped Effects as Parameterized Algebraic Theories” (2024), cited above.Adapt and delimit. Use that boundary visibility to state exposed, forwarded, and encapsulated interactions. The rule that a boundary decision affects Method identity when it changes the reusable action or admissible boundary is an FPF decision; a named receiver triggers explicit statement or publication because callers and substituting-method uses need a stable boundary account.Reject. Handler syntax, planner Work, publication layout, carrier choice, or diagram position does not decide whether an interaction is exposed, forwarded, or encapsulated.
Current constructional-ontology practice requires explicit constituents, constructive relations, dependence, and identity choices rather than inferring a whole from a diagram or label.A.1:11 — Florio and Linnebo, Introduction to Constructional Ontology (2024), and Borgo and Righetti, “Towards Applied Constructional Ontology” (2025).Adapt. Require exact part Methods, obtaining methodPartOf occurrences, other whole-forming claims at their A.6.RCD dispositions, a reusable whole action, and a reidentification rule because constituent names alone do not construct a Method whole.Reject. Method-composition order is not A.14 structural parthood, and neither a C.13 notation nor one shared label creates the Method or a relation kind.

Currentness and reopen. These four decisions are qualified by the exact source selections cited above. Reopen only the affected row when a cited source or edition is superseded, or when newer practice changes the relied-on model/occurrence separation, order or join condition, interface or substitution boundary, or construction and reidentification test. Recheck that row’s B.1.5 adoption, refusal, and affected Solution, worked-case, checklist, and Relations loci; leave unaffected rows closed.