archi-traceabilitylisted

<!-- Copyright (c) 2026 JG Systems Consulting Ltd. Source: https://github.com/jgsystemsconsulting/jgs-archi-skills. See LICENSE. --> <!-- SPDX-License-Identifier: MIT --> # archi-traceability ## When to use Orchestrator-dispatched after View Plan confirmation when cross-layer traces must be created or gaps reported. ## 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 Establish explicit cross-layer traces (motivation to business to application to technology, plus strategy/implementation when in scope) via MCP relationships, and report missing links as gaps (SPEC-D-08 / OBJ-3). ## Hard rules 1. **Mutations only after View Plan confirmation** (SPEC-D-15 / NG-3). 2. **Orchestrator-dispatched only** (SPEC-02 / SPEC-D-13). 3. **Follow `docs/CREATE_PATH.md`** (OBJ-4 coherence + OBJ-5 compliance explain-and-propose). 4. **No ArchiMate metamodel table dumps** (NG-4). 5. Prefer relating existing elements; create relationship-only structure unless hand-off authorizes new bridging elements. 6. Optional offline: `python helpers/compliance_validate.py slice.json` on proposed/created edges; never silent-apply illegal combos. ## Inputs | Field | Required | Notes | |-------|----------|-------| | Confirmation status | yes | approved | | Intent summary | yes | |