E.17:5.0 - Publication-scope and face-profile binding (normative)

• Ordinary selection. Start with the current source account, intended reader/use, and the smallest publication-form set needed now. A one-form result is valid; adding another form requires another current reader/use or a material distinction that the first form cannot carry safely.
• Bounded use before exact scope. Alongside each selected publication form, state the separate bounded-use declaration in ordinary prose. Identify an exact U.PublicationScope under A.2.6 when scope identity must travel across publication, comparison, exchange, dispute, or reliance. The scope establishes neither U.View membership nor permission, evidence, work, assurance, or release, and it encodes neither the selected source, viewpoint, publication-form profile, Publication Characteristics, nor carrier.
• Resolve before authoring. Reuse an existing viewpoint when its concerns and rules fit the reader/use. Author a new reusable viewpoint, or create a project-local family declaration under E.17.1, only when the current need cannot be served truthfully by an existing viewpoint or a simple bounded publication face. E.17.0 tests viewpoint conformance. Use E.17.1 to identify the catalogue edition, ordinary family designator, local declaration claim block, and needed U.ViewpointRef subset.
• Optional profile. A formal MVPK profile fixes exact publication-form designators, any declared partial order, Publication Characteristics and pins, and any cross-context or reference-plane constraints. These fields apply only to the optional formal or load-bearing branch, not to the ordinary first result.
• Canonical labels. PlainView, TechCard, InteropCard, and AssuranceLane are historical MVPK face designators. None identifies a U.View, U.Viewpoint, evidence object, assurance result, or gate. Use only the designators needed by the current readers; MVPK-Max is the optional profile in which all four have an actual use.