Unclassified

IntegrateWise & Spine Workspace — Canonical System Architecture Specification


1. Document Control & Executive Summary

PropertyCanonical Specification Value
System NameIntegrateWise Platform & Spine Workspace
Document Versionv3.0.0-Canonical
Architecture ClassificationModern Enterprise Service Bus (ESB) & Cognitive Operational Continuity Substrate
Company EntityIntegrateWise Inc. (integratewise.ai)
Product SurfaceSpine Workspace (spineworkspace.com / app.spineworkspace.com)
CategoryThe Self-Organizing Workspace
Platform EngineOperational Continuity Platform
Core Promise"Spine Workspace assembles the exact context, intelligence, and governed actions you need based on your role, your work, and what is happening right now."

2. Top-Level Taxonomy & Hierarchy

graph TD
    IW["IntegrateWise (Company & Platform Authority)"]
    SW["Spine Workspace (End-User Product)"]
    SOW["Self-Organizing Workspace (Category)"]
    DWE["Domain-Aware Workspace Experience (18 Projections)"]
    TGA["Twin + Governed Actions (Intelligence & Policy)"]
    AS["Adaptive Spine (Continuity Substrate)"]
    OCP["Operational Continuity Platform (Infrastructure & Mesh)"]

    IW --> SW
    SW --> SOW
    SOW --> DWE
    DWE --> TGA
    TGA --> AS
    AS --> OCP

2.1 The Naming Doctrine

  1. IntegrateWise: The company, the enterprise brand, and the platform authority.
  2. Spine Workspace: The commercial software product.
  3. Adaptive Spine: The governed continuity substrate connecting operational truth, knowledge, memory, and entity relationships.
  4. Twin: The contextual intelligence and cognitive co-worker runtime.
  5. Adaptive Workbench (Retired): Terminology consolidated into Spine Workspace and Domain Projections.

3. The 6-Layer Architectural Stack

┌──────────────────────────────────────────────────────────────────────────────────┐
│  LAYER 6: PRESENTATION & PROJECTION RUNTIME (Spine Workspace)                   │
│  • Self-Organizing Workspace Shell (OWUI)  • Multi-View Switcher (Table/Board)   │
│  • 18 Dynamic Domain Lenses (Sales/CS/RevOps/Eng)  • Interactive Live Canvas     │
└────────────────────────────────────────▲─────────────────────────────────────────┘
                                         │ Consumes Active Context Bundle
┌────────────────────────────────────────┴─────────────────────────────────────────┐
│  LAYER 5: CONTEXT COMPILER & PROJECTION ENGINE                                   │
│  • Materializes Active Context Bundle Contract (Single Context Law)              │
│  • Role × Domain × Industry × Entity × Intent Resolution Engine                  │
└────────────────────────────────────────▲─────────────────────────────────────────┘
                                         │ Assembles from Spine
┌────────────────────────────────────────┴─────────────────────────────────────────┐
│  LAYER 4: COGNITIVE INTELLIGENCE & TWIN RUNTIME                                  │
│  • Contextual Twin Copilot   • OODA Reasoning Loop  • Signal Sweep & Synthesis   │
│  • Proactive Proposal Generator (HITL-gated action drafts)                       │
└────────────────────────────────────────▲─────────────────────────────────────────┘
                                         │ Reads Context & Dispatches Proposals
┌────────────────────────────────────────┴─────────────────────────────────────────┐
│  LAYER 3: GOVERNED CAPABILITY FABRIC & POLICY ENGINE                             │
│  • Capability Resolver & Router  • 3-Tier Risk Classifier (Read / Gated / Strict)│
│  • Human-in-the-Loop (HITL) Gate • Action Lineage & Provider Reconciler          │
└────────────────────────────────────────▲─────────────────────────────────────────┘
                                         │ Reconciles & Mutates
┌────────────────────────────────────────┴─────────────────────────────────────────┐
│  LAYER 2: THE ADAPTIVE SPINE (Governed Continuity Substrate)                    │
│  ├── 1. Operational Truth (Entities, Relationships, States, Timeline Events)     │
│  ├── 2. Knowledge & Evidence (Docs, Chunks, Provenance, Retrieval References)    │
│  ├── 3. Memory & Continuity (Decisions, Commitments, Handoffs, Org Memory)       │
│  └── 4. Derived Context (Compiled Bundles & Temporal Signals)                    │
└────────────────────────────────────────▲─────────────────────────────────────────┘
                                         │ Ingests & Normalizes
