POPPY | THE COORDINATED BUILD

One save‑and‑go. Three lanes. Poppy 3.0 & the merger, live.

Everything we've roadmapped, organized into three waves — each owned by a lane, each deploying when it's done. Poppy documents and generates, Code deploys and activates, Design integrates and brands. This page is the single board all three work from.

Poppy 2.0 · Awakening (live) Poppy 3.0 · Connected (this build)
Reading the live board…
The three waves

What ships, in what order — deploy at the end of each wave

No big‑bang. Each wave lands and is verified live before the next opens. Wave 1 is Poppy's truth pass (done in‑flight). Wave 2 makes the staged catalog real. Wave 3 lights up the engine Shattique's been waiting on.

Wave 1 · now

Truth & the plan

Clean the registry, tell the honest story, and stand up this board.

Reconcile 6 alias surfaces to live pages — no duplicatesPoppy
Sitemap + crawlable rebuilt (319) Poppy
Publish this Build Plan + 6 board tickets + lane‑mailPoppy
Define Poppy 3.0 Connected (teal)Poppy
Wave 2 · next

Make the catalog real

~43 built products go from staged source to live, cross‑linked pages.

Generate kebab pages from Title‑Case source, rewrite internal linksPoppy
Deploy via pipeline + verify no 404 cross‑linksCode
Nav + ecosystem map integrationDesign
Coverage goes green as routes resolvePoppy
Wave 3 · then

Activate the engine

The backend that turns built tables into living features.

Notification / message emit triggersCode
Saved searches on pure_alerts + email‑template adminCode
WordPress Pure CMS, forms, agent contentCode
Single DB confirm + RLS for new writesCode
The 50 staged surfaces — verdict

My recommendation: reconcile a few, deploy the rest, cut nothing

Every staged surface is a real, roadmapped product — none are junk. Here's the honest split, and it's exactly "no duplicate pages."

6
Reconcile done
Already covered by a live page — point the route there. Zero new pages.
43
Deploy as kebab
Built products with source ready — generate kebab + rewrite links, ship in Wave 2.
6
Fold candidates
Finance sub‑ledgers that may live inside Pure Books rather than as standalone pages.
0
Cut
Nothing to throw away — it's all real.
Fold candidates to confirm with you: property-details-fields · pure-1099-nec · pure-ar-aging · pure-cap-tracker · pure-pnl · pure-trust-account — these are accounting sub‑views. Deploy as their own pages, or fold them into Pure Books / Pure P&L? Your call decides whether Wave 2 is ~43 or ~37 pages.
Who owns what

Three lanes, no collisions

Poppy

Documents, generates, grades, keeps everyone honest.

  • Registry reconciliation + this plan
  • Generate kebab catalog pages (link‑rewritten)
  • Coverage / Versions / Digest stay live‑true
  • Version bump to 3.0 on completion

Code

Deploys and activates — the backend muscle.

  • Catalog deploy pipeline + cross‑link verify
  • Notification / message / alert emit
  • Saved searches + email‑template admin
  • WordPress Pure; single‑DB; RLS

Design (Lane A)

Integrates and brands — makes it feel like one product.

  • Nav + ecosystem‑map integration
  • Brand polish across new surfaces
  • Poppy 3.0 Connected visuals (teal)
Live coordination board

The tickets, straight from pure_board

These are real, claimable rows on the live board — each lane works its own. Status updates here as the build moves.

Reading the board…
Where this lives

Tied to everything

Evidence

Pure Coverage

The arc

Versions / roadmap

Strategy

Mega Merger Plan

How it wires

Second Brain

The Coordinated Build · graded live by Poppy