HOW DATA MOVES — click anything to open it in the registry
INBOUND → PURE
32 tables · RLS
+ the lanes (Claude sessions)
PURE → OUTBOUND
Internal rails (Lane Mail, board, QA evidence) live inside the core. MCP servers are meta — they grant the lanes reach into everything listed.
EVERY INTEGRATION — toggle OFF and every lane honors it at next bootstrap (live pure_integrations table)
HOW TO REACH OUTSIDE SERVICES — the clickable field guide
The live database (Supabase)
The product's spine. Pages talk to it with the anon key + RLS (pure-db.js); lanes run SQL through Composio (SUPABASE_BETA_RUN_SQL_QUERY, ref mbnakfrkfwxinhxlisyq). You never touch this directly — ask any lane, or use the Command Center tabs (Memory · Dictionary · Releases all write here).
Composio apps — the big toolbox (15 services)
One connector layer holding live credentials for: Follow Up Boss · GitHub · GTmetrix · UptimeRobot · Google Maps/Analytics/Ads · Zoho · Zoom · Canva · Figma · Matterport · Cursor · API Ninjas · Supabase. Lanes discover tools with COMPOSIO_SEARCH_TOOLS, then call them. To use one: just ask in chat — "pull my FUB leads", "start a GTmetrix test". The wired-vs-available state is the Registry tab.
Zapier MCP — 7,000+ more apps
Anything Composio doesn't hold, Zapier usually does (it's how Netlify deploy + StreetText arrived). A lane enables the action; if it needs your login you get a one-click auth link in chat (exactly like the Netlify one you completed). To add a service: name it in chat.
Netlify — the live site
acquisto.biz. Auth CONFIRMED. Today: publish = download batch + drag to Netlify drop. After the repo link (B-T70): Releases ▸ publish in the Command Center triggers a real deploy. Sites on the account: acquisto, loquacious-boba-1e3952.
GitHub — history + backup
Private repo puremlstech/pure-deploy takes the state mirror at every close (boards, close-outs, memory docs, this schema). Diffable history; one-click revert source; future Netlify deploy source.
Follow Up Boss — the lead brain
30,550 events live. Lanes read/write via Composio (probe verified). The ingestion plan (LEADS-INGESTION-PLAN.md) wires sources → categories → action plans → saved searches. Your part: APR-5/6 approvals.
Monitors — GTmetrix + UptimeRobot
GTmetrix runs speed tests per deploy (scores log to qa_runs). UptimeRobot watches uptime — 22 ARE monitors exist; adding the PURE one needs the main API key (ND-6).
MCP servers — what they are
Named tool servers the lanes (and Cursor, future clients) connect to. Today: Zapier MCP (live) · GitHub MCP (live) · direct Supabase MCP (blocked by permissions — Composio is the path). Planned: the PURE MCP server (MCP-SERVER-DRAFT.md) — our own named, scoped, audited tools over board/memory/releases/connections; retires raw keys. Waiting on APR-2/3.
The lanes themselves
Claude sessions (A, B, n…) — your workforce. They bootstrap from pure_memory, claim from pure_board, message over Lane Mail, verify into qa_runs, and honor every toggle on this page. One window (Command Center ▸ Dispatch) drives them all.
OUTSTANDING DOCUMENTS — the permanent registry (live pure_needed_docs table)
Every gate that needs a file from a person lives HERE — nothing tracked in chat memory alone. "Mark received" when you've uploaded it in chat; the owning ticket unblocks on the next lane pass.