Unclassified

IntegrateWise Developer Platform

Canonical package surface for external developers, AI agents, and partner apps.

Publishable Packages (current release)

Package	Purpose	Consumers
`@integratewise/sdk`	Governed Gateway client: resolve → prepare → explicit approval	Customer Zero, web, mobile, third-party apps
`@integratewise/spine-schema`	Declarative Spine v1 fields, entities, workbench definitions, and registry helpers	Frontends, schema tooling, partner apps

Both packages produce ESM, CommonJS, and type declarations and are validated
with pnpm --filter <package> pack:check before publication.

Planned Public Packages

These names describe the intended platform surface. They are not yet publishable
artifacts and must not be referenced by external consumers until they have a
versioned package, generated declarations, and contract tests.

Package	Purpose	Consumers
`@integratewise/contracts`	Shared API contracts and schemas	All consumers
`@integratewise/types`	Shared TypeScript types	All consumers
`@integratewise/events`	Event contracts and streaming types	Integrations, webhooks, real-time apps
`@integratewise/capabilities`	Capability definitions and resolver contracts	SDK, MCP Pool, governance
`@integratewise/projections`	Projection DTOs, contracts, and client	Workbench, dashboards, SharedWorkbench consumers
`@integratewise/platform-api`	Gateway API client and request/response contracts	Frontends, mobile, third-party apps
`@integratewise/spine-schema-provider`	Resolved spine schema contracts/helpers per category+connector	Runtime, generators, SDK
`@integratewise/connectors`	Connector registry, metadata, OAuth definitions	Marketplace, onboarding, runtime
`@integratewise/connector-types`	Pure types: manifests, capabilities, webhooks, sync	SDK, runtime, external connector builders
`@integratewise/connector-sdk`	Plugin SDK for building connectors	External developers
`@integratewise/mcp-client`	MCP Pool client for AI agents	Claude Code, Cursor, Codex, Twin

Internal / Not Published

Package	Reason
`packages/projection-engine`	Implementation detail; public surface is `projections`
`packages/connector-contracts`	Superseded by `connector-types` and `connectors`
`packages/adk`	Internal agent toolkit
`packages/schema-ai`	Internal AI schema tooling
`packages/core-engine`	Internal runtime
`services/*`	Deployment units, not npm packages

Connector Ecosystem

Public Developer Surface
┌──────────────────────────────────────────────────┐
│ @integratewise/connectors                        │
│ @integratewise/connector-types                   │
│ @integratewise/connector-sdk (optional)          │
└──────────────────────────────────────────────────┘
                      │
                      ▼
Connector Runtime (Platform)
OAuth / Sync / Webhooks / Scheduling / State Machine
                      │
                      ▼
Individual Connector Implementations
Salesforce / HubSpot / Slack / Gmail / Jira / ...

Layer 1: Public Developer Surface

@integratewise/connectors — What Customer Zero and third-party developers use:

registerConnector()
listConnectors()
getConnectorMetadata()
validateConfiguration()
createConnection()
testConnection()

@integratewise/connector-types — Shared definitions:

ConnectorManifest
ConnectorCapability
OAuthConfig
WebhookDefinition
SyncDefinition
EntityMapping
RateLimitPolicy
ConnectorStatus

@integratewise/connector-sdk — Optional SDK for external connector builders:

  id: "my-crm",
  auth,
  capabilities,
  sync,
  webhooks,
});

Layer 2: Connector Runtime (Platform)

Do NOT publish:

connector-manager
connector-sync
connector-webhook
connector-worker
oauth-service
scheduler

Deployed as Cloudflare Workers / services.

Layer 3: Individual Connector Implementations

Option A (recommended): Independent packages

@integratewise/connector-salesforce
@integratewise/connector-slack
@integratewise/connector-gmail
@integratewise/connector-jira

Option B: Bundle everything in @integratewise/connectors

Not recommended once you have 30–50 connectors

Relationship with Platform

Customer Zero / Third-party App
        │
        ▼
   SDK + Contracts
        │
        ▼
     Gateway
        │
        ▼
Connector Runtime
        │
        ▼
Salesforce Connector

Customer Zero never imports connector implementations directly.

Relationship with MCP

Claude Code / Cursor / Codex / Twin
        │
        ▼
IntegrateWise MCP Pool
        │
        ▼
Governed Tools
searchCRM() / syncConnector() / refreshConnection()
        │
        ▼
Connector Runtime
        │
        ▼
Salesforce

MCP Pool exposes governed tools, not raw connector APIs.

Versioning

SDK, contracts, types: coordinated semver via Changesets
Individual connectors: independent semver
Services: deployed via CI/CD, versioned in Cloudflare

Example:

SDK                     2.1.0
Salesforce Connector    1.4.2
HubSpot Connector       3.0.0
Slack Connector         2.7.1

Registry

Artifact	Registry
Current public packages (`sdk`, `spine-schema`)	npm
Private/internal packages	GitHub Packages
Cloudflare Workers	CF Deploy
MCP Pool	Deployed service with versioned API

Migration from Current Packages

Current	Target
`packages/sdk`	`@integratewise/sdk`
`packages/types`	`@integratewise/types`
`packages/connectors`	`@integratewise/connectors`
`packages/connector-contracts`	`@integratewise/connector-types`
`packages/projection-engine`	`@integratewise/projections` (public DTOs/client)
`packages/webhooks`	`@integratewise/events`
`packages/core`	`@integratewise/capabilities`
`packages/gateway-sdk`	`@integratewise/platform-api`
`packages/types/src/spine-schema-provider.ts`	`@integratewise/spine-schema-provider`
`packages/projection-engine`	Keep private; engine stays internal