fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 21803–21816

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

A.6.7:2 - Problem

The suite user needs one description that can:

  1. represent a set of distinct mechanisms (distinct U.Mechanism),

  2. declare shared obligations that must hold across the set (e.g., crossing visibility, admissibility-citation discipline, guard decision format, penalty routing),

  3. provide shared spec pins (e.g., “this suite is governed by CN-Spec and CG-Spec”), without duplicating those spec contents,

  4. constrain allowed protocols of use (allowed pipelines / permitted ordering), without turning the suite into a mechanism, and

  5. preserve strict distinction among:

    • a suite of mechanisms (MechSuiteDescription),
    • a family of realizations of one mechanism (MechFamilyDescription),
    • a publication bundle (Pack, e.g., G.10).