{"slug":"product/connectivity","title":"Connectivity & Connector Architecture","section":"product","sectionLabel":"Product","status":"unclassified","type":"document","path":"product/connectivity.mdx","bytes":1219,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n\n\n\n## Purpose\n\nConnect SpineWorkspace to systems where business data and actual operational state exist, feeding the Business Context Spine.\n\n## The Tier-0 Principle\n\n> **Business Context is the semantic foundation of SpineWorkspace.** Connectors feed the Business Context Spine, which IS the organization's memory. Without Business Context, connectors have nothing to serve.\n\n## Connector classes\n\n```text\nOAuth / Unified API\nMCP\nREST / GraphQL API\nWebhook\nEvent\nFile / Document\nCustom Provider\nExternal Agent\n```\n\n## Architecture\n\n```text\nSource System\n ↓\nConnector\n ↓\nLoader / Event Handler\n ↓\nNormalizer\n ↓\nBusiness Context Spine\n```\n\nFor writes:\n\n```text\nSpineWorkspace\n ↓\nCapability\n ↓\nGovernance\n ↓\nExecution Binding\n ↓\nConnector\n ↓\nSource System\n```\n\n## Provider authentication vs IntegrateWise authentication\n\n- IntegrateWise auth establishes tenant/workspace/capability/governance access.\n- Provider auth establishes consent to external-system data/actions.\n\n## Connector invariant\n\nFrontend must not directly import provider SDKs or call provider APIs.\n\nFrontend calls stable platform contracts.\nPlatform resolves connector/provider implementation.\n"}