PURE · Poppy

my.poppy

Your own Poppy — learns you, needs less, does more

One Poppy for everyone, personal to each. PURE's software is the back; Poppy's intelligence is the front. The more you work together, the less you have to say — because she remembers, and she grows as PURE grows.

The model

Software at the back, Poppy at the front

my.poppy is one assistant standing on two layers that advance together: the system that knows the facts, and the intelligence that knows you.

You
Front · Poppy (the LLM)

Understands your words, your hats, your style. Reasons, plans, drafts, and proposes gated actions in plain language.

my.poppy · your layer

Per-user instance: identity × hats × org × workspace × poppy_memory. Your preferences, shortcuts, saved searches, voice — the part that makes Poppy yours.

Back · PURE (the software)

The system of record: 282 tables, the MCP fleet, crons, RLS. Live, true, gated. Poppy never guesses what PURE can simply know.

Division of labor: PURE holds the truth and does the work safely; Poppy holds the understanding and makes it effortless. Neither replaces the other — together they're my.poppy.
The payoff

Less context over time — try it

Click through the months. Watch the user type less while Poppy delivers more — because what you'd otherwise repeat now lives in your memory layer.

Context Poppy supplies from memory
10%
What you have to type
You provide nearly everything.
Customized for you

What makes it my.poppy

Remembers

Your facts

  • Saved searches & active clients
  • Preferences (format, tone, timing)
  • Shortcuts & recurring tasks
Adapts

Your hats

  • Agent vs ISA vs broker context
  • Org level + brokerage workspace
  • Only your data — RLS on auth.uid
Sounds like

Your voice

  • Drafts in your writing style
  • Your sign-offs & phrasing
  • Consistent across every channel
Stored per user in poppy_memory (RLS-locked). It accrues from what you do — corrections, approvals, repeated asks — and you can view, edit, or forget any of it in Command Center.
In lock-step, for everyone

As PURE grows, Poppy grows

Every new thing PURE can do becomes something Poppy can do — automatically, for all users at once. No per-feature retrofit.

PURE adds…
  • A new table / data type
  • A new MCP tool or action
  • A new cron / automation
  • A new connector or product
…Poppy gains
  • New knowledge to answer from
  • A new gated action to offer
  • New proactivity to surface
  • New reach across your world
The binding: Poppy reads PURE's live registries (pure_mcp_tools, schema, pure_surfaces, crons) rather than a hard-coded list — so the moment PURE ships, Poppy already understands it. One version line for both; every release stamped in poppy_lifecycle. PURE and Poppy never drift apart.