A.2.6:20.1.3 - F.18 Term Selection — Unified Tech & Plain names

Concept in A.2.6	Unified Tech (lexicon)	Unified Plain (manager‑friendly)	Allowed short form	Avoid / unpack
Addressable evaluation context	`U.ContextSlice`	Context slice	Slice (when local)	“domain” (as guard input), “latest” time
Extensional scope value	`U.Scope`	Scope	—	“applicability”, “envelope”, “validity” (as characteristic names)
Episteme applicability	`U.ClaimScope` (*nick G)	Claim scope	G	“generality”, “applicability/envelope (of claim)”
Capability applicability	`U.WorkScope`	Work scope	—	“capability envelope”, “operational applicability”, “operation scope”
Time selector	`Γ_time`	Time selector	—	implicit “latest”
Exact local-sense translation	Obtaining F.9 Bridge + separate affirmative C.2.1 use claim + current A.10 or B.3 reliance	Bridge, translation rule and tolerance, checked reliance	—	automatic Bridge use or treating a loss score as permission
Parallel coverage	SpanUnion	Union of supported areas	—	unqualified “union” without independence
Serial dependency	Intersection	Intersection of scopes	—	ordinal “more/less general” language
Scope edits	ΔG+ (widen), ΔG− (narrow), Refit, Translate	Widen, narrow, refit, translate	—	stealth widening (“it’s obvious”)
Optional didactics	`Detail (D)`, `AbstractionTier (AT)`	Detail and abstraction tier	D / AT	avoid as G substitutes

Naming rationale:

“Scope” rather than “envelope/applicability/validity”. “Scope” is idiomatic in SRE/SW; “validity” clashes with Validation Assurance (LA), and “envelope” suggests geometry rather than membership.
“Claim scope” vs “Work scope”. These names distinguish claim uses and capability uses of the common set-valued scope notion.
Keep G. The F–G–R triple is canonical; we retain G as nickname for Claim scope.
“Context slice” keeps the evaluation target addressable through its exact declared selector schema and values; one membership predicate may inspect only a projection without reidentifying the slice.
“Operation”, “operating”, and “validity” avoided. They are overloaded in existing FPF lanes (Work, Run, and LA) and create policy ambiguities in guards.

Use “Claim scope (G) covers TargetSlice” and “Work scope covers JobSlice” in guards.
When time changes membership, name exact gammaTime and its membership boundary; never say “latest.” A time-independent predicate need not inspect gammaTime, but keep every selector already declared in the slice.
To compose, say: “intersection along dependency paths; SpanUnion across independent support lines.”
When exact local-sense translation is current, say: “through an obtaining F.9 Bridge and a separate affirmative C.2.1 claim for this direction, rule, and tolerance; rely on it only through the current A.10 or B.3 branch, then evaluate membership on the returned scope.”
When widening/narrowing, write “ΔG+ / ΔG−” and log the support change; use “Refit” for unit/param normalization.

local context phrase	Use in USM wording
“Context of use” (NIST, ASME/FDA)	Claim scope (G) on explicit Context slice
“Operating modes/situations” (ISO 26262)	Work scope with measures & qualification windows
“Target (class/shape)” (SHACL/OWL)	Claim scope predicates (membership)
“Architecture view context” (42010)	Context slice + Scope checks inside the view
“Capability envelope” (safety documents)	Work scope
“Domain” (informal)	Context slice elements; not acceptable as a guard input