Arsenal Autopsy
Bounded agent-facing workflow diagnosis and execution forensics.

Diagnostic Engine Findings

• ✓ Graph Topology Checks — Flags duplicate node names (DUPLICATE_NODE_NAME), missing connections (MISSING_CONNECTION_SOURCE), cycles, and unreachable terminal nodes.
• ✓ Runtime Failure Detection — Pinpoints exact error inception, unhandled timeout cascades, retry storms, and swallowed exceptions.
• ✓ Multi-Format Intake — Accepts n8n_workflow JSON exports, event_array, event_object, and event_jsonl logs.
• ✓ Redaction Guarantees — Automatically scrubs credential keys, secrets, and authorization headers from returned findings and evidence.

Ephemeral Security Boundary

• ! No Durable Data Footprint — Artifacts are processed in an ephemeral temporary directory destroyed immediately on exit. Multi-tenant calls leave zero trace.
• ! Resource Guardrails — Strictly caps incoming artifact payloads at 1 MiB at the gateway boundary (engine self-caps at 64 MiB and 250,000 events).
• ! Offline Code Isolation — The offline Python engine executes zero imported or executable user code; purely inspects data structures.
• ! Finding Limit — Returns up to 2,000 findings per call with explicit limitation notation if truncated.

cURL / HTTP Invocation

# Execute Workflow Diagnosis Call
curl -s https://elyraon.com.co/api/arsenal/v1/products/elyreon.workflow.diagnose/execute \
  -H "X-Arsenal-Key: $ARSENAL_KEY" \
  -H "Idempotency-Key: wf-$(date +%s)" \
  -H "Content-Type: application/json" \
  -d '{
    "artifact_kind": "event_array",
    "content": "[{\"event_id\":\"1\",\"type\":\"error\",\"error\":\"econnrefused\"}]",
    "include_markdown": false
  }'

MCP Tool Definition (JSON-RPC 2.0)

# POST /api/arsenal/mcp
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "elyreon.workflow.diagnose",
    "arguments": {
      "artifact_kind": "n8n_workflow",
      "content": "{\"nodes\":[],\"connections\":{}}",
      "__idempotency_key": "mcp-wf-001"
    }
  }
}