G.8:1 - Problem frame

Method families compete within a CG‑Frame, but dispatch is only lawful if (i) admissibility decisions remain tri‑state and auditable, (ii) evidence and crossings are explicitly citable (by ids, not prose), and (iii) selection preserves set-return semantics under partial orders. In practice, SoS‑LOG rules (C.23) and “maturity stories” are often distributed across prose, dashboards, and ad‑hoc checklists, with thresholds embedded where they do not belong and with missing pins for evidence paths, crossings, and editions.

This pattern provides the missing packaging kit: a selector‑facing, UTS‑citable bundle that binds (a) rule ids (semantics governed by C.23), (b) an ordinal/poset maturity ladder (published as a citable card), and (c) explicit wiring to Acceptance (G.4), EvidenceGraph (G.6), selection/registry (G.5), and refresh (G.11)—without creating any shadow governing spec refs.