Skip to main content

Architecture Overview

SABLE is split across four runtime layers:

  1. Browser app.
  2. Vercel API routes.
  3. Supabase spine and Edge Functions.
  4. Claude Managed Agents demo path.

Browser​

The app is deliberately simple: static HTML files, shared CSS, and shared shell scripts. The product views live in sable-agents-demo/web.

Vercel API​

Vercel routes handle browser-facing API concerns:

  • Viewer/auth resolution.
  • Scoping.
  • Chat.
  • Approvals API.
  • Outcome API.
  • Document signed URLs.
  • Legacy CMA demo routes.

Supabase​

Supabase owns durable state:

  • Project spine.
  • Documents and embeddings.
  • Approval queue.
  • Audit.
  • Connector sync state.

Edge Functions​

Supabase Edge Functions own connector work and external write gates because the relevant secrets live in Supabase Edge secrets.

Claude Managed Agents​

Managed Agents remain part of the demo and future-agent architecture. The older memory-store path proves autonomous board generation and delivery, while the newer production direction moves connector truth into Supabase.