Skip to main content

SABLE Overview

SABLE is Indigo Trigger's agency operating spine: a web app, project memory, connector layer, and managed-agent workflow that turns meeting truth, project documents, time telemetry, and task systems into scoped answers and human-approved actions.

The current app proves four capabilities:

  • See the work: Home, Cockpit, Project Hub, Documents, and Accounts read a shared Supabase spine.
  • Ask the work: Ask SABLE answers from scoped project data and retrieved document excerpts.
  • Propose actions: Fathom and app surfaces create pending approval rows for Asana tasks, weekly updates, email drafts, scope flags, and SOW estimates.
  • Act safely: Approved Asana writes execute only through the asana-act Edge Function, only for admin/lead users, only when ASANA_ACT_WRITES_ENABLED=true.

Current Runtime​

What Is Real​

  • The Vercel app and Supabase API routes are real app surfaces.
  • Supabase Auth/JWT viewer resolution is used when Supabase is configured.
  • The Supabase schema, migrations, and Edge Functions are deployed against the project fvngkfrmienkltuwtoxa.
  • Toggl, Asana, Fathom, Drive, HubSpot, and Anthropic secrets live in Supabase Edge secrets.
  • The Fathom webhook secret is configured in Supabase as FATHOM_WEBHOOK_SECRET.

What Is Still Demo Or Gated​

  • Demo mode can fall back to bundled fictional JSON when Supabase is not configured.
  • Client-facing instances must set SABLE_MODE=production, which disables those fallback paths.
  • The legacy Vercel /api/fathom-webhook route is retained for the original CMA-memory demo only.
  • Asana writes are dark unless ASANA_ACT_WRITES_ENABLED=true.
  • Outcome pricing is Supabase-backed and includes mapped hours, category, budget variance, margin fields, and extracted SOW budget lines when present.
  • The client portal has a real membership/curation layer, but invite/reset and billing flows are not productized yet.

Source Of Truth​

Use these paths as the primary source of truth:

  • Web app: sable-agents-demo/web
  • Web API: sable-agents-demo/web/api
  • Supabase schema: sable-agents-demo/supabase/migrations
  • Edge Functions: sable-agents-demo/supabase/functions
  • Managed Agent configs: sable-agents-demo/agents
  • Connector setup: sable-agents-demo/CONNECTOR-SETUP.md
  • Act layer spec: sable-agents-demo/ACT-LAYER-SPEC.md