archi-viewpoint-selectlisted

<!-- Copyright (c) 2026 JG Systems Consulting Ltd. Source: https://github.com/jgsystemsconsulting/jgs-archi-skills. See LICENSE. --> <!-- SPDX-License-Identifier: MIT --> # archi-viewpoint-select ## When to use Orchestrator-dispatched. Use after a draft View Plan exists and each viewpoint must be traced to stakeholder, concern, purpose, and abstraction. Never user-invoked. ## Prerequisites Archi with the JGS Archi Bridge MCP (see docs/MCP.md). Python 3.10+ for helpers. Follow docs/CREATE_PATH.md. Specialists require View Plan confirmation `approved` before mutations. Orchestrator-dispatched specialist. Not a primary user entrypoint. ## Purpose Given intent plus draft viewpoints (from the orchestrator), produce a **Viewpoint Trace Table** proving each choice maps to stakeholder, concern, purpose, and abstraction level (VSEL-04 / VIEW-01). When no standard viewpoint fits, propose an organisation-specific viewpoint with justification that stays ArchiMate-compliant (VSEL-06 / VIEW-02). List rejected alternatives so the user can see the choice space (VSEL-07 / NG-3). ## Hard rules 1. **No MCP mutations.** Do not call `create-element`, `create-relationship`, `create-view`, `clone-view`, `bulk-mutate`, `update-element`, `update-relationship`, `delete-element`, or other mutating tools. Read-only resources only (VSEL-10). 2. **Do not copy ArchiMate metamodel tables** into the trace or chat. Prefer MCP resources for definitions (NG-4). Offline, use plain-language names and th