PURE · Poppy

Poppy — Architecture & BI

What she's built on · where she lives · who owns her · how she's used

The architecture beneath Poppy across versions, where it physically lives and in what time zone, who owns it, a visual map of the brain's wiring, and live business-intelligence on real usage.

Location · ownership · time

Where Poppy lives

Data & brain host

Supabase

Project mbnakfrkfwxinhxlisyq · region us-east-2 · Postgres 17.6 + Edge Functions.

Web host

Netlify

acquisto.biz (app) + app.acquisto.biz (static) · source GitHub puremlstech/puremls.

Time zone

Central (CT)

Stored in UTC (timestamptz); operated & displayed in America/Chicago — CT is canon for all stamps.

Owner

Mike & Shana Acquisto

Brand: Acquisto Real Estate. Platform owner: PURE MLS Technologies. DB owner mike@acquistorealestate.com.

Governance owners of Poppy specifically (the poppy_technician roster): Mike › Dave › Shattique › v2 R&D. Manage in the Control Center.
Architecture by version

Current & future architecture

The stack she's built on, tracked as it evolves. v2/v3 extend the same base — they don't replace it.

Layerv1 — nowv2 — nextv3+ — future
ModelClaude Sonnet (single, env-set)Best-model-per-task router + meteringSelf-tuning quality/cost loop
Brainchat Edge Function v26chat v2: per-user instance, tools[]/citations contractMulti-step runner over pure_mcp_jobs
Tools8 of 87 (6 read, 2 gated)Full fleet, hat-scopedConnectors + embeddings retrieval
MemoryClient-side historypoppy_memory per-user/dealLong-term semantic memory
AccessPages (chat/operator/trainer)Omnipresent top-bar + mobile/PWA + voiceProactive + embedded everywhere
IdentitySupabase Auth (passkey-first)Per-instance gating via pure_permissionsOrg-federated SSO
Visual linkings

The brain, wired

How a message flows through Poppy — surface to brain to model and live data, and back, with everything gated and logged.

Entry
Useragent · broker · client
SurfacePure Chat.ai · Operator · Trainer
Brain
chat fn v26system prompt · tool loop ≤5 · gate writes
Intelligence
Claude APIreasoning · vision
web_searchlive web · 5/turn
Live data & record
pure-mcp RPCslistings · dict · board · deals · memory · crons
Postgres 17.6282 tables · RLS on hats
audit_log + chainevery write, tamper-evident

Reads flow straight through; writes pause at the brain for an approval card before touching data — then land in audit_log.

Business intelligence — live

Usage levels

Real counts from the platform on 2026-06-27. As Poppy's adoption grows these climb — v2 adds per-user usage + spend metering.

367
board tickets
262
audited actions
126
QA / verifier runs
71
job runs
34
org members (users)

Most-used tools (call counts)

board.list
42
board.dispatch
27
qa.log
23
lane.mail
21
board.update
19
memory.get
11
email.send
6
lead.create
1
Reports · users · access

BI functions, users & access

Reports & BI surfaces (live)

Where the numbers are read

  • Model Routing & Spend.html — model mix + estimated cost
  • Pure Coverage.html — catalog/nav drift + 404s
  • cron-efficiency-snapshot + pure-improve-digest — daily ops
  • pure-brand-digest — brand-health findings
  • qa_runs · audit_log · pure_job_runs — raw BI tables
Users & how they reach Poppy

34 members across the org spine

  • Roles: agent · designated_broker · isa · TC · client · association_admin · mls_admin · superadmin · vendor
  • Access via the surfaces in the Access Map — chat, operator, trainer (v1)
  • v2: each user gets a hat-scoped instance from pure_permissions + pure_subscriptions
  • Every access + action audited per principal
Tracked in canon poppy.architecture. Companions: v1 SoR · Foundation · Data Flow · Persona · Control Center · Access Map.