{"slug":"docs/canonical/11-HERMES-EXECUTION-AND-PROVIDERS","title":"11 — Hermes, Execution and Providers","section":"docs","sectionLabel":"Docs","status":"unclassified","type":"document","path":"docs/canonical/11-HERMES-EXECUTION-AND-PROVIDERS.md","bytes":1386,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Canonical reference:** `00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md` §20  \n**Status:** Canonical\n\n---\n\n## 1. Hermes\n\nHermes starts after an execution plan has been approved or policy-allowed. It coordinates dispatch, waits, retries, timeouts, observations, recovery/compensation, evidence capture, verification steps and reconciliation workflows.\n\nExecution providers can include APIs, MCP tools, agents, browser runtimes, workflows, local execution, AI models or human tasks.\n\nHermes is not the AI brain. It does not decide whether execution is allowed and it does not own canonical business truth.\n\n## 2. Execution providers\n\n| Provider type | Examples |\n|---|---|\n| API connector | CRM, ERP, support, finance APIs |\n| MCP tool | External MCP server tools |\n| Agent | Spine Agents, specialist agents |\n| Browser | Browser automation runtimes |\n| Workflow | Multi-step coordinated flows |\n| Local | Platform-internal execution |\n| AI model | Model-based reasoning tasks |\n| Human | Human task assignment |\n\n## 3. Execution contract\n\nHermes coordinates: dispatch, waits, retries, timeouts, observations, recovery/compensation, evidence capture, verification steps and reconciliation workflows.\n\nExecution produces outcome events/evidence, and governed writes occur only after the appropriate re-ingestion, verification and reconciliation path.\n"}