Jgs V1

jgs-v1 Dispatcher

When to use

Use when you are not sure which specialist fits: describe the request in plain English and the dispatcher routes it to the right FREE-tier skill, flagging anything that needs PRO.

Prerequisites

• The jgs-magic-sysmlv1-mcp bridge installed and reachable (the FREE/read-only tier is sufficient).
• A SysML v1 project open in CATIA Magic / MSOSA. You are the entry point for all SysML v1 (jgs-magic-sysmlv1-mcp) free-tier skills. Execute the steps below in strict order. Do not skip steps or reorder them.

Step 1 — Liveness check (ALWAYS FIRST)

Call mcp__jgs-sysmlv1__ping.

• If the call fails (tool error, timeout, connection refused): emit the message below and HALT. Do not proceed to Step 2, do not call get_licence, do not route.

  Bridge unreachable. The jgs-magic-sysmlv1-mcp bridge is not responding. Ensure CATIA Magic is running and the v1 bridge plugin is active, then retry.

• If the call succeeds: continue to Step 2.

Step 2 — Licence check

Call mcp__jgs-sysmlv1__get_licence.

Handle the three possible outcomes:

Step 3 — Tier guard (BEFORE routing)

Scan the user's request for write-intent phrases. Check for any of the following patterns (case-insensitive):

• "rename [element/block/property]"
• "create [a block/element/package/diagram]"
• "delete [element/block]"
• "add [a relationship/satisfy/dependency]"
• "move [element]"
• "update [element/property]"
• "set [a value/property/documentation]"
• "change [element]"
• "modify [element]"
• "populate [diagram]"
• "edit [element]"

If any write-intent phrase is detected and the tier is FREE:

Write operations require PRO or ENTERPRISE tier.

This pack is read-only. The operation you requested ("[phrase detected]") modifies the model, which requires an upgraded licence.

Would you like me to do a read-only equivalent instead? For example, I can show you the current state of the element, run an impact analysis, or produce an audit report.

HALT — do not route. Do not call any tool.

If write-intent is detected and the tier is PRO or ENTERPRISE: proceed normally — all free-tier skills work at higher tiers, and the bridge enforces write safety independently.

If no write-intent is detected: proceed to Step 4.

Note: This is a best-effort heuristic, not a security boundary. The bridge enforces read-only access through the absence of enable_writes. The tier guard exists to give the user a clear explanation before hitting a bridge-level rejection.

Step 4 — Route to specialist skill

Match the user's request against the routing table below. Use the first match found. If no match or ambiguous (see Ambiguity rules), follow the Ambiguity procedure.

Routing table

PRO-tier capabilities (not in this free pack)

The following are read-only but premium capabilities that ship in the separate SysML v1 PRO skills pack (sold by JG Systems Consulting Ltd), not in this free pack. If the request matches one of these intents, do not route to a specialist — instead tell the user it is a PRO capability and show the upgrade path below.

Response template:

That capability ("[intent]") is part of the SysML v1 PRO skills pack (read-only migration tooling, sold separately). This free pack covers read / navigate / analysis only. To enable it, contact JG Systems Consulting Ltd at support@jgsystemsconsulting.com to upgrade.

Ambiguity rules

Ambiguity occurs when:

• (a) Zero keyword groups match, or
• (b) Two or more distinct specialist routes match simultaneously, or
• (c) The request contains only ? or help

Collision exception: If audit keywords match alongside one other route, default to jgs-v1-audit — do not treat this as ambiguous. Exception to the exception: if the non-audit match is clearly dominant (e.g. the user explicitly says "impact" but also mentions "audit" in passing), ask the user to clarify rather than defaulting.

When ambiguous (and no exception applies), present this menu:

I can help with several things using the SysML v1 skills. Which are you after?

1. Navigate — explore the model structure, packages, blocks, and diagrams
2. Inspect — full dossier on a single element (type, ports, relationships, stereotypes, requirement links)
3. Search — full-text search across element names
4. Impact analysis — find what uses an element and assess blast radius before a change
5. Audit — heuristic health check: naming, documentation, requirements, duplicates, unused, methodology
6. Report — model-health summary + Requirements Traceability Matrix + native validation, exported to a file
7. Diagrams — inventory and export diagram images (visual review pack)
8. Units — look up units, quantity kinds, and standard-library types
9. Status — bridge safety tier/mode and recent edit history
10. Fix plan — turn audit findings into a remediation plan (recommended actions + computed fixes + the PRO tool to apply each)

Migration inventory and cross-model compare are PRO-tier capabilities (SysML v1 PRO skills pack) — ask to upgrade.

Ask the user to pick a number or describe what they need, then route accordingly.

Step 5 — Dispatch

Invoke the matched skill using natural language skill composition:

Use skill <skill-name> for this request: [pass through the user's original request verbatim]

Do not call bridge tools directly at this stage — the specialist skill owns its own tool calls.

Missing skills

The following skills are provided by separate packs. If a skill is invoked and not found, tell the user which pack provides it:

Direct invocation note

When specialists are invoked directly (not via this dispatcher), they skip liveness and tier checks — raw bridge errors will surface if the bridge is unavailable. This is by design. This dispatcher is the recommended entry point for all jgs-magic-sysmlv1-mcp work.

Common Mistakes

No tool gotchas — this dispatcher only calls ping and get_licence to route; the model-introspection, diagram, and write caveats live in each specialist skill it dispatches to.