Documentation Portal

Connectors share one explicit session-routing model.

The bridge keeps connector-specific behavior behind connector runtimes and execution adapters while the platform itself stays explicit about workspace, connector type, and target session identity.

Documentation map

The docs portal stays in the same application as the product shell so setup, deployment, connector, and developer guidance can evolve with the codebase.

In-repo docs7 foundation routes5 developer routesCurrent: Connectors

Foundation docs

  • OverviewRoute

    Start with the current architecture, product surfaces, and the stable documentation sections.

  • Getting StartedRoute

    Install the workspace, configure local env files, and run the first verification flow.

  • DeploymentRoute

    Use the managed bridge deployment order, health checks, migrations, and workspace bootstrap flow.

  • ConnectorsOpen

    Understand the Figma reference connector, Satellite runtime, and explicit session routing model.

  • SecurityRoute

    Review auth lanes, workspace isolation, policy controls, rate limiting, and audit semantics.

  • API ReferenceRoute

    Browse the stable HTTP route groups, shared envelopes, auth lanes, and machine-readable errors.

  • TroubleshootingRoute

    Use the current operational failure patterns for readiness, auth, session liveness, policy, and MCP issues.

Developer docs

  • DevelopersRoute

    Developer-facing entry point for HTTP, MCP, connector, and shared-contract guidance.

  • Developer QuickstartRoute

    Bring up the bridge, connect one runtime, and make the first explicit authenticated calls.

  • HTTP GuideRoute

    Use the bridge HTTP transport with the correct auth lane, shared envelopes, and explicit targetSessionId routing.

  • MCP GuideRoute

    Use the Streamable HTTP MCP endpoint, LIST_CAPABILITIES, and the same connector-neutral tool catalog.

  • Connector ModelRoute

    Understand connector definitions, capability metadata, data scopes, and high-risk policy presets.

Figma reference connector

Figma remains the proving connector for the first external path, but it no longer owns the platform vocabulary.

Reference connectorembedded_pluginExplicit sessionId
  • Import apps/figma-plugin/manifest.json as a local plugin and keep the plugin window open during smoke.
  • Use the public bridge URL, one explicit workspace id, one explicit session id, and either runtime_token or supabase_jwt.
  • Confirm the runtime through GET /api/v1/sessions/:sessionId before treating it as a live smoke target.

Satellite runtime

Satellite is the outbound runtime boundary for desktop-oriented and restricted-network connector work.

Desktop runtime pathsatellite_agentConnector-neutral discovery

The current Phase 4 slice already proves Satellite command execution, file changesets, package inspection, Git inspection, and the first bounded generic_host adapter-host workflow through the same bridge path.

Routing model

Every execution path remains explicit about workspace scope and target session identity.

The bridge never routes to any active session. Callers must target one specific sessionId.

Session discovery uses one shared read-state vocabulary: online, stale, and offline.

Connector-specific metadata stays inside the dedicated connectorMetadata boundary instead of leaking into platform-level discovery fields.