A.2.6:6.5 - U.PublicationScope — scope of a publication view or publication form

Carrier. A publication view or form is rendered on a carrier; the carrier is a separate object. Meaning. The set of U.ContextSlice where a publication (a view, card, or lane about some object or morphism) is admissible for use within its underlying Claim scope or Work scope.

Relation to other scopes (normative).

• If the publication is about an episteme E: PublicationScope(view_E) ⊆ ClaimScope(E).
• If the publication presents a qualified holder-ability claim C for work admission: PublicationScope(view_C) ⊆ WorkScope(C), where WorkScope(C) is the work-condition basis designated by that claim. Any relied-on episteme ClaimScope remains a separate constraint; stating the ability in an episteme does not turn its WorkScope into ClaimScope.
• If the publication is about a composition, its scope is a subset of the intersection of the exact contributing scopes. When exact local senses require translation, use section 7.5 for each affected source scope: obtaining F.9 Bridge, separate affirmative C.2.1 use claim, and current A.10 or B.3 reliance before the returned scopes are intersected.

Expression. Declare U.PublicationScope as an exact predicate over only the U.ContextSlice selectors that restrict publication use: for example versioned standards, environment, audience, interface availability, exact local senses, or gammaTime when time changes membership. It may be narrower than the underlying scope but must not be wider.

Algebra and Delta-moves. Publication scope uses the USM algebra. A widened publication scope is admissible only when the resulting set remains a subset of every relevant underlying Claim scope or Work scope and the publication conditions support each added slice; the underlying scope need not change when it was already broader.

Orthogonality to measurement. U.PublicationScope is a USM scope object (set‑valued), not a CHR Characteristic and MUST NOT appear as a slot in a U.CharacteristicSpace.

View refinement (profiles). When a publication profile or view refines another, its U.PublicationScope MUST be a subset of the scope of the profile or view it refines (for example, a typed card may require additional pins).