{"slug":"business/32-hermes-execution","title":"Hermes & Execution","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/32-hermes-execution.mdx","bytes":2693,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nHermes is the execution coordinator. It does not assemble context, make governance decisions, write to the Spine, reconcile provider systems, or select AI models.\n\nFor the canonical execution model, see `docs/spec/INTEGRATEWISE_CANONICAL_SPEC_v1.0.md`, `docs/architecture/PRODUCT_ARCHITECTURE.md`, and `docs/internal/operations/API_REFERENCE.md`.\n\n## Hermes scope\n\nHermes receives authorized ExecutionPlans and:\n\n1. Resolves runtime binding.\n2. Validates schema and permissions.\n3. Routes to a runtime adapter.\n4. Dispatches execution.\n5. Tracks correlation, state, and timeouts.\n6. Reports telemetry and outcome events.\n\nEverything outside that list is out of scope.\n\n## Execution modes\n\nExecution is not monolithic. Supported modes include:\n\n- local execution\n- API Connector action\n- MCP invocation\n- API Wrapper capability\n- AI execution\n- agent-to-agent\n- tool-to-tool\n\nExecution mode and synchronization mode are independent. Work may execute in one mode and converge in another.\n\n## Customer Zero versus external customers\n\nIn Customer Zero, native execution and writeback run inside IntegrateWise infrastructure.\n\nFor external customers, execution is handed off, not centralized. The approved proposal becomes a canonical handoff package. The customer’s execution environment runs the work and posts outcomes back to IntegrateWise.\n\nThis split must be preserved in integration design. Do not assume external tenants have local execution or writeback surfaces inside IntegrateWise.\n\n## Handoff layer\n\nThe handoff layer packages approved proposals into adapter-neutral canonical contracts. Adapters then translate to JSON, MCP, Hermes, OpenClaw, n8n, or other execution targets.\n\nHandoff packages contain:\n\n- actions and mutations\n- context references\n- governance token and approval metadata\n- required authority\n- success criteria\n- adapter routing hints\n\n## Async behavior\n\nAll handoffs are async. The Workbench must not block users waiting for execution. Users track progress by status, not by polling synchronous responses.\n\n## Outcome ingestion\n\nExternal execution agents must POST outcomes to IntegrateWise. Outcome ingestion validates governance tokens, updates execution state, records memory signals, refreshes Workbench projections, and advances Timeline.\n\nOutcome ingestion is a customer responsibility in the handoff model. If outcomes are not returned, the continuity loop is incomplete.\n\n## Retry and recovery\n\nExecution may reach:\n\n- Denied\n- Cancelled\n- Partially Completed\n- Failed\n- Retry Available\n- Recovery Required\n- Sync Conflict\n\nRecovery and retry behavior must be explicit. Do not hide recoverable failures inside generic error states.\n"}