A.6.C:11 — Source contributions
Preface node
heading:a-6-c-11-source-contributions:16438
What this page is
This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.
Methodology
Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.
Content
The following sources contribute distinct disciplines to boundary interpretation.
-
Dietz and Mulder distinguish production from the acts that request, promise, declare and accept a product. They connect several transactions for one order through the results each requires. In FPF, the terms governing a particular order determine what counts as its acceptance. Enterprise Ontology, second edition, ch. 8, §§8.2.5–8.2.7
-
BCP 14 (RFC 2119 and RFC 8174) supplies the interpretation of capitalized requirement keywords. A.6.B separately classifies the claim; the visible keyword alone does not establish its object or whether an individual relation obtains.
-
Behavioural and session types describe typed interactions, including safety and progress properties. These support the distinction between model properties, admission conditions, implementer obligations and actual trace results.
-
Algebraic effects, handlers and effect systems distinguish declared operations from their handling. This is a useful analogy for declaration versus actual application; a result, production, delivery, evidence use or acceptance requires its own relation.
-
ISO/IEC/IEEE 42010:2022 viewpoint discipline supplies conventions for descriptions under viewpoints. E.17.0 tests a selected episteme's
U.Viewconformance, while A.6.3 governs any separately claimed construction. A.6.C keeps the boundary claims traceable across ordinary E.17 publication faces.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)