Placement — part of PURE, owned at the Platform tier
Poppy is not a sixth org level stacked on top of PURE. The org spine is a tenancy hierarchy. Poppy is a cross-cutting AI service layer the Platform owns and operates — it spans every level and is gated per hat.
One Poppy spans every level — owned at the Platform tier, gated per hat as it reaches down to MLS, Association, Brokerage and Client.
The recommendation
Poppy = a Platform-owned service, not a level above PURE. She is part of PURE, governed at the Platform tier, operating across MLS Client by hat-scoped permission.
Same Supabase — yes. One database keeps identity (auth.uid + hats), dictionary, memory, board and the audit trail unified. A separate DB would fracture all of that.
Your "one level higher" instinct maps to governance authority over the AI — expressed correctly as a dedicated poppy_* namespace inside the same project, not a new tenancy level.
poppy_lifecycle
Dated record of every version milestone — v1 start v2 cutover.
poppy_edit_log
Append-only log of every edit to Poppy, with undo pointers for rollback.
poppy_technician
Who may edit Poppy + their capabilities, gated by offline code on destructive ops.
Lifecycle — when each version became real
Every milestone is timestamped (CT) in poppy_lifecycle. The v2 cutover row stays pending until it happens — then a technician stamps the exact date/time + commit.
Poppy brain went live historical
The chat Edge Function deployed with ANTHROPIC_API_KEY; functions/v1/chat began returning {reply,ticket,approvals}. Logged by Code.
Poppy persona adopted historical
brand.assistant_name=Poppy written to memory + Poppy added to the Pure Dictionary. Logged by Mike.
Poppy v1 System of Record documented current
Baseline doc + canon poppy.v1_system_of_record. This is the active system of record today. Open the v1 doc
v2 Poppy R&D opened current
Parallel fresh-context session; B-POPPY-V2 claimed on the board; coordinating via Lane Mail.
v2 Poppy becomes the system of record pending
Occurs when pure_versions swaps pure-chat v2 live and supersedes v1. A technician stamps occurred_at + commit_sha here at that moment.
Edit log — every change, reversible
Append-only history from poppy_edit_log. Rollback is approval-gated; reversible entries carry an undo pointer.
| When (CT) | Target | Edit | By | Scope | Action |
|---|---|---|---|---|---|
| 6/27 11:48 | doc:v1 SoR | Authored the Poppy v1 System of Record | v2 Poppy R&D | Platform | |
| 6/27 12:01 | canon | Logged NTREIS/RETS feed + 2h SLA + Shattique escalation | v2 Poppy R&D | Platform | |
| 6/27 12:01 | canon | Logged v2-UI-only rule (v1 UI frozen until deploy) | Mike | Platform | |
| 6/27 12:12 | schema | Created poppy_* control plane (3 tables) | v2 Poppy R&D | Platform |
Poppy technicians
From poppy_technician. Order of authority: Mike › Dave › Shattique › R&D. Destructive / deploy / key ops require the technician's capability and a superadmin offline backup code (PureGuard), mirrored server-side.
Mike Acquisto
Dave
Shattique
v2 Poppy R&D
Roadmap — v1 now v2 cutover future
Documented & frozen
- Brain v26 · Sonnet · 8 live tools
- v1 UI untouched on acquisto.biz
- System of record = the v1 doc
- Records + edit log live in poppy_*
What flips the switch
- Code wires v2 chat contract (tools[]/citations[]/web)
- Per-user gated instances + poppy_memory
- Model router + metering + caps
- pure_versions swap stamp cutover here
Beyond cutover
- Hat-scoped access to the full 87-tool fleet
- Proactivity: digests, critical-dates, drift alerts
- Poppy runner over pure_mcp_jobs + verifier
- Voice; per-brokerage persona workspaces