Poppy 4.0 — At the Edge · meet you where you are

The concept

Add Poppy as a destination

You were looking at "Add a destination" — a list of places to send a design. That's exactly the model: Poppy should be a destination too. Not a page you open — a target you send to, from wherever you already are. Highlight a paragraph and "Send to Poppy." Text a photo to a number. Share a listing from your phone. Forward an email. Poppy receives it, files the ticket, routes it, and replies on the same channel. Meet you where you're at.

Here's the whole surface area — every place you are, the channel that reaches Poppy, and what she does with it:

Where you are	How you reach Poppy	What Poppy does
Any web page	Point & Ask · right‑click · omnibox `poppy` live	Answers cited from PURE, or files a ticket about the element
Any web page	Save‑to‑Pure clipper next	Clips the page/selection ticket, lead, or doc in the right deal
Your phone	Text a number (SMS) 4.0	"Text a ticket" — photo/note ticket; Poppy texts back status
Your phone	Share sheet "Send to Poppy" (PWA) 4.0	Share a listing/photo/link from any app routed into PURE
Email	poppy@acquisto.biz 4.0	Forward anything AI intake ticket/deal, reply by email
Desktop browser	Side panel (Chrome) next	Poppy docked beside any tab — ask, clip, quick‑add
In PURE	Reply‑to‑Poppy back‑channel 3.0+	Reply on any Poppy notification continues the thread

On the browser

The Chrome extension, built out in coordination

Poppy already ships as a Manifest‑V3 extension (Point & Ask, omnibox, right‑click — live). 4.0 turns it into the full edge client: the clipper is the "Send to Poppy" destination, the side panel is Poppy docked everywhere.

Save‑to‑Pure clipper

The browser version of "Send to Poppy" — the destination itself.

Clip a full page, selection, or image
Pick the target: ticket · lead · deal doc · saved search
Poppy classifies + files it (same AI intake as pure-intake)

Side panel

Poppy docked beside any tab — no context switch.

Ask / search PURE without leaving the page
Quick‑add to calendar, tasks, deals
Carries your hat sees only what you should

PureGuard highlighter

Dictionary canon enforced anywhere you type.

Flags retired terms in any web field
One‑click swap to canon + dictionary link

Watcher + quick‑add

Saved‑search badge + calendar quick‑add from the toolbar.

New listing matches toolbar badge
Select a date on any page add to PURE Calendar

On the phone

Native texting, share sheet, and the field

The phone is where agents and vendors actually are. 4.0 makes Poppy reachable by the two things every phone does best — text and share — plus the offline field‑capture you already have.

Text a ticket (SMS)

A real PURE number. Text a photo + a line; Poppy files it and texts back the ticket link.

📱 Text + photoTwilio pure‑commsPoppy AI intakeTicket + reply

Share sheet Poppy

Install PURE as a PWA and Poppy appears in the OS share sheet as a destination.

Share a listing, photo, or link from any app
share_target in the manifest receives it
Routed into the right deal / record

Field App + MFA

The mobile field client you have — extended.

Offline capture + GPS + photo (live)
MFA / passkey approve from the phone
NFC lockbox open on showings

Reply on the channel

Poppy answers where you reached her — text replies to text, email to email — so it's a conversation, not a form.

SMS thread keyed to the ticket
Email reply‑to threads back to Poppy

Never lose a thing

Poppy's Daily Journal

You asked for this before and we started it — every session self‑captures to pure_session_log at start, and close‑outs archive to pure_sessions. 4.0 unifies them into one living diary: every session, every sweep, auto‑stored at the end of the nightly sweep, always referenceable — and Poppy reads it as memory so context is never lost.

Start · log_session() Work · edits + commits logged Nightly sweep writes the day's entry Journal surface + Poppy recall

What 4.0 adds

End‑of‑sweep auto‑store — the nightly sweep writes a journal entry per lane (no human capture)
One diary surface — poppy-journal.html: searchable day‑by‑day, links to every commit + surface
Poppy reads it — the journal becomes a knowledge source; "what did we ship Tuesday?" answers from it
Session URL capture — paste a Claude session URL tied to that day so nothing's orphaned

Live now — recent captures

Read live from list_sessions() — the foundation 4.0 builds on:

Loading the journal…

For Shana & ARE

Design Pickle Pure Creative, on autopilot

Shana has a deep Design Pickle library for Acquisto Real Estate. 4.0 pulls it in and automates the asset creation each time — so listings, social, and print are generated without anyone filing a request — and sets the path to retire the third‑party spend into Pure Creative.

Pull in the library

Index ARE's existing Design Pickle assets into pure_marketing_assets (ARE‑scoped)
Direct Poppy / Pure MCP Design Pickle link (or via Composio) — Omkar wires the key into Vault
Canva + Figma already feed Pure Creative — same pipe

Automate every time

New listing Poppy auto‑drafts the asset set (flyer, social, just‑listed)
Brand‑locked to ARE; Shana previews + approves
Recurring weekly marketing already ticketed (t‑shana‑weekly‑marketing)
Cron keeps the set fresh; Pure Creative replaces the Design Pickle subscription

What it needs

The plugs (ties to the punch list)

Twilio number

The PURE text line for "text a ticket" + SMS replies.

Omkar · CONN‑TWILIO

poppy@ inbox

Forward‑to address webhook intake (acquisto.biz mail is a clean slate).

Omkar · t‑poppy‑inbox

Design Pickle key

API/login Vault for the direct pull + automation.

Omkar · new CONN

Sweep write

Nightly sweep also writes the journal entry (extends the cron just handed over).

Code · sweep cron

PWA share_target

Manifest entry so Poppy shows in the phone share sheet.

Code · PWA

Extension publish

List Save‑to‑Pure + side panel in the Chrome Web Store.

Design · extension

Poppy 4.0 — At the Edge · proposed scope · graded live by Poppy