<!-- DOCUMENT CLASS: DEVELOPMENT | SOURCE: 42_INTEGRATION_DISCOVERY_ARCHITECTURE.md -->

SpineWorkspace — Integration Discovery Architecture

Purpose

Integration Discovery determines what external systems and capabilities are available and how they may participate in Business Context and Work.

Integration states

Discovered
→ Selected
→ Configured
→ Connected
→ Authorized
→ Active
→ Healthy
→ Disabled / Deprecated

These states are distinct.

Integration object

Integration
├── Provider
├── Product
├── Version
├── Connector Type
├── Authentication
├── Capabilities
├── Data Domains
├── Read Scope
├── Write Scope
├── Permissions
├── Health
├── Dependencies
└── Lifecycle

Discovery flow

Tenant / User / Host / Work
→ Discover Providers
→ Match Need / Business Domain
→ Find Compatible Connectors
→ Check Policy / Security
→ Check Credentials
→ Check Scope
→ Present Integration
→ Connect
→ Register Capabilities

Contextual discovery

Discovery should be work-aware:

Current Work
+ Role
+ Domain
+ Required Capability
+ Host
        ↓
Relevant Integrations

Example:

Payment Failure
→ payment capability
→ Finance user
→ Stripe / Billing / ERP integrations

Canonical rule

Discovery exposes possibility; Governance determines permission; Connectivity establishes access; Capability determines what can be done.