Unclassified

03 — User Journeys and Activation

Status: Canonical journey; implementation and production evidence vary

Primary onboarding journey

Clerk sign-in
→ active organisation selected
→ Gateway verifies user and membership
→ account and tenant resolved
→ Integration Manager opens
→ connector selected
→ Nango provider authorisation
→ provider workspace resolved
→ server-owned connector binding created
→ schema compatibility validated
→ initial load and normalisation
→ Pipeline promotion into Spine
→ Projection Engine composes Workbench
→ Twin becomes contextually available

The browser cannot supply authoritative user, account, tenant, Spine, provider
workspace, or schema identifiers.

Connector activation journey

The visible stages are:

  1. Authentication
  2. Provider workspace resolution
  3. Spine binding
  4. Schema validation
  5. Initial sync
  6. Operational readiness

If any mandatory evidence is missing or inconsistent, the binding is stale.
The user sees the failed stage and a precise repair or reconnect action.

Returning user

Gateway revalidates the Clerk session and active membership, resolves the tenant,
loads a permission-scoped SharedWorkbench, and exposes only operational
connectors and capabilities. A projection cache miss may show an explicit
partial-evidence state; it may not silently show demo data.

Marketplace or MCP entry

AI-host and MCP distribution are additional Bridge entry points, not separate
products. Each client must use the public OAuth-protected nineteen-tool MCP and
resolve to the same IntegrateWise user, account, and tenant contracts.

Host reuse of other connected tools is Unverified until a host proves one of
these modes:

  • HOST_DELEGATED: the host explicitly delegates a bounded capability.
  • HOST_ORCHESTRATED: the host invokes both systems and returns only permitted
    results.
  • DIRECT_FALLBACK: the user authorises the provider directly through
    IntegrateWise.

IntegrateWise never assumes access to another app's private credentials.

Activation acceptance

Activation succeeds only when the user can see the correct tenant, an
operational connection, its schema and sync evidence, the resulting Workbench
projection, and the permitted Four Button actions.