Unclassified
SpineWorkspace — Host-Aware Architecture
<!-- DOCUMENT CLASS: DEVELOPMENT | SOURCE: 41_HOST_AWARE_ARCHITECTURE.md -->
SpineWorkspace — Host-Aware Architecture
Company: IntegrateWise
Product: SpineWorkspace
Definition
Host Aware means SpineWorkspace understands the environment in which a user, Twin, agent, integration, or application is operating and adapts the available context, channels, capabilities, integrations and marketplace surface accordingly.
Host
├── Identity
├── Tenant
├── User
├── Session
├── Active Work
├── Context
├── Channels
├── Capabilities
├── Integrations
├── Plugins
├── MCP
└── Policy
Host-aware flow
Host Detected
→ Authenticate
→ Resolve Tenant / User / Twin
→ Discover Host Capabilities
→ Discover Connected Integrations
→ Discover Plugins / MCP
→ Apply Policy / Authority
→ Build Host Capability Manifest
→ Project Work
Host examples
- SpineWorkspace Web
- SpineWorkspace Mobile
- Slack
- Teams
- Browser / application host
- AI host
- external agent host
- MCP host
Critical boundaries
Host capability ≠ user authority
Host presence ≠ permission
Plugin installed ≠ authorized
MCP available ≠ mutation authority
Persistent Twin
The user's Twin remains the same logical Twin across hosts.
USER
↓
TWIN
┌─────┼─────┐
↓ ↓ ↓
Web Slack Mobile
The host changes interaction and available capabilities, not ownership of the user relationship or canonical business context.
Canonical principle
The Twin is persistent; the host is contextual.