Connector Model

The early connector model lives in @prox-os/connectors.

Types

Core types include:

• ConnectorProvider
• ConnectorCapability
• ConnectorStatus
• DataSource
• DataCollection
• DataField
• DataRecordPreview
• SyncJob
• ConnectorRecipe
• ConnectorPermissionScope
• ConnectorRiskLevel

Provider Fields

Each provider can describe:

• source type, such as docs, database, project, finance, internal-tools, no-code, low-code, developer, cloud, feed, AI, local-bridge, or static-file;
• connection state, such as connected, mocked, needs OAuth, or planned;
• read capability;
• write-back capability;
• sync maturity;
• risk level;
• auth mode;
• objects exposed by the future connector.

Data Explorer Model

DataCollection describes mock schema and records. It is not a normalized data layer yet. Its purpose is to let Hub UI and docs reason about fields, record counts, last sync, schema drift, and record previews before a real sync engine exists.

Future Server Boundary

Provider clients, OAuth callback handling, token refresh, webhook validation, sync queues, write-back operations, and audit logs must not live in browser packages. They should be introduced behind server-safe packages and explicit permission contracts.