G.5:12 - Relations

Builds on (normative): G.Core (core invariants + linkage discipline).

Uses (conceptual dependencies; cited via pins and ids):

• Specification refs required by this result: A.19.CN (CN‑Spec), G.0 (CG‑Spec). Use A.2.6 only when a U.ClaimScope or selected U.ContextSlice changes selection, applicability, or a receiver’s justified reliance; validity and evaluation windows and intended-use restrictions follow the same conditional boundary.

• Method identity and family grouping: A.3.1 for every exact selectable U.Method; A.3.2 only for the same C.2.1 episteme that substantively describes one already admitted Method; and C.2.1 or the defining declaration or pattern for the family relation cited by a registry row. G.5 creates none of those source facts.

• Method composition and selected organization: B.1.5 for the complete composite-Method qualification, A.22 for an independently selected organization that does not constitute one Method, and C.29 for algebraic, graph, matrix, embedding, neural, or other representation-lens use. G.5 consumes exact resulting references and does not construct them.

• Upstream object sets: G.1 (CG‑Frame Card), G.2 (SoTA Pack), G.3 (CHR Pack), and G.4 (CAL Pack). C.22 alone constitutes the TaskSignature. When G.4 CAL gates are current, G.5 additionally consumes the exact TaskMapRef that relates that same TaskSignatureRef to one exact charter and the cited CAL declarations; otherwise the map is absent.

• Evidence and crossings: G.6 for EvidenceGraph citations; F.17 for exact local senses; F.9 for the direct Bridge; C.2.1 for the separate bounded-use proposition; and A.10 or B.3 for reliance or assurance. Add a CrossingBundle under E.18 or a GateCheck under A.21 only when that named downstream use requires one. A G.7 calibration artifact remains a cited policy or evidence input; it does not define the Bridge, bounded use, reliance, or selector actuality.

• Planning and enactment boundary: A.15.2 identifies the U.WorkPlan used as plannedBaselineRef; A.15.3 defines any planned-filling rows kept inside that WorkPlan. G.5 does not redefine them.

• Actual selector use and result availability: A.19.SelectorMechanism and A.6.1 for the actual Select application and bindings; A.13 for every precise performer’s local-kind criterion, classification, same obtaining assignment, scope, situation, window, and evidence; A.15.1 for independent Work admission; A.2.1 for the assignment species and occurrence; and F.6 only for a current exact assignment-bound attribution. When asserted by the account or consumed by its receiving use, A.2.4 governs evidence use, A.10 governs reliance and provenance, G.11 governs currentness, C.2.1 governs a persisted result episteme, B.3 governs assurance, the direct authority pattern governs authorization, and E.24.PUB governs publication. Upstream CPM applications retain their local bindings without requiring separately admitted comparison Work unless that Work is asserted. A root-family assignment reference, temporal overlap, or omission from short wording supplies no attribution and removes no world-side fact. G.5 declarations and records create none of those neighboring facts.

• Joint-use members outside Method dispatch: the direct identity pattern identifies every memberRef; C.11 supplies a local choice result when one is current; another accepted decision or governed inclusion basis may establish all-member inclusion; E.4.PFR states framework-edition dependency or pairwise compatibility separately; G.11 supplies currentness; and E.17/E.24.PUB plus the applicable access-carrier pattern supply exposure and source return. G.5-6 DeclareSetResult consumes the exact members and sufficient basis pins and emits only the selector-facing membership result.

• Causal-use method dispatch: C.28 when method selection involves causal effect, counterfactual comparison, causal fairness, causal policy, causal RL, or simulation-only causal-use claims.

• Optional Method or generator extensions through G.5:Ext.*: C.18, C.19, C.23, plus extension-bearing patterns whose exact Part G admission relation is established when they add extra selector pins.

• Mathematical-lens use: apply C.29 when a selector input depends on a mathematical object or mapping whose use is not yet recoverable—for example, a comparator, distance, descriptor geometry, embedding, normalization, surrogate model, learned representation, QD archive descriptor, model-family label, or model-selection basis. For claim-bearing lens use, recover that object’s mapping mode, preserved or lost structure, and stop condition. A LensCandidateNote may instead retain the recognition and next-action account while CandidateMathObject? remains unresolved. The recorded result is a C.29 lens-use result; non-exhaustive examples include no lens use, a lens-candidate note, a one-line note, a mini-card, a full card, or a note naming the applicable pattern for the stated selector use. That result does not declare a selector result or its supporting records, such as the selected set, selector policy, registry row, shortlist, ranked shortlist, or selector evidence pins; use G.5 for those objects and cite the exact references used.

Provides to: downstream uses such as G.6 audit citations, RSCR emission records with typed triggers and payload pins, and packs shipped through G.10. When a named use needs stable public identity, publish the required family ids, selector policy records, or selected-set identities—such as ShortlistId—to UTS under the applicable identity rule.

Coordinates with: C.11 for local choice results; E.4.PFR for direct framework-edition dependency and pairwise compatibility claims; G.11 for edition currentness; E.17 for a source-backed publication face and return to source; E.24.PUB for a publication occurrence and audience availability; C.19 for pool-policy records; C.32.P2S when a selected-set result declaration feeds architecture problem-to-structure carry-through; C.35 when a generated or discovered structure-bearing output is not yet a selector-facing result; C.24 for enactment-facing next-action records; and C.18 when a Front or Q-front is the source set for a G.5 use.

A Q-front stays a C.18 source set; it is not the emitted G.5 outcome or a SetResultFamily. The G.5 result states one admitted SelectorOutcomeKind; a set result also states Shortlist, RankedShortlist, or JointUseSet, and any public selected-set label resolves to that family.

Architecture discovery boundary: when a generated or discovered structure-bearing output is only a representation or carrier—for example, a description, query result, graph, cluster, or search trace—use C.35 before G.5. Use G.5 only when the live claim is declaration of selected-set result content with selector-policy and selected-set identity; stable public identity and actual publication remain conditional neighboring branches.