Documentation Portal

Documentation grounded in the current bridge architecture.

This portal turns the existing README, deployment guides, connector onboarding, and shared contracts into route-backed product documentation without inventing a separate docs stack.

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: Overview

Foundation docs

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

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

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

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

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

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

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

Developer docs

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

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

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

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

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

Foundation sections

These routes document the stable concepts already reflected in the current repository and product shell.

Getting Started

Ready

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

Open section

Deployment

Ready

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

Open section

Connectors

Ready

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

Open section

Security

Ready

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

Open section

API Reference

Ready

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

Open section

Troubleshooting

Ready

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

Open section

Developer entry points

The first developer slice stays inside the docs portal and reuses the same route shell.

Developers

Developer

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

Open section

Developer Quickstart

Developer

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

Open section

HTTP Guide

Developer

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

Open section

MCP Guide

Developer

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

Open section

Connector Model

Developer

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

Open section

Source of truth

These docs are derived from the repository state that is already treated as canonical for setup, deployment, onboarding, and secure runtime behavior.

README-backedDeployment guide alignedConnector onboarding aligned

`README.md` remains the primary source for workspace setup, secure-shell env contracts, runtime usage, and public route expectations.

`docs/ai/bridge-external-deployment-guide.md` stays the deployment-facing source for managed bridge rollout, health checks, migrations, and first workspace bootstrap.

`docs/ai/figma-external-plugin-onboarding.md` stays the connector-facing source for explicit Figma session connection and first external smoke verification.