DOMAINS ON CORE · NOT NEW PRODUCTS

Workflow exports, after parse.

Weavatrix reads the automation files already committed in your repository. Both parsers are domains on Weavatrix Core, on the existing JSON and YAML adapters — not new MCP products, not editors and not executors. No API hop to n8n or Dify.

n8n domain Dify domain →

Two domains, one engine

Same graph, same trust boundary: read-only, network-free, secrets omitted. They share the in-process graph measured at the installed boundary on 2026-08-03, so no separate parser millisecond figures are claimed.

N8N · CORE 1.12.0n8n JSON export

n8n_inventory, n8n_trace, n8n_context and --profile=n8n. Not a live n8n API.

DIFY · ENGINE 2.12.0Dify DSL YAML

dify_inventory, dify_trace, dify_context on the local export. Not the Dify console API.

Boundary: both domains are read-only, contact no instance, and omit secrets. Core 1.12.0 ships 50 read-only MCP operations with engine pin weavatrix-rust 2.11.0; engine 2.12.0 on GitHub adds the Dify tools. MIT license · Security