FPF Reference

A.6.7:4.1 MechSuiteDescription (data model)

Preface node heading:a-6-7-4-1-mechsuitedescription-data-model:13982

Content

MechSuiteDescription declares:

  1. Suite identifier: a stable identifier for downstream citation.
  2. Membership: a finite set of distinct mechanism intensions.
  3. Suite obligations: shared invariants that every member (and any permitted composition of members) must respect.
  4. Suite contract pins: required citations/pins to contract surfaces and other “anchor” references.
  5. Suite protocols: allowed pipelines of use (permitted ordering and optional steps), expressed at the descriptive level.
  6. Suite audit obligations: required audit/pin visibility for downstream uses (UTS/Path pins, crossing pins, guard pins), expressed as required anchors (not run-time values).
  7. Notes: didactic boundaries and anti-pattern warnings.

A minimal canonical form:

MechSuiteId := Identifier  // PascalCase; stable citation handle. Versioning MAY be carried externally.

SuiteObligation := one of {
   * bridge_only_crossings,
   * two_bridge_rule_for_described_entity_change,
   * transport_declarative_only,
   * penalties_route_to_r_eff_only,
   * guard_decision_tristate(pass|degrade|abstain),
   * unknown_never_coerces_to_pass,
   * gate_decision_separation,
   * guard_lexeme_reservations,
   * cg_spec_cite_required_for_numeric_ops,
   * no_silent_scalarisation_of_partial_orders,
   * no_silent_totalisation,
   * no_thresholds_in_suite_core,
   * crossing_visibility_required,
   * planned_slot_filling_in_work_planning_only,
   * finalize_launch_values_in_work_enactment_only,
   * implementation_export_discipline_when_cited
  +}

SuiteObligations := { SuiteObligation[*] } // clause set; duplicates-free.

MechSuiteDescription := ⟨
  mech_suite_id: MechSuiteId ,
  mechanisms: U.Mechanism.IntensionRef[+] ,     // distinct members; references preferred
  suite_obligations: SuiteObligations ,
  suite_contract_pins: SuiteContractPins ,
  suite_protocols?: SuiteProtocol[*] ,
  suite_audit_obligations?: SuiteAuditObligations ,
  suite_notes?: DidacticNotes
⟩

Norms.

  • Suite identifier. mech_suite_id MUST be present and stable: it is the citation handle for downstream planning and U.Work.Audit.

Well-formedness constraints (admissibility; non-deontic).

  • WF‑MS‑1 (Membership set semantics). mechanisms denotes a duplicates‑free set; order carries no semantics.

  • WF‑MS‑2 (Protocol closure). If suite_protocols is present, then for every ProtocolStep in every SuiteProtocol, step.mechanism ∈ mechanisms.

  • WF‑MS‑3 (Suite ≠ Pack). MechSuiteDescription does not carry shipping/publication payloads; publication remains the role of Pack patterns.

  • WF‑MS‑4 (Suite ≠ Mechanism). MechSuiteDescription contains no OperationAlgebra/LawSet/execution semantics and is not admissible where a U.Mechanism.* node is required.

  • Membership is by mechanism intension (order-free). mechanisms MUST denote a duplicates-free set of distinct U.Mechanism.Intension members. Membership order has no semantics; any intended ordering is expressed only in suite_protocols. A suite is not defined by a shared BaseType.

  • No substitution by MechFamilyDescription. A suite MUST NOT be encoded as a MechFamilyDescription. If desired, a suite MAY additionally cite MechFamilyDescription / MechInstanceDescription for particular members (e.g., “preferred realization for this context”), but such citations do not redefine membership.

  • No “Pack” meaning. A suite MUST NOT be named or treated as a publication pack. Pack remains reserved for publication/shipping bundling (e.g., G.10).

  • No mechanism semantics in the suite. A suite is a Description, not a mechanism: it does not define OperationAlgebra, it does not execute, and it does not absorb gate logic.