Pure · Poppy

Poppy Atlas

The living reference for Poppy — the LLM layer that runs PURE. Capability map, every document, and the full canon, read live from pure_memory so it is always in sync and never lost.

LIVE · mirrors canon in real time · 28 keys
Master Record Search Second Brain Coverage Home Digest Versions The Build Connections At the Edge System Map WordPressPure Verify For Chrome Runner Console Access Map my.poppy Pure Chat (live)
The shape of it all

Everything Poppy knows — one living map

A live spider of canon, the Pure Dictionary, every surface, every connector and the control plane. Click a node to open it — or dive into the full Second Brain.

Open the Second Brain See PURE Coverage
Capability map · v2

What Poppy can do — p1 p5

One consolidated B-POPPY-V2 batch, sequenced highest-leverage first. All guardrails intact — gated writes, approval card, per-role scope, audit, RLS. Rendered live from poppy.v2_capability_map.

Loading the capability map from canon…
Documentation library

Every Poppy document — live

The complete, deployed set. Each link is a live page on acquisto.biz; nothing lives only in a chat session.

Live canon

The source of truth, mirrored

Every poppy.* key in pure_memory, exactly as stored. Click any card to expand the full record. This list updates itself the moment canon changes — the never-lose-it guarantee.

Reading canon…
Connectors

Can Poppy connect to Composio? Yes.

Composio is the tool-router behind 500+ apps (GitHub, Gmail, Canva, Figma, Supabase, Follow Up Boss, Zoho, Matterport, Maps — already connected in this workspace). Here is how Poppy reaches them — gated and audited, the PURE way.

① PURE MCP Composio bridge recommended
Add a composio.execute tool to the live pure-mcp Edge Function. Poppy already speaks to the MCP fleet; this gives her every Composio app through one governed surface — gated by rank, approval-carded for writes, every call audited to audit_log. This is the path that lets us retire connector bloat and run everything through our own MCP.
② Mount Composio MCP in the runner
Composio offers hosted MCP endpoints. The t-poppy-runner (the automated Claude loop) adds Composio as an MCP connector and instantly gains 500+ tools. Fastest unlock for the runner specifically.
③ Direct from the chat function
The live chat function calls Composio's execute API for a few specific tools. Simplest, but least governed — use only as a stopgap.
How we make it happen — routed to Code (Edge Function + secret work):
  1. Store COMPOSIO_API_KEY as a Supabase secret on mbnakfrkfwxinhxlisyq.
  2. Add composio.execute {app, action, params, account} to pure-mcp; register it in pure_mcp_tools (disabled until tested).
  3. Proxy to Composio's tool-execute endpoint with the org's connected account; return result; audit every call.
  4. Gate: reads free; writes require rank ≥ 4 (admin/superadmin) + the approval card for anything irreversible.
  5. Register the 15 connected accounts in a poppy_connectors table so Poppy knows what is available per org; surface them here and in the Runner Console.