Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:35:15 UTC

A.19.SelectorMechanism:1 - Problem frame

FPF’s Characterization (CHR) suite treats selection as a mechanism boundary within the suite (authoritative membership: A.19.CHR:4.2). Suite membership is a set; order has no semantics. Any intended ordering is expressed only via suite_protocols (A.19.CHR:4.5), under suite obligations (A.19.CHR:4.3).

Within the suite‑closed protocol, SelectorMechanism appears as the select stage (after admissible comparison; optional stages remain optional per suite_protocols). The kernel’s role is concept‑level and governed by CN‑Spec and CG‑Spec:

  • consume admissible comparison outcomes without collapsing them into a hidden scalar,
  • apply explicit criteria and policy references, and
  • return a selected-set result under policy-bound defaults, with the Select application and its argument and result bindings recoverable; dated Work and evidence-provenance grounds enter when the account asserts them or the receiving use consumes them.

The kernel uses the CHR suite SlotKind lexicon (A.19.CHR:4.2.1) to prevent SlotKind drift across specializations and across SoTA wiring layers.