<!-- DOCUMENT CLASS: DEVELOPMENT | SOURCE: 24_CONNECTIVITY_CONNECTOR_ARCHITECTURE.md -->

Connectivity & Connector Architecture

Purpose

Connect SpineWorkspace to systems where business data and actual operational state exist.

Connector classes

OAuth / Unified API
MCP
REST / GraphQL API
Webhook
Event
File / Document
Custom Provider
External Agent

Architecture

Source System
 ↓
Connector
 ↓
Loader / Event Handler
 ↓
Normalizer
 ↓
Spine

For writes:

SpineWorkspace
 ↓
Capability
 ↓
Governance
 ↓
Execution Binding
 ↓
Connector
 ↓
Source System

Provider authentication vs IntegrateWise authentication

• IntegrateWise auth establishes tenant/workspace/capability/governance access.
• Provider auth establishes consent to external-system data/actions.

Connector invariant

Frontend must not directly import provider SDKs or call provider APIs.

Frontend calls stable platform contracts.
Platform resolves connector/provider implementation.