Unclassified

SpineWorkspace Information Architecture

Status: CANONICAL · COMPREHENSIVE v2.0
Owner: IntegrateWise Platform
Scope: Complete Information Architecture including Domain Topology, Sidebar Structure, Work Projections, Platform Services, and Technical Implementation
Last Updated: 2026-08-21

1. Executive Summary — Who We Are

IntegrateWise is the persona-shaped operating system that sits between third-party AI assistants and human systems of record. We convert distribution traffic into tenant truth, then operate a Twin on that truth.

Core Doctrine:

Distribution is ingress — every AI assistant marketplace is a tenant-acquisition channel
Truth you own — the Spine is canonical; AI tools are projections
AI you rent — the LLM provider is plumbable (Cloudflare AI Gateway); no vendor lock
Approval in between — every write that crosses a system boundary passes through the Governance Engine
One capability, every surface — the same cap_id resolves identically across all interfaces
Continuity over asking — the Spine is the source of context; the Twin never re-asks
Persona barrier — tenant_spine_config.industry × department defines the visible universe
Hard gates are non-negotiable — Soft-sync defaulting, 5-minute first-data-load, promotion-queue human approval

2. Subdomain Topology

SpineWorkspace is one application with subdomain-based routing that resolves department context.

spineworkspace.com
│
├── www.spineworkspace.com             → Public marketing
├── auth.spineworkspace.com            → One Access (Authentication & Identity)
├── platform.spineworkspace.com        → Platform control plane
│
├── founder.spineworkspace.com         → Founder workspace
├── sales.spineworkspace.com           → Sales workspace
├── cs.spineworkspace.com              → Customer Success workspace
├── marketing.spineworkspace.com       → Marketing workspace
├── finance.spineworkspace.com         → Finance workspace
├── operations.spineworkspace.com      → Operations workspace
├── product.spineworkspace.com         → Product workspace
├── engineering.spineworkspace.com     → Engineering workspace
├── account-success.spineworkspace.com  → Account Success
├── technical-account-success.spineworkspace.com → Technical Account Success
├── business-intelligence.spineworkspace.com → Business Intelligence
├── campaigns.spineworkspace.com       → Campaigns workspace
├── knowledge-management.spineworkspace.com → Knowledge Management
├── revops.spineworkspace.com          → Revenue Operations
├── support.spineworkspace.com         → Support workspace
├── brandstore.spineworkspace.com      → Brand Store
├── book-of-records.spineworkspace.com → Book of Records
├── ops.spineworkspace.com             → Ops workspace
│
└── future projections...

Routing Contract

The subdomain resolves to a department identifier. Combined with the authenticated user's role and the tenant's industry, this selects the Work projections rendered in the sidebar and main content area.

Key Principle: Every department subdomain loads the same application shell. Only the Work section differs. www, auth, and platform are distinct surfaces with their own shells. Department subdomains share one shell.

Resolution Formula

subdomain → department
session   → role
tenant    → industry
policy    → workspace configuration

projection = f(role, department, industry, workspace_policy)

Each projection contains enough operational depth for a user to perform their complete job in the agentic era.

spineworkspace.com
│
├── www.spineworkspace.com             Public marketing
├── auth.spineworkspace.com            One Access (Descope)
├── platform.spineworkspace.com        Platform control plane
│
├── founder.spineworkspace.com         Founder workspace
├── sales.spineworkspace.com           Sales workspace
├── cs.spineworkspace.com              Customer Success workspace
├── marketing.spineworkspace.com       Marketing workspace
├── finance.spineworkspace.com         Finance workspace
├── operations.spineworkspace.com      Operations workspace
├── product.spineworkspace.com         Product workspace
├── engineering.spineworkspace.com     Engineering workspace
├── account-success.spineworkspace.com          Account Success
├── technical-account-success.spineworkspace.com Technical Account Success
├── business-intelligence.spineworkspace.com    Business Intelligence
├── campaigns.spineworkspace.com       Campaigns workspace
├── knowledge-management.spineworkspace.com     Knowledge Management
├── revops.spineworkspace.com          Revenue Operations
├── support.spineworkspace.com         Support workspace
├── brandstore.spineworkspace.com      Brand Store
├── book-of-records.spineworkspace.com Book of Records
├── ops.spineworkspace.com             Ops workspace
│
└── future projections...

Routing contract

The subdomain resolves to a department identifier. The department identifier,
combined with the authenticated user's role and the tenant's industry, selects
the Work projections rendered in the sidebar and main content area.

Every department subdomain loads the same application shell. Only the Work
section differs. www, auth, and platform are distinct surfaces with their
own shells.

3. Sidebar Structure

The sidebar is consistent across all department subdomains. It has three
top-level zones: Common, Work, and Platform. Common and Platform
are identical on every subdomain. Work changes per subdomain.

