A.2.6:0.1 - Kind Settlement

U.ContextSlice and U.Scope are the durable USM values for scope work. U.ClaimScope, U.WorkScope, and U.PublicationScope are C.3-governed scope specializations under U.Scope, not independent root ontics. ContextSliceSet := Set[U.ContextSlice] is the mathematical ValueKind whose values are exact sets of independently identified context slices; it is neither a durable scope nor another U-kind. Each exact U.Scope has one ContextSliceSet value as its extension under the effective reference scheme.

One-line summary. A.2.6 lets a practitioner test one exact U.ContextSlice against one exact set-valued scope. For a claim, member(slice, claimScope) is true or false: true admits the claim-scope condition and false stops that use. An evaluation returns unknown when its available basis cannot determine membership. The predicate is not a U.Relation occurrence.

Use this pattern when a receiving action needs to decide whether a claim, capability, or publication use covers one exact combination of standards, environment, local sense, platform, cohort, or time selectors.

First useful move. Name the exact claim, its exact U.ClaimScope, and the target U.ContextSlice; evaluate membership. Stop on false. On unknown, obtain the missing evaluation input, narrow the attempted use, or abstain. Add a result episteme or table only when the receiving use needs one. If exact local senses must be translated, first name the obtaining F.9 Bridge, then state the separate affirmative C.2.1 claim for this translation’s direction, rule, and tolerance. Before using the translated scope, establish evidence-based reliance through A.10 or assurance-based reliance through B.3.

What goes wrong if missed. Teams infer coverage from a document, table, “current context” label, or selected structure; treat an unevaluated slice as excluded; or mint ScopeDelimitationRelation occurrences for included and excluded slices. Those moves collapse predicate truth, evaluation, representation, and structure.

What this buys. One set-valued scope algebra supports exact membership, intersection, supported union, translation, widening, narrowing, and refit while keeping claim content, evaluation work, result epistemes, model-applicability relations, and selected structures separate. Vocabulary boundary. Use these scope names in live FPF wording:

• For epistemes, the only scope type is U.ClaimScope (nick G in F–G–R).
• For system capabilities, the only scope type is U.WorkScope.
• For publication views or forms, the only scope type is U.PublicationScope.
• The abstract architectural notion is U.Scope — a durable scope value identified extensionally through one exact ContextSliceSet value under the effective reference scheme. Intersection, SpanUnion, translation, widening, and narrowing operate on those extensions; refit changes an expression without changing the extension. U.Scope is not a U.Characteristic and MUST NOT appear in any CharacteristicSpace.

Source words such as applicability, envelope, generality, and capability envelope may appear only as explanatory aliases in non-normative notes.

Cross‑references.

• C.2.3 (Unified Formality F) and C.2.2 (F–G–R): this pattern defines G as U.ClaimScope.
• A.2.2 (Capabilities): capability gating SHALL use U.WorkScope.
• F.9 (Bridges): use an exact obtaining Bridge only when membership content must be translated across exact local senses; a different label or reference scheme alone does not trigger translation. F.9 supplies the direct semantic relation only. The separate C.2.1 claim states the exact translation use, direction, rule, tolerance, and polarity; A.10 or B.3 governs reliance on that claim.
• Part E (Publication discipline; e.g., E.17 MVPK): publication views, cards, and lanes MAY declare U.PublicationScope to bound where a publication is admissible; U.PublicationScope MUST NOT widen the underlying U.ClaimScope/U.WorkScope. (USM supplies the scope calculus; Part E supplies publication discipline.)