{"slug":"development/runtime/platform","title":"IntegrateWise Platform Runtime & Infrastructure","section":"development","sectionLabel":"Development","status":"unclassified","type":"document","path":"development/runtime/platform.md","bytes":933,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"<!-- DOCUMENT CLASS: DEVELOPMENT | SOURCE: 30_PLATFORM_RUNTIME_AND_INFRASTRUCTURE.md -->\n\n# IntegrateWise Platform Runtime & Infrastructure\n\n## Platform responsibility\n\nIntegrateWise provides the substrate required to run SpineWorkspace:\n\n```text\nIdentity\nConnectivity\nAI\nExecution\nCommunication\nGovernance\nInfrastructure\nObservability\nMetering\nRouting\n```\n\n## Runtime\n\nPrimary implementation direction:\n\n- TypeScript;\n- JavaScript / Node.js;\n- Cloudflare Workers;\n- durable execution;\n- queues;\n- workflows;\n- storage;\n- edge services.\n\n## Infrastructure separation\n\nConceptually separate:\n\n```text\nControl Plane\nOperational Plane\nProduct Plane\n```\n\nThe user product should not become dependent on operator UI implementation.\n\n## Runtime components\n\n```text\nGateway\nSpine\nContext\nProjection\nTwin\nTriage\nAgents\nWorkflows\nHermes\nConnectors\nMCP\nQueues\nDurable Objects\nObservability\n```\n\nPhysical providers may evolve behind contracts.\n"}