The whole journey as screens, in order, on real North Fork Valley data (46 live listings). Two questions born a team; the board sells the extension; a zero rides back as a card; the loop compounds. Each stage notes who the market authored vs. what the advisor authored — the boundary that governs everything.
Each morning, your advisor and the market agent read the public record on the homes you like — and brief you on what actually matters.
where resolves, the market reflects the place back; then you confirm or widen its boundary, and set the inventory range.This is the one thing your team can't work without — it's how we know which place to read for you.
where→market resolver + a published market-summary doc. That's the same build as fixing the createIntake Delta-hardcode. For an uncovered place there's no count — it's an honest "we'll stand up an agent for your area."A few things your advisor should know about you. This stays private; it's how it learns to brief you, not anyone else.
Optional — add WhatsApp and your advisor sends live alerts and a morning briefing there. Add it later from your account anytime.
delta.homezero.md. The board must live on that same origin, or "install → it's already you" silently breaks.savedListings + rings the cell.Two questions (place→market, person→advisor) → a team born → the board → the extension → a zero on Zillow → it lands back as a card → the loop sharpens. Every stage holds the boundary: the market authors the place & the home; the advisor authors you, the CliffsNotes, and every question. Spec: specs/the-flow.md (the through-line) + specs/surfaces/onboarding.md (the screens). Flags in red are the real build gaps — give feedback per stage.