PURE · Poppy

Poppy Access Map

Every way in — v1 live today, mapped through v2 and beyond

How people actually reach Poppy. This maps every entry point, shows the live surfaces as they are now, and charts the best-in-class access methods we add as Poppy evolves. Drop real screenshots into the frames so the live state is always visible here.

Open live Poppy — Pure Chat.ai
Live today · v1

v1 entry points — the live surfaces

These are the ways into Poppy right now on the live site. Each links to the real page; drop a current screenshot into its frame to keep the visual record honest as the UI changes.

Pure Chat.ai

pure-chat.html · acquisto.biz/pure-chat.html

The primary entry — a full-page conversational surface. History, vision (image drop), persona, ticket drafting; calls the chat Edge Function with window.claude local fallback.

v1 liveall users + operators
View live

Tech Panel Operator

pure-tech-admin.html

The admin-side entry — same brain, operator framing. Reaches Poppy alongside the per-user capability matrix (view/operator/tickets/lanemail/content/cron + guarded ops).

v1 livetechnicians / admins
View live

AI Roleplay Trainer

ai-roleplay.html

The practice entry — scripted real-estate scenarios to rehearse with Poppy. v4 folds this in as "practice with Poppy."

v1 liveagents
View live
Two more v1 paths, no dedicated UI: inline window.claude.complete embedded in admin surfaces (e.g. Admin Console), and the raw functions/v1/chat endpoint for programmatic callers. Both are real entry methods to document, even though they aren't pages.
The full list

Entry inventory — now next

Entry methodSurface / mechanismAudienceVersion
Pure Chat.aipure-chat.html full-page chatAll users + operatorsv1 live
Tech Panel Operatorpure-tech-admin.htmlTechnicians / adminsv1 live
AI Roleplay Trainerai-roleplay.htmlAgentsv1 live
Inline assistantwindow.claude.complete in pagesAdminsv1 live
Direct APIfunctions/v1/chat endpointProgrammaticv1 live
Best-in-class shellpure-chat-v2.html (tabs, slash, previews)All usersv2 staged
Omnipresent Search Barpure-topbar.js role menu — Poppy on every surfaceAll, per hatv3 planned
Command palette / slash/board /find /define… anywherePower usersv2
Mobile app / PWAInstallable home-screen app + pushAgents on the gov2+ proposed
VoiceSpeak-to-Poppy in/outPer subscriptionv2+
Proactive pushPoppy initiates: digests, critical-date & drift alertsAll, per hatv2+
Embedded widgetsContextual Poppy inside Transaction Hub, listings, CRMIn-contextv2+
Deep links / QRpure_short_urls prefilled PoppyShareablev2
Reply-to-PoppyAnswer an email/SMS routes into a Poppy threadClients / agentsv3+
Best-in-class · forward

Where access goes — v2 and beyond

v1 · now

Destination chat

  • You go to Poppy (a page)
  • Full-page + operator + trainer
  • One shared assistant for all

Poppy comes to you

  • Omnipresent top-bar on every surface
  • Slash / command palette + deep links
  • Per-user, hat-aware instance
  • Mobile/PWA + voice begin
v3+ · beyond

Redundant + proactive

  • Poppy initiates (push, alerts, digests)
  • Embedded in-context everywhere
  • Reply-to-Poppy over email/SMS
  • Pill nav retired search-bar entry
Versioned linking: as each entry method ships, it gets a row above with its live link and a screenshot frame here — so this map always shows the real, current set of doors into Poppy. Companions: v1 System of Record · Foundation · Control Center.

Screenshot frames persist your drops via a sidecar at the project root — that's why this map lives at the root while the deep-dive docs live in v2-poppy/.