A.2.6:20.1.3.1 - Selected names (normative)
| 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.