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

E.18:5.2a - Split-and-join structure discipline

Use split and join only as selected-structure relations inside one TransformationFlowStructure. A split separates one source locus, variant set, problem-side cue, or candidate family into several identified loci or flow valuations. A join relates several identified loci, selected sets, gates, measurements, or refresh returns back to one current structure position. Neither operation creates a new FPF kind, a new pattern, or a prescribed work procedure.

Minimum split-and-join use names the selected TransformationFlowStructure, the exact split or join predicate or policy when membership changes, the set or archive returned by the exact selector relation, the selected-set result declaration when current, the exact publication relation when that value is published, and the smallest refresh scope when currentness changes. Apply the definitions and tests in A.19.CPM, A.19.SelectorMechanism, C.18, C.19, and G.5 when comparator, selector, archive, pool, or result-declaration claims are current; use E.17 for a source-backed publication face and return to source, E.24.PUB for the publication occurrence, form, carrier, audience, bounded use, and availability, A.21 for a gate claim, and G.11 for a refresh claim.

For evolutionary-engineering work, the same selected structure may contain, for example, loci for variant generation, retention, archive or front treatment, comparison, selected-set result declaration, actual publication, architecture-candidate movement, planning, performed work, effect measurement, residual triage, and refresh. E.18 defines only the structure, loci, U.Transfer, crossings, valuations, pins, and slice-local refresh. Apply the definitions and tests in C.18, C.19, and G.5 when archive, pool, or selected-set result-declaration claims are current; use E.17 for a source-backed publication face and return to source, E.24.PUB for the publication occurrence, form, carrier, audience, bounded use, and availability, C.11 and C.30 for their decision and architecture-candidate claims, the A.15 family for planning and performed Work, and G.11 for refresh.