From d240b7962b36fe9f5c684e75c70290088a72e96b Mon Sep 17 00:00:00 2001 From: vp Date: Thu, 12 Mar 2026 14:25:19 +0300 Subject: [PATCH] fix: normalize USM checklist language for scope objects --- FPF-Spec.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/FPF-Spec.md b/FPF-Spec.md index 0cdece9..83df254 100644 --- a/FPF-Spec.md +++ b/FPF-Spec.md @@ -3817,7 +3817,7 @@ When **G** is a **set‑valued scope**, composition becomes precise: serial depe | Force | Tension to resolve | | ------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **One mechanism vs two worlds** | We must serve both **knowledge about the world** (claims) and **doing work in the world** (capabilities) **without** duplicating concepts. | -| **Locality vs interoperability** | Scope must be **context‑local** and precisely checkable, yet transferable across Contexts via Bridges **without redefining** the characteristic. | +| **Locality vs interoperability** | Scope must be **context‑local** and precisely checkable, yet transferable across Contexts via Bridges **without redefining** the scope object. | | **Expressivity vs minimal vocabulary** | Teams need to capture rich conditions (time windows, environment, versions) but not explode the lexicon into “envelope/applicability/…” variants. | | **Static content vs operational change** | Claims may hold broadly while current operations are narrow (or vice versa). The mechanism must keep “what is true” and “what can be done” aligned yet distinct. | | **Open‑world exploration vs closed‑world gating** | Exploration benefits from permissive drafts; **gates** require crisp, observable checks. The same scope object must support both. | @@ -3837,7 +3837,7 @@ When **G** is a **set‑valued scope**, composition becomes precise: serial depe **Lexical commitments (normative):** — In normative text and guards, use **Claim scope (G)**, **Work scope**, and **Publication scope**. -— Do **not** name the characteristic “applicability/envelope/generality/capability envelope/**publication applicability**/validity.” Those words are permitted only as explanatory aliases in notes. +— Do **not** name the scope object “applicability/envelope/generality/capability envelope/**publication applicability**/validity.” Those words are permitted only as explanatory aliases in notes. ### A.2.6:6 - Normative Definitions @@ -4125,7 +4125,7 @@ For empirical claims and operational capabilities, **R** typically binds evidenc ### A.2.6:9 - Lexical Discipline (Part E compliance) -**L‑USM‑1 (names).** Use **Claim scope (G)** for epistemes, **Work scope** for capabilities, and **Publication scope** for publication carriers. Use **Scope** only when discussing the abstract mechanism. Avoid naming any **characteristic** as “applicability,” “envelope,” “generality,” “capability envelope,” or “validity”. +**L‑USM‑1 (names).** Use **Claim scope (G)** for epistemes, **Work scope** for capabilities, and **Publication scope** for publication carriers. Use **Scope** only when discussing the abstract mechanism. Avoid naming any **scope object** as “applicability,” “envelope,” “generality,” “capability envelope,” or “validity”. **L‑USM‑2 (Work/Run).** Prefer **Work/Run** vocabulary from A.15 for system execution contexts. Do not introduce “operation/operating” as characteristic names; use **Work scope**. @@ -4270,12 +4270,12 @@ Implicit “latest” is not allowed. If multiple contributors declare different | ID | Requirement | | ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **CC‑USM‑1 (Declaration).** | Epistemes **SHALL** declare **`U.ClaimScope`**, capabilities **SHALL** declare **`U.WorkScope`**. The abstract `U.Scope` MAY be used in architectural notes but not in guards. | -| **CC‑USM‑2 (Set‑valued).** | Scope characteristics are **set‑valued** over `U.ContextSlice`. Implementations MUST support **membership**, **intersection**, **SpanUnion**, **translate**, **widen/narrow**, **refit**. | +| **CC‑USM‑2 (Set‑valued).** | Scope objects are **set‑valued** over `U.ContextSlice`. Implementations MUST support **membership**, **intersection**, **SpanUnion**, **translate**, **widen/narrow**, **refit**. | | **CC‑USM‑3 (Coverage guards).** | ESG and Method–Work guards **MUST** use `Scope covers TargetSlice` predicates and **MUST** specify `Γ_time`. Guards fail closed. | | **CC‑USM‑4 (Serial intersection).** | Along essential dependency paths, effective scope **SHALL** be the **intersection**; empty intersection invalidates the path. | | **CC‑USM‑5 (SpanUnion constraints).** | Parallel scope **MAY** use **SpanUnion** only if independent support lines are **justified**; published union **MUST NOT** exceed supported slices. | | **CC‑USM‑6 (Cross‑context).** | Any Cross‑context use **MUST** declare a Bridge and **CL**; CL penalties apply to **R**, not **F/G**. | -| **CC‑USM‑7 (No synonym drift).** | In normative text and guards, **MUST** use **Claim scope (G)** or **Work scope**. Terms “applicability/envelope/generality/capability envelope/validity” **MUST NOT** name the characteristic. | +| **CC‑USM‑7 (No synonym drift).** | In normative text and guards, **MUST** use **Claim scope (G)** or **Work scope**. Terms “applicability/envelope/generality/capability envelope/validity” **MUST NOT** name the scope object. | | **CC‑USM‑8 (Determinism).** | Membership evaluation **MUST** be deterministic given the slice tuple; no heuristic “close enough” matching. | | **CC‑USM‑9 (Edition triggers).** | ΔG± (widen/narrow) constitutes a **content change**; refit does not. | | **CC‑USM‑10 (Publication discipline).** | Publication carriers that gate usage **SHALL** declare `U.PublicationScope`. For any publication **about** an episteme or capability, `PublicationScope` **MUST** be a subset of the underlying `U.ClaimScope`/`U.WorkScope`. Cross‑context publications **MUST** cite Bridge + CL; CL penalties **apply to R only** (scope membership unchanged). |