A.6.7:1 - Problem frame

In FPF, a mechanism is a node-level U.Mechanism with explicit argument and result declarations for each operation and a declared LawSet/guards/transport/audit (A.6.1). Many architectures, however, require a stable bundle of multiple different mechanisms that are intended to be used together under shared admissibility and crossing discipline (e.g., a characterization chain, an admissibility-gated selection pipeline, or a universal Part-G kernel that multiple G.* patterns must reuse).

FPF already has MechFamilyDescription, but its meaning is: many realizations of one and the same U.Mechanism. That construct cannot correctly represent a bundle of different mechanisms (different declarations), and trying to overload it creates a level error.

Additionally, FPF reserves “Pack” for publication/shipping bundling (e.g., G.10); using “Pack” to mean “container of mechanisms” creates ontological collisions and downstream confusion.