FPF Reference

    C.30.TFS-REL:4.4a - Architecture use of a transformation-flow structure network

    Preface node heading:c-30-tfs-rel-4-4a-architecture-use-of-a-transformation-flow-structure-network:62111

    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

    First ask whether one exact ArchitectureOf@Context claim for a named holon includes the selected network in structureRefs. If it does not, ask whether the architecture question relies on claims for several named holons while no containing holon has been grounded. Select exactly one branch; a connected diagram does not answer either question.

    1. Named containing-holon use. Set networkArchitectureUseBranch=namedContainingHolon. Name exactly one containingArchitectureClaimRef: ArchitectureOf@Context whose describedHolonRef identifies the containing holon and whose structureRefs include the same exact transformationFlowStructureNetworkRef; keep participatingArchitectureClaimRefs[] and noArchitectureOfNetworkBearerAsserted absent. Member TFS values and their Work, valuations, boundaries, and direct relations remain independently governed.
    2. Explicit inter-holon use. Set networkArchitectureUseBranch=explicitInterHolon. Put at least two exact ArchitectureOf@Context claims with distinct describedHolonRef values in participatingArchitectureClaimRefs[]. Include exactly the claims whose selected structures or architecture characteristics this inter-holon question relies on; a network member whose architecture is not used by the question stays outside this array. Keep containingArchitectureClaimRef absent and set noArchitectureOfNetworkBearerAsserted=true. This states an architecture relation question spanning the named holons; it does not invent a holon or an ArchitectureOf@Context claim whose bearer is the network.

    Every other populated architecture-side reference must agree with the selected branch. In namedContainingHolon, architectureClaimRef when present equals containingArchitectureClaimRef, each value in selectedArchitectureStructureRefs is selected by that claim, and each architecture structural view, architecture description, or functional structure view used by this relation points through that claim. In explicitInterHolon, each such reference points through one named participating claim; a singular reference names only that participant and does not imply a containing architecture. If a reference depends on another architecture claim, add that claim as a participant only when the current question actually relies on it, or use a separate relation record.

    The branches are mutually exclusive. When transformationFlowStructureNetworkRef is absent, networkCrossFlowRelationRowRefs[] and all network branch fields are absent. A network ref without one complete branch is not ready for architecture use. When the record also names a path, slice, crossing, or valuation, bind it to the exact member TFS and the local positions or bindings that own it. When it names a network-aware unfolding, that E.18.3 locator must select the same exact network and preserve its admitted position mappings. The network ref does not lift member-local values into network-global state.

    Use networkCrossFlowRelationRowRefs[] only for E.18.NET-owned composite locators. Each locator's current containing record must describe the same exact selected network, and the occurrence plus complete ordered endpoint-binding identity must resolve exactly one nested row. Zero matches, several matches, or a record for a different network stop this architecture use. The locator identifies the row; it neither creates the relation occurrence nor changes its direct governor.

    For every maintainability, capability, responsibility, production, safety, or other architecture-characteristic claim made or used by this relation, name the exact holon, ArchitectureOf@Context claim, selected structure, view, relation, or other bearer governed by C.30. A network may have selected structural facts, such as its members, relations, recursion, or exposed positions; those facts do not make an unnamed network the bearer of holon characteristics, agency, Work, or production.

    A network diagram, member graph, mathematical description, publication, or TransformationFlowStructureNetworkRecord@Context is neither branch and does not enter architecture identity. It may describe the selected network only under its description or publication pattern.

    Named containing-holon case. ArchitectureOf@ManufacturingPlatform names the manufacturing platform as describedHolonRef and includes one product-development/production-system-change network in structureRefs. C.30.TFS-REL may use that network to localize an architecture change while each member TFS and production relation keeps its own owner.

    Explicit inter-holon case. A supplier architecture claim and a plant architecture claim use one selected E.18.NET-conforming supply-linked TFS network to inspect a cross-company dependency. Both claims appear in participatingArchitectureClaimRefs[]; no containing supply-chain holon has been grounded, so noArchitectureOfNetworkBearerAsserted=true. The network is not called the architecture of an unnamed enterprise.

    Last Updated: 2026-07-28 — upstream FPF commit 17edd955 (github.com/ailev/FPF)