archi-documentationlisted

<!-- Copyright (c) 2026 JG Systems Consulting Ltd. Source: https://github.com/jgsystemsconsulting/jgs-archi-skills. See LICENSE. --> <!-- SPDX-License-Identifier: MIT --> # archi-documentation ## When to use Orchestrator-dispatched after View Plan confirmation when rationale and a completion summary must be written into the model. ## 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 Record structured rationale for significant views into model documentation fields via MCP, support natural-language change notes without destroying shared elements, and produce a completion summary for the modelling run (SPEC-D-11 / RATE-01..03 / OBJ-6). ## Hard rules 1. **Mutations only after View Plan confirmation** (SPEC-D-15) when writing into the model. 2. **Orchestrator-dispatched only** (SPEC-02). 3. **Follow `docs/CREATE_PATH.md`** including the OBJ-6 rationale / NL-change / completion-summary section. 4. Validate rationale markdown with `python helpers/rationale_schema.py` before write when a file artifact exists (non-empty required sections). 5. NL regeneration must run an impact plan first and reuse element IDs; never recreate shared concepts as duplicates (RATE-02). 6. Validate completion summary with `python helpers/completion_summary_schema.py` before han