┌────────────────────────────────────────┴─────────────────────────────────────────┐
│  LAYER 1: INTEGRATION MESH, GATEWAY & ONEAUTH INGRESS                            │
│  • OneAuth SSO / Session Broker (Zero client credential exposure)                │
│  • Bi-directional Connectors (Salesforce, HubSpot, Jira, Zendesk, Stripe, Slack)│
│  • Webhook Ingress, Event Mesh & Telemetry Pipeline                              │
└──────────────────────────────────────────────────────────────────────────────────┘

4. The 12-Step Closed Continuity Execution Loop

Every interaction, webhook event, or Twin proposal executes through the deterministic 12-Step Closed Loop:

flowchart TD
    subgraph INGESTION["1. INGESTION & NORMALIZATION"]
        S1["1. Observe (Webhooks, Telemetry, User Inputs)"] --> S2["2. Normalize (Canonical Mapping)"]
        S2 --> S3["3. Resolve (Entity Graph & Identity Linking)"]
        S3 --> S4["4. Persist (Authoritative Adaptive Spine Write)"]
    end

    subgraph PROJECTION["2. CONTEXT & PROJECTION"]
        S4 --> S5["5. Compile Context (Active Context Bundle Materialization)"]
        S5 --> S6["6. Project (Role × Domain Workspace Lens)"]
    end

    subgraph REASONING["3. COGNITIVE SYNTHESIS"]
        S6 --> S7["7. Reason (Twin OODA & Signal Sweep)"]
        S7 --> S8["8. Propose (Structured Action Proposal Generation)"]
    end

    subgraph GOVERNANCE["4. GOVERNANCE & RECONCILIATION"]
        S8 --> S9["9. Govern (Policy Engine & HITL Risk Gates)"]
        S9 --> S10["10. Execute (Server-side Capability Runtime Mutation)"]
        S10 --> S11["11. Reconcile (Provider Confirmation & Receipt Verification)"]
        S11 --> S12["12. Continue (Durable Organizational Memory Update)"]
    end

    S12 -.-> S5

5. The Single Context Law & Data Contract

[!IMPORTANT]
The Single Context Law: The user interface (Views, Table, Canvas), the AI intelligence (Twin, Background Reasoner), and the tool execution fabric MUST consume the identical ActiveContextBundle. AI is never allowed to hallucinate from ungrounded prompt memory.

export interface ActiveContextBundle {
  tenantId: string;
  projectionId: string;
  domain: OperationalDomain;
  user: {
    userId: string;
    role: string;
    department: string;
    capabilities: string[];
  };
  entity: {
    id: string;
    type: string;
    displayName: string;
    primarySource: string;
    externalIds: Record<string, string>;
    lastReconciledAt: string;
    freshnessScore: number;
  };
  signals: Array<{
    id: string;
    severity: "critical" | "warning" | "info" | "positive";
    source: string;
    title: string;
    description: string;
    detectedAt: string;
  }>;
  evidence: Array<{
    id: string;
    type: "contract" | "ticket" | "call_transcript" | "invoice";
    provenanceUrl: string;
    summary: string;
  }>;
  governanceGates: {
    maxExecutionRisk: "low" | "medium" | "high";
    requiresHitl: boolean;
    policyRulesEnforced: string[];
  };
}

6. Multi-Domain Projections (18 Operational Domains)

Spine Workspace resolves the work surface via a multi-dimensional matrix:
$$\text{Role} \times \text{Runtime Domain} \times \text{Industry} \times \text{Entity} \times \text{Intent} \longrightarrow \text{Compiled Projection}$$

DomainCanonical IdentifierCore EntitiesPrimary Sources
SalessalesOpportunities, Accounts, ContactsSalesforce, HubSpot
Account Successcustomer-successAccounts, Health, MilestonesGainsight, Zendesk
Technical Operationstechnical-account-successIncidents, Clusters, SLAsDatadog, PagerDuty, Jira
RevOpsrevopsPipelines, Quotas, ConversionSalesforce, HubSpot, Stripe
FinancefinanceInvoices, Contracts, LedgersStripe, QuickBooks, NetSuite
Business OpsbusinessopsOKRs, KPIs, ResourcesGoogle Sheets, Notion
MarketingmarketingCampaigns, Leads, AttributionMarketo, Google Ads
Content OpscontentEditorial, Briefs, AssetsNotion, Figma
CampaignscampaignsWorkflows, AudiencesHubSpot, Customer.io
ProductproductRoadmaps, Features, SpecsJira, Linear, Productboard
EngineeringengineeringPull Requests, Issues, ReposGitHub, GitLab, Jira
SupportsupportTickets, Escalations, CSATZendesk, Intercom
Human Resourceshuman-resourcesCandidates, Offers, HeadcountGreenhouse, Workday
LegallegalContracts, NDAs, RedlinesIronclad, DocuSign
Founder Opsfounder-opsInvestor Updates, Runway, Cap TableCarta, Mercury
KnowledgeknowledgeDocumentation, Wiki, SOPsNotion, Confluence
Personal WorkpersonalTasks, Focus Time, InboxGoogle Calendar, Slack
ExecutivestrategyStrategic Bets, Board DecksGoogle Slides, Mixpanel

