Network of Transformation-Flow Structures
About this pattern
This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.
How to use this pattern
Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.
Tech-name: TransformationFlowStructureNetwork Plain-name: Network of transformation-flow structures Type: Structural pattern for ontic relations (E) Status: Stable Normativity: Normative unless marked informative
Use this pattern when one engineering question depends on two or more independently identified transformation-flow structures, or on nested networks of them, and at least one obtaining relation connects positions across their boundaries. Typical situations include a toolchain that builds another tool, a production system related to the product it helps produce, or an operating flow whose observation returns to a separate development flow.
Relations
C.30.TFSContent
Problem frame — intent and first useful result
Use this pattern when one engineering question depends on two or more independently identified transformation-flow structures, or on nested networks of them, and at least one obtaining relation connects positions across their boundaries. Typical situations include a toolchain that builds another tool, a production system related to the product it helps produce, or an operating flow whose observation returns to a separate development flow.
Start with the three cases in step 1. Continue with steps 2–5 when the engineering question requires a network.
- decide whether the case is several valuations of one flow structure, an internal portion of one flow structure, or a network of independent flow structures;
- identify each candidate member independently;
- name the obtaining relation occurrences that connect positions in different members;
- select only the members, relations, boundary exposures, and constraints needed for the current question; and
- return one network reference, or stop at the proposed description and name either the relation-claim result returned by its governing pattern or the separate missing network discriminator.
A successful selection returns a network reference and its basis.
If selection stops, return the proposed description and the reason. For example:
When the relation claim has a positive obtaining result but a network endpoint is not bound, keep that positive result and state a separate E.18.NET selection blocker:
If a fact needed to decide the relation claim is unavailable, carry the governing pattern's missing-information outcome; a sufficient case basis that fails its positive test yields factually unsupported. Neither outcome alone asserts a negative. Carry an inapplicable or negative result only when that pattern's applicable rule and case basis establish it.
A missing member, applied constraint, or networkUseFrame remains its own network-selection blocker and never becomes a relation result.
Keep proposedNetworkDescriptionRef until all four A.22 discriminators—members, selected obtaining relation occurrences, applied constraints, and use frame—are recoverable; only then assert selectedNetworkRef.
Do not use E.18.NET merely because one flow branches, contains a detailed portion, has several valuations, or is drawn as a network. Use E.18 for one selected TransformationFlowStructure, its valuations and selected internal obtaining relations; use E.18's SubflowRef for one parent-relative internal portion.
Use E.18.2 when the current object is a graph, wiring diagram, tuple, category-theory expression, or another mathematical description. Use A.22.CGUS and E.18.3 when the current object is an admitted demonstrative traversal rather than the network itself.
Problem
Teams routinely connect flows that concern different objects, Work occurrences, architecture boundaries, valuation state, and change cadence. A development TFS has positions for the Work that produces or changes a tool; other TFS values have positions for its use and evaluation, with feedback to development.
A manufacturing system is changed through one flow while products are made through another. A compiler is built by one toolchain and then participates in a later build.
A single picture can hide three different ontic answers:
When the third case is treated as one giant TFS, local state appears global, one internal connection is asked to replace distinct production, use, evaluation, feedback, correspondence, and dependency predicates, and a change in one member appears to reidentify everything.
When the first or second case is over-split into a network, the model invents members and relations that the engineering situation does not need.
Forces
Solution
Select a dependent non-agentive structure
TransformationFlowStructureNetwork@Context is a dependent, non-agentive specialization of U.Structure defined by E.18.NET and selected through the A.22 identity law. It is not a root U-kind, acting system, holon, workflow, graph, record, publication, FlowValuation, WorkPlan, or performed Work.
The @Context suffix qualifies retrieval and use; it adds no identity discriminator.
For N : TransformationFlowStructureNetwork, recover its four identity discriminators:
As in the first-use result, the four fields identify the direct members, selected obtaining cross-flow occurrence refs, applied network constraints and one concrete use frame.
returnCondition is not a fifth identity discriminator; it records when the current use must return and reselect. stopOrReturnCondition states the boundary of the action or use within networkUseFrame; returnCondition names a change that reopens selection.
forbiddenOverread?, also called groundedForbiddenOverread?, records an optional explanatory guard under F.19:4's plausible-reader test. It remains outside networkUseFrame and structure identity. A change to that explanation alone leaves the network unchanged; if its content changes an applied constraint or a use-frame value, compare that existing discriminator.
The direct-member set contains at least two members. Each member is one independently identified TransformationFlowStructure or one independently identified E.18.NET-conforming TransformationFlowStructureNetwork. At least one selected relation occurrence binds positions in different direct members or in different leaf TFS members reached through them.
The use frame states the concrete question or action, how this selection will be used, and its stop or return condition. “Current use”, “appropriate network”, and the title of a diagram are not use frames.
The direct-member discriminator identifies the selected members; record rows cite those independently identified values. If a later use needs a separately re-identifiable world-side membership occurrence, apply the direct relation pattern that defines its participants, predicate, applicability, and identity rule. When no such rule is available, reopen the relation question under A.6.RCD.
Reidentification and change locality
Replacing a direct member, selected relation occurrence, applied endpoint or exposure constraint, acyclicity constraint, or named selection-use frame identifies another selected network. Reidentifying a nested member reopens every parent network that selects that member.
Changing only a name, reference designator, record edition, graph layout, mathematical description, publication, selecting system, selection Work, evidence item, FlowValuation, PathSliceId, or local DesignRunTag leaves the network unchanged when the four A.22 discriminators still resolve to the same values.
Recurse through finite member paths
The selected direct-member nesting is acyclic. No direct or transitive member path from a network resolves back to that network, and every member path used by a reference is finite. The same network kind supports build-the-builder and supply-network recursion at any finite nesting depth.
When functional layers are useful in a flow network, organize them by the contributions that the selected flows make to the stated result. In a build-the-builder case, one flow produces a system that performs work in another flow; recover the production, use and participation relations that connect them.
Nesting one selected network inside another records member grouping for the current question. The depth of that nesting does not determine the functional layers or a modular hierarchy. Use C.30.STRAT:4.2 to keep functional layers distinct from levels in a module and interface structure.
Cycles among selected cross-flow relation occurrences remain possible when their applicable predicates and constraints permit them. Feedback from operation or evaluation to development is therefore compatible with acyclic membership: the cycle is among those relation occurrences, not in network containment.
E.18 defines the complete FlowPositionRef identity. Import that tuple unchanged; E.18.NET defines only the ExposedFlowPositionRef extension needed for a boundary position reached through one finite member path:
Every hop in memberPath[] resolves through the preceding network's direct members. Its final member is the TFS named by leafFlowPositionRef. When the path crosses a nested network, the leaf position must be one of the boundary positions that nested network exposes for the current use by the containing network. Two different paths to the same leaf TFS position are two different exposures.
The parent network may compose the finite path and use the exposed boundary. It must preserve the nested member’s internal structure without copying or flattening it. A separate mathematical description may flatten the nesting for a declared use when it states what the flattening preserves and loses. FlowValuation, PathSliceId, actual fillings, and DesignRunTag qualify use of a position; they are not part of FlowPositionRef or ExposedFlowPositionRef identity.
Keep valuation and design/run state leaf-local
Each positionBindingRef cites the relevant E.18 participant-position/use binding or a declaration-local binding whose pattern defines the needed participant meanings, value kind, and reference mode. A network introduces no universal cross-flow value kind.
Recover each leaf TFS under E.18:5.1, including its A.22 identity, beta resolution and the complete participants of its selected relations. Its valuations use E.18:5.2’s declared connection/cut domain and regime.
DesignRunTag belongs to one position binding inside one leaf TFS. A network has no FlowValuation for the network as a whole, global design/run ladder, or automatic crossing that changes the carried entity's kind.
If the same episteme fills local positions in different members—for example one position concerned with design work and another with production, verification, or later operation—record each leaf-local binding and the exact relation that obtains between them. Those ordinary member descriptions create no fixed TFS taxonomy or lifecycle phase.
When a changed basis is used across members, follow E.18:5.13 through the exact cross-member occurrences and every dependent branch and join. Cover the required leaf-local PathSlices; independent uses and each member’s local state remain separate.
Preserve the direct cross-flow relations
For every relation used by the network, recover the following values.
- the obtaining occurrence;
- its admitted relation kind;
- the pattern that defines or tests its predicate, applicability, and occurrence-identity rule;
- the complete participant meanings and order;
- the endpoint member and position binding for every participant; and
- direction only when the direct relation has direction.
An n-ary relation remains n-ary. Do not decompose it into invented binary arrows. A row, edge label, shared entity, temporal adjacency, operation result, plan row, or graph connection never makes the relation obtain.
E.18 resolves each internal connection(q) to its selected relation occurrence r. That position is local to one selected TFS; it supplies no universal cross-member predicate.
For any production, use, participation, evaluation, correspondence, feedback, dependency, supply, or other cross-flow relation, the relation kind must already be admitted. Use its applicable relation pattern to recover the participant meanings, predicate, applicability, and occurrence-identity rule; current case facts or constituting history must satisfy the positive predicate.
The occurrence obtains when those conditions hold. For network selection, identify an occurrence that already obtains. Use A.6.REL only when a named use must distinguish that occurrence from another.
For ordinary network selection, the PatternID and exact relation occurrence are enough; add relationFunctionClaimRef to the defining or constraining ClaimGraph only when comparison, migration, or reliance depends on that exact rule identity. The network selects only the ref to the occurrence that already obtains.
If no admitted relation kind and applicable predicate cover the intended participants and use, carry missing-governor from the pattern governing the relation claim. If required case facts are unavailable, carry its missing-information result; if the available basis is sufficient to apply the positive test but that test fails, carry factually unsupported.
Neither missing information nor a failed positive test suffices to establish a negative. Carry an inapplicable or negative result only when the governing pattern defines that outcome and its current basis establishes it. Only a positive obtaining occurrence may fill selectedCrossFlowRelationOccurrenceRefs[].
After a positive occurrence is established, test the E.18.NET endpoint and position bindings separately. A missing binding blocks network selection but does not change the relation result. Missing members, applied constraints, and use-frame values are likewise separate network-selection blockers.
A row, graph edge, or episteme neither admits a relation kind nor creates an occurrence. In none of these branches substitute creates, produces, uses, input, output, result, handoff, or transfer as a generic edge.
Record the network without replacing it
If the selected answer must remain available after the immediate work, describe it with a separate C.2.1 episteme. Its effective scheme has the C.2.1:4.1.2 range EpistemeInterpretationScheme; recover the rules that interpret the record's network, member, relation and endpoint-binding designations and its claims:
The C.2.1 record describes the selected network. The network and record have different identities. The record’s member and relation rows cite objects that already exist and occurrences that already obtain.
An architecture-correspondence row is a qualified reading only. It contributes no member or selected cross-flow relation unless a separately grounded relation occurrence and endpoint bindings also satisfy the network identity.
E.18.NET defines this composite locator for one nested cross-flow row:
Resolve the record ref first, then match crossFlowRelationRows[] by the occurrence ref and the complete ordered endpoint-binding identity. Exactly one row must match. Zero matches or several matches leave the locator unresolved and stop that consumer; never fall back to the containing record, the occurrence alone, or a prose pointer.
NetworkCrossFlowRelationRowRef is a reference shape, not a U-kind, episteme, or relation occurrence. Its U.EpistemeRef targets the containing record, never the nested row.
Keep descriptions, demonstrations, architecture, and Work outside identity
Use E.18.2 for a graph, hypergraph, network expression, wiring diagram, category-theory object, tuple, fold, or other mathematical description of the selected network. State what that description preserves and loses. Use E.17 when publishing a rendered graph or another face. Use C.29 when the adequacy of the mathematical lens for its declared use is at issue.
Use A.22.CGUS and E.18.3 for an admitted network-aware DemonstrativeUnfoldingSlice@Context. Its finite paths must map to already admitted included positions, its cross-flow relations must cite admitted relation-reference epistemes identifying those occurrences, and its tags remain in leaf-local bindings. The slice demonstrates one traversal; it is neither the network nor an actual trajectory, WorkPlan, or Work occurrence.
Use C.30.TFS-REL when architecture uses the independently selected network. Distinguish one named containing holon with an obtaining architecture relation whose selected structure is that network, a bounded C.30 claim about one named holon, and an explicit inter-holon use with its participating architecture claims.
For the single-holon claim, retain its negative, unresolved or candidate/expected disposition, supporting or missing basis, and return before stronger reliance; the architecture claim does not relax network selection.
Use C.32.CONWAY only for its one-pair architecture-influence reading; the pair does not become the network.
Only admitted Systems perform Work. Selecting a network, writing its record, or drawing its graph may be Work when A.15.1 independently admits the occurrence after each precise performer has an A.13 core; none is performance by the network, and no Work claim is needed merely to select or discuss the network.
When selection Work is material, cite those already established A.13 and A.15.1 results. Cite F.6 only when the current network account also needs precise assignment-bound attribution, and leave its proof with F.6.
Keep the Method, performer, dated Work, result episteme, selection or decision relation, and any C.11 choice result separate. A result episteme is not a decision or accountability relation by form; state accountability, duty, responsibility, or authority only through the direct relation that obtains.
Archetypal Grounding — worked cases
Same surface vocabulary, different ontic answers
Several valuations of one TFS. A cooling-loop review compares nominal-load and emergency-load valuations of the same cooling-loop TransformationFlowStructure. Both valuations retain the same A.22 selection O/R/C/F and use the E.18 connection/cut domain under their declared regimes. A counterfactual load value, path slice or local use tag may differ while those discriminators remain unchanged.
Replacing an actual run, applied selection constraint or selected occurrence first reopens the TFS identity. E.18.NET is not used.
Internal coffee subflow. A coffee-brewing TFS exposes a preparation portion containing grinding, dosing, and wetting positions plus their selected parent-internal relation occurrences with all participants retained. Its entry and exit remain positions of the brewing TFS. The practitioner uses E.18's SubflowRef; no second TFS or network is created.
Independent network. A roastery-production TFS and a café-brewing TFS concern different objects and have separate Work occurrences, valuation boundaries, and architecture change cadence. The applicable supply pattern defines its predicate and applicability, and the current delivery-and-acceptance facts satisfy that predicate for a dispatch position in the first and an accepted-stock position in the second. The following selection suffices for ordinary first use.
This filled basis is enough for the immediate selection; it is not a TransformationFlowStructureNetworkRecord@Context. Create that separate descriptive record only when the result must survive the current work.
If the supply claim has no admitted relation kind or applicable predicate, carry the governing pattern's missing-governor result. If required facts are unavailable, carry missing-information; if a sufficient case basis fails the positive test, carry factually unsupported. Neither missing information nor a failed positive test asserts a negative. Only an applicable negative rule and satisfying case basis can supply a negative result.
When the supply occurrence obtains but an endpoint binding is missing, keep the positive occurrence and name the missing binding as a separate E.18.NET selection blocker. A missing member, applied constraint, or coffee-service use frame is also a separate selection blocker.
Project system-of-interest and recursive build-the-builder
For one project question, practitioners ask which independently identified flow structures must be considered together to connect production and later operation of the project system-of-interest, and which builder branches must also be visible. The actual project remains composite U.Work; the selected network is a non-agentive U.Structure.
Project designation and U.System identity remain separate from any local system-role kind, classification, assignment, selection Work, or result episteme. None follows from a project or network label.
For the compiler-and-application use, identify five TFS values by the questions they answer:
CompilerEditionPreparationTFS, whose loci bind compiler-edition preparation and the obtaining source-use occurrences needed by the build;BootstrapCompilerBuildTFS, whose loci bind Work on pre-existing build substrates and the separately grounded production and identity-inception claims for one bootstrap compiler;ApplicationBuildTFS, whose loci bind application-production Work and the use of that admitted compiler in the application build;ReleaseAssuranceTFS, selected for release-assurance questions; andDeploymentOperationTFS, selected for deployment and operation after the application system exists.
These names designate independently identified TFS values, not lifecycle kinds. They assert no transformation of a not-yet-existing compiler or application. Use E.18 for each TFS, A.15.1 for any current Work occurrence, A.3.4 for a change of a continuing referent, A.15.PROD for production or identity inception, and the applicable relation pattern for each cross-member occurrence used here.
The compiler-producing contribution of BootstrapCompilerBuildTFS and the application-producing contribution of ApplicationBuildTFS occupy different functional layers in this build-the-builder account. Their connection runs through the produced compiler and its participation in application-building Work.
The nested networks below instead group members for successively broader questions. Their four depths are not four functional layers or four levels of a modular structure.
Select the nested network values from those already established inputs:
Each named occurrence is independently established under its project predicate before selection. Each network applies its endpoint-binding and boundary-exposure constraints plus the acyclic direct-member constraint, and each keeps the use frame in its row. The local names select or add nothing by themselves.
No claim about who selected these networks is required. If the case also needs CompilerNetworkSelectionWork-5, cite each precise performer's independently established A.13 core and the Work's independent A.15.1 admission. Add F.6 only if the case also needs attribution under the assignment in question; its assignment declaration and proof remain outside E.18.NET. Adding or removing the Work or attribution claim changes none of the four network identities above.
The result episteme may describe the selected structures and cite a separate selection or decision relation, but it is not a decision or accountability relation by form. Any accountability claim needs the predicate and participants of that accountability relation.
A compiler-production case can close on separately grounded identity inception, production completion or readiness, evidence, and decision while naming the application-build position as the downstream use outside that closed case. Project-level reasoning continues into the member where the compiler later participates.
The same joint-selection question recurs for a builder system: select the TFS in which that admitted builder performs the Work at issue together with the independently identified TFS or nested network concerning production and identity inception of the builder, or its later change after it exists.
Shared identity creates no edge; use obtaining production, inception, participation, application, use, or other relation occurrences and their endpoint bindings.
The bootstrap compiler result is exposed from the outer network through one finite member path:
Each path entry is a direct member of the preceding network, the final entry is the TFS named by leafFlowPositionRef, and no network repeats. FlowValuation, path slices, and DesignRunTag remain leaf-local. “Builds”, “uses”, “evaluates”, and “delivers” are ordinary cues until each link resolves to an admitted relation kind, complete participant meanings and order, obtaining occurrence, and endpoint bindings.
Before these identities and relations are grounded, A.1.STM may show the dependency only as a Plain provisional long-mantra map and must name the missing member, the exact relation-claim result returned by its governing pattern, or the separate missing occurrence, endpoint, or position binding. It is not yet an E.18.NET selection.
Once the network is admitted, a separate A.22.CGUS demonstrative slice may traverse admitted positions and relation-reference epistemes; it remains a demonstration, not the project, network, case, or Work order.
N-ary relation and feedback cycle
A manufacturing release relation has three participants defined by one admitted domain relation pattern: one product-definition position in a TFS selected to answer the development question, one equipment-readiness position in a TFS selected to follow the changes that establish equipment readiness, and one release-condition position in a TFS selected for assurance. Keep the three participants in predicate order in one network row. Three unlabeled arrows would lose the ternary relation.
Later, a use-observation relation connects a position in a TFS selected for operation or use back to a position in a TFS selected to answer the development question. If independently established cross-member occurrences lead from that development position to the operating position, the observation closes the path into a feedback cycle. In either case, the selected direct-member nesting remains acyclic. The feedback does not make the operation-or-use TFS a member of itself and does not turn observation into development Work.
Architecture and two demonstrative boundaries
For one containing holon, an independently obtaining C.30 ArchitectureRelation may have the exact network as its selected structure. A bounded C.30 claim Q about one named holon H and the independently selected network N may instead remain negative, unresolved or candidate/expected under C.30.TFS-REL's single-holon claim branch; retain Q's basis and next return.
If the selected members belong to separately named holons and no containing bearer is grounded, use the inter-holon branch and name the participating architecture claims. None of these architecture uses supplies a missing network discriminator.
A Plain A.1.STM long-mantra map may display proposed members and a missing cross-member link before network admission. It names the intended final result and the absent member, relation kind or predicate, predicate result, occurrence, or endpoint binding; it asserts neither an E.18.NET structure nor a CGUS.
After the network is admitted, a separate teaching mantra may show one finite admitted dependency slice. The slice uses the network locator family, cites admitted positions and exact relation-reference epistemes, and keeps omissions and return visible. It does not prescribe project Work order, make the path the whole network, or turn a leaf-local DesignRunTag into a project phase.
Bias-Annotation
These five bias risks apply across uses of this pattern: Gov, Arch, Onto/Epist, Prag, and Did. The table gives a mitigation for each.
Conformance Checklist
Common Anti-Patterns and How to Avoid Them
Consequences
Adoption test: use E.18.NET only when the current question needs independently identified members and at least one obtaining relation that connects positions across their boundaries. If one TFS or one parent-relative SubflowRef answers the question, there is no need to add a network, endpoint bindings or member paths.
Rationale and naming
TransformationFlowStructureNetwork names a recursively selected organization over independently identified transformation-flow structures or networks and exact cross-flow relation occurrences, preserving member boundaries and locally exposed positions. Members are structures rather than their valuations, and nesting may have any finite depth. The Plain name is “network of transformation-flow structures.” The shorter cue “transformation-flow network” serves retrieval after that subject is clear.
SoTA-Echoing
Each line below is inherited only while the cited current pattern version retains both the named body decision and the named source-use row for its declared use. E.18.NET relies on the currentness decision recorded with that source-use row; it does not independently turn the cited literature or tool practice into current authority.
When one cited source-use row changes, reopen only the affected line here.
A new need for cyclic member identity, a separately re-identifiable membership occurrence, or cross-flow semantics that cannot preserve the direct relation and its endpoints reopens the E.18.NET architecture decision itself.
Relations
Builds on: A.22 for selected-structure identity and non-agentivity; E.18 for one TFS, its selected internal relations and resolved connection positions, FlowPositionRef, valuations, paths, slices, and local state; A.6.REL, A.6.RCD, and A.6.P.WMR for exact relation recovery and missing-governor; C.2.1 for the optional descriptive record; and F.18 for the stable local name.
Coordinates with: A.15.6 for actual project Work, project system-of-interest designation, and subject- or claim-centred case closure; A.1.STM for a Plain provisional long-mantra display and backward/forward attention use; E.18.2 and C.29 for mathematical descriptions; A.22.CGUS and E.18.3 for admitted demonstrative slices; C.30.TFS-REL for architecture use; C.32.CONWAY for one qualified architecture-influence pair; A.3.4, A.12, and the A.15 family for actual transformation, causal or acting positions, Work, production, and work-to-change claims; E.17 for publication; E.11 for public entry and recognition; and E.11.PUA for using one already selected pattern to reach its first useful result.
Does not replace: the direct pattern that defines or constrains any selected production, use, participation, evaluation, feedback, dependency, correspondence, supply, evidence, assurance, gate, decision, causal, or work relation. E.18.NET selects already obtaining occurrences for one network use; it does not define their kinds or make them obtain.
E.18.NET:End
Last Updated: 2026-11-12 — this section last modified in upstream FPF commit 1e57ccda (github.com/ailev/FPF)