{"slug":"development/contracts/execution","title":"Execution Fabric & Hermes","section":"development","sectionLabel":"Development","status":"unclassified","type":"document","path":"development/contracts/execution.md","bytes":1002,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"<!-- DOCUMENT CLASS: DEVELOPMENT | SOURCE: 23_EXECUTION_FABRIC_HERMES.md -->\n\n# Execution Fabric & Hermes\n\n## Purpose\n\nPerform approved work through reliable, observable, reconciled execution.\n\n## Flow\n\n```text\nIntent\n→ Capability\n→ Immutable Execution Plan\n→ Governance\n→ Approval when required\n→ Hermes\n→ Tool / API / MCP / Workflow\n→ Source System\n→ Receipt\n→ Reconciliation\n```\n\n## Hermes\n\nHermes is the execution/orchestration runtime.\n\nIt is not the product's canonical memory.\n\nIt receives governed work and coordinates execution.\n\n## Execution requirements\n\n- tenant isolation;\n- idempotency;\n- correlation;\n- causation;\n- retries only when safe;\n- timeout handling;\n- dead-letter handling;\n- receipts;\n- audit;\n- reconciliation.\n\n## Ambiguous result\n\n```text\nUnknown result\n→ Stop automatic retry\n→ Reconcile source state\n→ Continue only after state is known\n```\n\n## Outcome\n\nTechnical execution success is not sufficient. Business outcome must be verified/reconciled.\n"}