┌─────────────────────────────┐
│  COMMON                     │
│  ├── Home                   │
│  ├── My Work                │
│  ├── Inbox                  │
│  ├── Tasks                  │
│  ├── My Queue               │
│  ├── Approvals              │
│  ├── Notifications          │
│  ├── Recent Work            │
│  ├── Favorites              │
│  ├── Communications         │
│  │   ├── Activity Feed      │
│  │   ├── Email              │
│  │   ├── Calendar           │
│  │   ├── Meetings           │
│  │   ├── Chat               │
│  │   └── Calls              │
│  ├── Documents              │
│  │   └── Shared             │
│  ├── Personal               │
│  │   ├── Notes              │
│  │   ├── Knowledge Base     │
│  │   └── Brainstorming      │
│  └── Activity               │
├─────────────────────────────┤
│  WORK                       │
│  ├── View 1                 │  ← Department-specific
│  ├── View 2                 │     projections
│  ├── ...                    │
│  └── View N                 │
├─────────────────────────────┤
│  PLATFORM                   │
│  ├── Integration Manager    │
│  ├── Connector Marketplace  │
│  ├── Activation Hub         │
│  ├── Capability Manager     │
│  ├── MCP Pool               │
│  ├── AI Models              │
│  ├── Knowledge              │
│  ├── Memory & Continuity    │
│  ├── Automation             │
│  ├── Pipelines              │
│  ├── Governance             │
│  ├── Observability          │
│  └── Administration         │
│      ├── Organizations      │
│      ├── Users              │
│      ├── Roles              │
│      ├── Permissions        │
│      ├── Audit              │
│      ├── Billing            │
│      ├── Deployments        │
│      ├── API Keys           │
│      ├── Security           │
│      ├── Admin              │
│      └── Paywall            │
└─────────────────────────────┘

4. Common Sidebar Sections

Home

Personal operational dashboard. Cross-domain aggregation independent of
the current department projection.

Personal KPIs and priority ranking
Pending approvals
AI recommendations and quick actions
Workspace continuity entry
Personal Twin context
Cross-projection navigation
Recent activity

My Work

Personal execution surface.

Assigned work and delegated work
Waiting on others / waiting for me
Tasks, goals, deliverables, follow-ups
Approvals and SLA commitments
Calendar-linked work
Twin-assisted execution

Inbox

Unified operational inbox. Aggregated from email, chat, CRM, tickets,
comments, mentions, notifications, AI-generated follow-ups, connector events,
workflow events, and approval requests.

Priority scoring and deduplication
Threading and AI summaries
Suggested actions

Tasks

Universal task execution. Manual tasks, workflow tasks, agent-generated tasks,
connector-generated tasks, scheduled tasks, recurring tasks, approvals,
dependencies, SLA tracking, and context-aware execution.

My Queue

Dynamic execution queue generated from the priority engine, OODA, signals,
deadlines, dependencies, AI prioritization, role, current context, business
impact, and attention management.

Approvals

Human-in-the-loop governance. Publishing, budget, connector, AI, write-back,
customer, deployment, security, and policy approvals. Escalation workflows
with full audit trail.

Notifications

Workspace event stream from connectors, pipelines, agents, skills, workflows,
governance, security, platform, workspace, Twin, and human collaboration.
Intelligent grouping and prioritization.

Recent Work

Continuity surface. Recently viewed entities, edited records, conversations,
workflows, approvals, Twin sessions, canvas work, documents, and context.
Resume previous work.

Favorites

Pinned operational assets. Views, dashboards, accounts, campaigns, customers,
reports, skills, agents, workflows, documents, canvases, and pipelines.

Communications

Unified communication layer.

Section	Purpose
Activity Feed	Operational timeline combining CRM, emails, meetings, chats, deployments, customer interactions, agent activity, workflow execution, connector events, and platform events into one chronological Spine timeline.
Email	Multi-provider inbox with AI summaries, draft generation, smart replies, CRM linking, entity linking, Twin memory, knowledge retrieval, and workflow initiation.
Calendar	Multi-provider scheduling with AI scheduling, meeting preparation, agenda generation, follow-up generation, linked entities, and linked workflows.
Meetings	Meeting operating system: preparation, briefing, live assistance, recording, transcript, action extraction, decisions, follow-ups, memory promotion, and workflow creation.
Chat	Unified conversation across Slack, Teams, Discord, internal chat, MCP messaging, and AI conversations with context retrieval, entity linking, workspace memory, and suggested actions.
Calls	Voice communication with call preparation, live notes, transcript, CRM linking, entity extraction, tasks, decisions, follow-ups, and memory updates.

Documents

Collaborative document workspace across Google Docs, Office, Notion, Coda,
PDFs, and internal documents. Semantic indexing, context retrieval, version
awareness, AI understanding, and knowledge promotion.

Personal

Personal knowledge and thinking space.

