FPF Reference

    C.30.TFS-REL:7 - Conformance Checklist

    Preface node heading:c-30-tfs-rel-7-conformance-checklist:62237

    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

    IDRequirementFailed-check repair
    CC-C30TFR-1 Flow-structure object.The relation names the exact E.18 TFS, E.18.NET network, path, slice, crossing, or flow valuation object it uses.Add the exact E.18 or E.18.NET reference named by value, or use C.30 or C.30.ASV without this relation.
    CC-C30TFR-2 Architecture locus.The relation names ArchitectureOf@Context, selected architecture-relevant structure, architecture structural view, or conditional ArchitectureDescription@Context use it relates to.Add architectureClaimRef, selectedArchitectureStructureRefs, architectureStructuralViewRef, architectureDescriptionRef, containingArchitectureClaimRef, or participatingArchitectureClaimRefs[] as the selected use requires; otherwise keep the TFS or network claim with E.18 or E.18.NET, the mathematical-description claim with E.18.2, or the math-lens-use claim with C.29.
    CC-C30TFR-3 Functional and flow separation.Functional structure and transformation-flow structure remain separate unless correspondence or positive selected-structure co-reference is declared.Add FunctionTransformationFlowRelationNote, add the co-reference check, or remove the functional-architecture claim from the flow sentence.
    CC-C30TFR-4 No architecture takeover.The selected transformation-flow structure, network, or mathematical description is not treated as generic architecture ontology or all architecture structure kinds.Assign grounded architecture claims, selected architecture-relevant structures, or conditional architecture-description use to C.30 and keep this pattern to the architecture-to-transformation-flow relation.
    CC-C30TFR-4a Network architecture branch.A network use selects exactly one branch. The containing branch has one ArchitectureOf@Context claim whose structureRefs include the exact network, and every other architecture-side ref agrees with that claim. The inter-holon branch has every architecture claim this question actually relies on, no containing claim, and noArchitectureOfNetworkBearerAsserted=true; a singular participant ref never implies a containing architecture.Complete one branch, remove or reroute a conflicting architecture-side ref, add a participating claim only when the current question relies on it, or keep the network claim under E.18.NET without architecture use.
    CC-C30TFR-4b Named characteristic bearer and representation boundary.Every architecture characteristic claimed or used by this relation remains on an exact named bearer, and no graph, mathematical description, publication, or network record becomes the architecture claim or its bearer.Name the holon, architecture claim, selected structure, view, relation, or other C.30-governed bearer; demote the representation to its description or publication use.
    CC-C30TFR-4c Member-local, unfolding, and row-reference boundary.Every path, slice, crossing, or valuation named with a network remains bound to its exact owning member TFS and local positions or bindings; a network-aware unfolding selects that same network through its E.18.3 locator; and every NetworkCrossFlowRelationRowRef resolves exactly one row in a current record for that network without replacing the obtaining relation occurrence.Restore the member-local binding or network-locator match; repair or remove a row locator that resolves zero or several rows or points to another network; keep occurrence truth with its direct governor.
    CC-C30TFR-5 No work overread.A selected TFS, network, path, or slice is not treated as work occurrence or work result.Assign the work claim to A.15 or the governing work-result pattern.
    CC-C30TFR-6 No evidence, assurance, or gate overread.The relation is not used as evidence sufficiency, assurance claim, gate decision, or release permission without evidence named by value, assurance, gate, or release pattern application.Assign the claim being made to A.10, G.6, B.3, A.20, A.21, or the release locus named by value when a release claim is being made.
    CC-C30TFR-7 Causal and mathematical boundaries.Causal or intervention claims and mathematical-lens claims are assigned to C.28 and C.29.Apply those governing patterns or narrow the relation's admissible use.
    CC-C30TFR-8 Pin and scalarization boundary.Edition, context, and plane pins plus no-hidden-scalarization claims remain E.18-governed.Add E.18 pin and set-return references or remove the comparison or selection claim.
    CC-C30TFR-9 Hidden relation return.Extracted, generated, coarsened, or partial relation graphs or flow diagrams state the source publication or edition, extraction or probe locus, relation observation class, unexplored regions, and hidden relation-structure return condition when hidden distinctions affect action.Add the missing relation-structure fields or narrow the admissible use.
    CC-C30TFR-10 Useful action.The repair leaves a remaining use: name the selected TFS, path, or crossing; choose the containing or inter-holon branch for a selected network; add correspondence; return to source; assign the claim being made to a governing pattern; or stop.Restore that use, or classify the phrase as reduced-use cue, quote-only wording, blocked transfer, or incomplete rewrite.
    CC-C30TFR-11 Lowering and currentness.The relation states the smallest changed locus when E.18 TFS semantics or pins, E.18.NET network identity or relations, the selected network branch or architecture claims, a relied-on row locator, relation observation class, architecture locus, correspondence, hidden relation-structure return, or related governing boundary changes.Update the affected TFS or network reference, branch, architecture claim, or row locator; narrow admissible use; keep the TFS or network claim inside E.18 or E.18.NET; keep the mathematical-description claim inside E.18.2; keep math-lens use inside C.29; apply the governing pattern to the non-flow claim; lower the relation; or block architecture-to-transformation-flow use.

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