FILE /Users/forgebot/.hermes/artifacts/import-leads-map/import-leads-file-map.html

Under the hood / 12-node source map

Import Leads: From Request To Files

Skills tell the agent what to do. Procedures explain how. Scripts execute it. Stored data keeps its place.
This is a map of the installed implementation—not a picture of model internals.

Agent reads / follows instructionsCode dispatch / callsData / API access

01 · Request & skills02 · Procedures & entry points03 · Working code04 · Persistence & services

Click any node for exact paths and responsibilities. Supporting skills and procedure references are grouped to keep the graph at 12 nodes. Selected major relationships are shown; this is not an exhaustive import graph.

What “procedure” means here: ordered Markdown instructions inside SKILL.md and references/commands.md. There is no separate procedures/ directory or standalone workflow engine in this package.
Evidence: local source files, resolved skill paths and default-profile external skill directory inspected for this diagram. Readiness notes report fixture-tested code, not completed live-import acceptance. No CRM writes were performed for this map.
Hermes skills documentation · Preview is unlisted and link-accessible, not private. Only architecture metadata is included.

Import Leads: From Request To Files

Request → Agent

Import Leads

Service Rules

How To Run It

CLI Entry Point

Production Coordinator

Planning Rules

Guarded Executor

Live Adapters

State Access

Durable Work Folder

Actual Services