> ## Documentation Index
> Fetch the complete documentation index at: https://docs.integratewise.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# INTEGRATEWISE USER JOURNEY

# IntegrateWise — Canonical User Journey & Activation Blueprint

**Status:** Authoritative User Lifecycle Specification\
**Source Baseline:** `integratewise-docs/user-journey.html`\
**Core Through-line:** *The user connects once, the Spine assembles their operational truth, and work begins with context already attached — nothing reconstructed by hand.*

***

## The 8 Journey Stages & 7 Activation Readiness Gates

```mermaid theme={null}
flowchart LR
    S1["1. Enter"] -->|Gate 1: Identity Ready| S2["2. Discover"]
    S2 -->|Gate 2: Workspace Ready| S3["3. Connect"]
    S3 -->|Gate 3: Connections Ready| S4["4. Load"]
    S4 -->|Gate 4: Data Ready| S5["5. Normalize"]
    S5 -->|Gate 5: Spine Ready| S6["6. Activate"]
    S6 -->|Gate 6: Workbench Ready| S7["7. Work"]
    S7 -->|Gate 7: Governance Ready| S8["8. Loop"]
```

***

### Stage 1 — Enter

* **User Action:** Authenticates once via OneAuth SSO or arrives via a delegated host session.
* **System Action:** Resolves Principal $\to$ Tenant $\to$ Workspace $\to$ Role $\to$ Entitlements $\to$ Policies.
* **Security Substrate:** Zero client credential copying. Host retains primary session authority.
* **Readiness Gate 1:** **Identity Ready** (Verified principal securely bound to workspace).

### Stage 2 — Discover

* **User Action:** Reviews pre-connected integrations and suggested domain workbenches.
* **System Action:** Discovery engine scans host environment for active SaaS instances (Salesforce, HubSpot, Zendesk, Stripe, Slack, GitHub).
* **Underlying Logic:** Capability Resolver computes the intersection of available connectors against tenant RBAC policies.
* **Readiness Gate 2:** **Workspace Ready** (Configured workspace with resolved capability envelope).

### Stage 3 — Connect

* **User Action:** Approves connector permissions (e.g. Read CRM, Sync Support, Query Billing).
* **System Action:** Generates isolated server-side connector instances in the Provider Fabric.
* **Security Substrate:** Credentials remain in secure server vault; only bounded capability projections are exposed to the client.
* **Readiness Gate 3:** **Connections Ready** (Provider channels active and authenticated).

### Stage 4 — Load

* **User Action:** Initiates zero-friction initial ingestion or real-time webhook subscription.
* **System Action:** Ingestion pipelines stream external accounts, opportunities, tickets, threads, and invoices into raw staging.
* **Telemetry:** Progress metrics computed in real-time (Entities loaded, records batched).
* **Readiness Gate 4:** **Data Ready** (Initial payload batch safely ingested).

### Stage 5 — Normalize

* **User Action:** Observes automated entity deduplication and relationship graph resolution.
* **System Action:** Loader passes data to Normalizer, executing canonical entity resolution, provenance tagging, and relationship synthesis.
* **Storage Invariant:** Writes structured state to Operational Spine (D1) and archives historical truth in Canonical Spine (Neon).
* **Readiness Gate 5:** **Spine Ready** (Cohesive multi-source business graph assembled).

### Stage 6 — Activate

* **User Action:** Selects primary domain role (e.g. Sales Director, CS Lead, RevOps Manager).
* **System Action:** Context Compiler projects the initial User Workbench with calculated Continuity Scores and real-time risk signals.
* **Output:** Instant, hydrated workspace ready in $< 300\text{ms}$.
* **Readiness Gate 6:** **Workbench Ready** (Active role projection mounted with live data).

### Stage 7 — Work

* **User Action:** Inspects accounts, prioritizes triage items, and invokes Twin on high-priority objects.
* **System Action:** Twin evaluates active object context path, surfaces converging risk signals, and drafts decision-ready proposals.
* **Interactive Mode:** 1-click execution for standard operations; side-by-side diff previews for complex workflows.
* **Readiness Gate 7:** **Governance Ready** (HITL approval policies active and verified).

### Stage 8 — Loop (Continuous Operation)

* **Operating Grammar:** **Understand $\to$ Propose $\to$ Govern $\to$ Execute $\to$ Reconcile $\to$ Learn**
* **System Action:** Closed-loop execution engine dispatches approved mutations to external SaaS providers, validates transaction receipts, and updates long-term organizational memory.
* **Continuous State:** Workspace stays continuously synchronized without manual context reconstruction.