Section	Purpose
Notes	Personal operational memory with quick capture, linked entities, AI organization, tags, knowledge promotion, Twin context, and search.
Knowledge Base	Workspace knowledge graph: canonical knowledge, policies, documentation, procedures, product knowledge, customer knowledge, organizational knowledge, semantic search, RAG context, and source traceability.
Brainstorming	Collaborative ideation: whiteboards, structured thinking, AI ideation, Twin collaboration, decision capture, research, concept evolution, and memory promotion.

Activity

Personal operational timeline. Work history, AI activity, decisions, context
switches, workflow participation, learning, memory evolution, and workspace
interactions.

5. Work Section

The Work section is the only section that changes per subdomain. It is built
from:

Spine projections
Views
Canvas
Tool capabilities
Twin execution through OODA invocations
Skills
Agents
Workflows
Pipelines
Backend/frontend mappings
Operational databases
Context gathering
Entity360
Continuity memory

Each projection contains enough operational depth for a user to perform
their complete job in the agentic era.

Work section components

Views               Spine-projected operational views for the domain
Canvas              Spatial working surface for the domain
Skills              Domain-specific skills available to the user
Agents              Domain-specific agents (Twin, Triage, Co-worker)
Workflows           Domain-specific automated workflows
Twin                Domain-aware Twin context and execution
Operational Objects Domain entities projected from the Spine

Routing contract

Work projections are resolved by:

subdomain → department
session   → role
tenant    → industry
policy    → workspace configuration

projection = f(role, department, industry, workspace_policy)

The views rendered in the Work section are sufficient for any person working
in that domain. They are not a subset of a larger tool — they are the
complete operational surface for that department.

6. Platform Section

Shared platform capability layer provided by apps/platform. Every subdomain
renders the same Platform section. Administration is permission-aware and
exposes only the capabilities the current user is authorized to manage.

Integration Manager

Connector lifecycle: OAuth, credentials, sync, health, scopes, events,
policies, write-back, and diagnostics.

Connector Marketplace

Connector discovery: providers, templates, MCP connectors, native connectors,
community connectors, installation, configuration, ratings, and documentation.

Activation Hub

Workspace onboarding: identity, workspace, connectors, capabilities, initial
sync, Spine hydration, memory bootstrap, verification, and readiness.

Capability Manager

Capability fabric mapping skills, tools, connectors, APIs, agents, workflows,
permissions, and policies.

MCP Pool

Unified MCP runtime: tool registry, MCP discovery, invocation, authentication,
sessions, context, security, and monitoring.

AI Models

Model management: providers, routing, policies, costs, benchmarks, prompt
versions, safety, evaluation, and observability.

Knowledge

Knowledge infrastructure: indexing, semantic search, embeddings, documents,
citations, knowledge graph, retrieval, and context assembly.

Memory & Continuity

Continuity infrastructure: personal memory, workspace memory, organizational
memory, Twin memory, timeline, decisions, context, recall, and promotion.

Automation

Automation runtime: triggers, schedules, events, conditions, retries,
dead-letter queues, idempotency, human approvals, and monitoring.

Pipelines

Operational data pipelines: load, normalize, map, validate, enrich,
synchronize, index, publish, and observe.

Governance

Operational governance: policies, approvals, compliance, risk, audit, change
control, AI governance, and connector governance.

Observability

Platform intelligence: logs, metrics, traces, health, costs, AI usage,
connector status, pipeline status, workflow execution, and user experience.

Administration

Workspace administration layer. Permission-aware — exposes only the
administrative capabilities the current user is authorized to manage.

Section	Scope
Organizations	Workspace and tenant management
Users	Members, invitations, sessions
Roles	Role definitions and assignments
Permissions	Resource-level access control
Audit	Immutable audit trail and compliance records
Billing	Plans, usage, invoices, payment methods
Deployments	Release management and deployment history
API Keys	API key lifecycle and scoping
Security	Security policies, SSO, MFA, threat detection
Admin	Platform-level administration
Paywall	Feature access control and subscription enforcement

7. Architectural Principles

SpineWorkspace is one application. Subdomain routing resolves department
context — it does not deploy separate applications.
The Common sidebar and Platform section are identical across all department
subdomains.
Intelligence (Skills, Agents, Workflows, Twin, OODA) is embedded inside
each domain projection, not isolated in a separate product area.
The Work section renders projections sufficient for a complete job in the
agentic era — not a subset of a larger tool.
The sidebar has three zones: Common (universal operations), Work
(department-specific projections), and Platform (shared infrastructure).
www, auth, and platform are distinct surfaces with their own shells.
Department subdomains share one shell.
Administration is permission-aware. The sidebar renders only the sections
the authenticated user is authorized to access.

8. Invariants

Every department subdomain loads the same application shell.
The Work section is the only section that differs per subdomain.
Work projections are resolved by Role × Department × Industry × Policy.
Platform, auth, connectors, marketplace, MCP, and integration manager are
shared across all subdomains.
The sidebar structure is frozen. New sections require architecture review.