7. Governance, Security & Non-Repudiation (R1–R10)

flowchart TD
    Intent["User or AI Intent"] --> RiskClass{"Risk Evaluation"}

    RiskClass -- "Class 1: Read / Synthesize" --> AutoExec["Execute Automatically"]
    RiskClass -- "Class 2: Low-Impact Draft" --> PolicyCheck{"Policy Enforced?"}
    PolicyCheck -- Yes --> AutoDraft["Draft in Sandbox"]
    PolicyCheck -- No --> HITL["Human Approval Card"]

    RiskClass -- "Class 3: Consequential Mutation" --> HITL

    HITL --> UserConfirm{"User Approval"}
    UserConfirm -- Approved --> ExecRuntime["Server Capability Runtime"]
    UserConfirm -- Rejected --> Abort["Audit Log Rejection & Cancel"]

    AutoExec --> ExecRuntime
    AutoDraft --> ExecRuntime

    ExecRuntime --> Provider["External Provider (Salesforce / Stripe / Zendesk)"]
    Provider --> Receipt["Provider Receipt & Transaction ID"]
    Receipt --> Reconcile["Reconcile into Spine & Update Lineage"]

7.1 Core Governance Rules

  • R1 (Zero Browser Credentials): No third-party OAuth tokens or API keys ever touch the frontend bundle.
  • R2 (Single Context Law): The AI copilot and UI canvas share the identical ActiveContextBundle.
  • R3 (Closed Execution Loop): Actions are never marked complete until external provider confirmation is received.
  • R4 (Explicit Risk Classification): Read-only (1), Drafts (2), External Mutations (3).
  • R5 (Confidence Never Grants Authority): An AI confidence score of 99% does not bypass human-in-the-loop gates.
  • R6 (Immutable Action Lineage): Records user ID, timestamp, intent, prompt, policy version, and provider response receipt.

8. Network Topology & Ingress Architecture

INTERNET & CLIENT INGRESS
│
├── https://integratewise.ai                    → Platform brand & category education
│   ├── /platform                               → The 12-Step Continuity Loop & Adaptive Spine
│   ├── /security                               → Trust Center (Zero Credential Exposure)
│   ├── /pricing                                → Enterprise platform tiers
│   └── /contact                                → Enterprise sales & security inquiries
│
├── https://spineworkspace.com                  → Commercial Product Homepage ("The Self-Organizing Workspace")
│   ├── /how-it-works                           → 3-Step Process: Connect → Assemble → Project
│   ├── /twin                                   → Contextual Intelligence with Governed Execution
│   ├── /governance                             → Risk Classification, Approvals & Action Lineage
│   └── /gallery                                → Artifact Gallery: Real QBRs, RCAs & Plans
│
├── https://app.spineworkspace.com              → Authenticated Workspace Runtime (The End-User Product)
├── https://platform.spineworkspace.com         → Customer Control Plane (Tenant Admin, RBAC, Connectors, Audit)
├── https://auth.spineworkspace.com             → Identity & SSO Ingress (OneAuth Session Gateway)
├── https://activation.spineworkspace.com       → Self-Service Provisioning & Onboarding Wizard
├── https://docs.integratewise.ai               → Technical API & developer documentation
├── https://api.integratewise.ai                → Edge API Gateway ingress
└── https://mcp.integratewise.ai                → Model Context Protocol tool endpoint

EDGE REWRITES (Vanity Solution Subdomains)
├── https://sales.spineworkspace.com            → /solutions/sales
├── https://cs.spineworkspace.com               → /solutions/customer-success
├── https://technical-account-success.spineworkspace.com → /solutions/technical-account-success
├── https://finance.spineworkspace.com          → /solutions/finance
├── https://revops.spineworkspace.com           → /solutions/revops
└── https://marketing.spineworkspace.com        → /solutions/marketing