A.19.SelectorMechanism:5.3 - Show, U.Episteme example

Scenario. A methods group selects a declared set of analysis methods for a task. Candidates are method family refs. The group wants diversity in the selected set, but does not want diversity metrics to silently become dominance criteria.

• CandidateSetSlot = {Family1, Family2, Family3, Family4}

• The selection conditions declare which binary method-family comparisons are required. A finite basis identifies every relied-on CPM application, its exact pair, eligibility value, and own output binding; the Selector’s ComparisonResultSlot argument is their exact justified-token union.

• TaskSignatureSlot is present and is the single policy-default slot or ref:

  • PortfolioMode and dominance regime,
  • budgeting and telemetry hooks (when used).

• CriteriaSlot declares that diversity signals are telemetry unless explicitly promoted by policy.

Outcome.

• SelectionSlot returns a selected set; any archive‑style behavior is a specialization and policy choice, not a hidden kernel default.
• The dated selection U.Work, actual Select application with its TaskSignatureRef.edition and SelectionSlot bindings, and A.10 evidence-provenance path support later explanation without embedding tool tokens into the kernel.