FPF Reference

A.6.7:4.6 Examples (tell–show–show discipline)

Preface node heading:a-6-7-4-6-examples-tell-show-show-discipline:14188

Content

Example 1 (conformant). A characterization legality suite:

CHRMechanismSuiteDescription : MechSuiteDescription :=
  mech_suite_id = CHRMechanismSuiteId
  mechanisms = { UNM, UINDM, USCM, ULSAM, CPM, SelectorMechanism }
  suite_obligations includes:
    bridge_only_crossings,
    penalties_route_to_r_eff_only,
    guard_decision_tristate(pass|degrade|abstain),
    gate_decision_separation,
    cg_spec_cite_required_for_numeric_ops,
    no_silent_scalarisation_of_partial_orders,
    crossing_visibility_required,
    planned_slot_filling_in_work_planning_only,
    finalize_launch_values_in_work_enactment_only
  suite_contract_pins requires: {CNSpecRef, CGSpecRef}
  suite_protocols includes:
    normalize → indicatorize → score → (fold_Γ?) → compare → select → publish/telemetry

This description is not a MechFamilyDescription (because it contains multiple distinct mechanisms), and it is not a Pack (because it does not ship artifacts; it only declares membership and shared obligations/pins/protocols).

Example 2 (non-conformant). Misusing a family as a suite:

CHRMechanismFamily : MechFamilyDescription := { UNM, UINDM, USCM, ... }

This is a level error: MechFamilyDescription is reserved for realizations of a single mechanism intension.

Example 3 (non-conformant). Turning a suite into a hidden gate:

  • The suite declares GateDecision values or embeds a DecisionLog.
  • The suite defines acceptance thresholds (“pass score ≥ 0.7”) as part of suite obligations.
  • The suite embeds Φ/CL tables or invents ad-hoc “transfer edges”.

All violate the separation between mechanism/suite descriptions and gate-level operational control.