The DandyLine Command Center

Your vision board. Everything in one place — what's live, what's in progress, and what's still just notes. Nothing gets lost.

Last updated: April 9, 2026

What Changed This Session

Vault decisions locked, new vault type created, 9 homework items added. This was a vault deep-dive session — the goal was to make the vaults bulletproof before moving into build.

🔒 Locked Decisions
  • ✓ Grove: seed recall = yes; pending invite display logic
  • ✓ Grove: Surprise tiers = 30 / 90 (default) / 365 days max
  • ✓ Grove: Occasion defines Milestone, not contributor count
  • ✓ Personal: occasion-first decision logic for vault chooser
  • ✓ Milestone: confirmed as distinct vault type — stays
  • ✓ Milestone: fuzzy/estimated bloom dates supported
  • ✓ Legacy: Guardian model (delivery-only, sealed content)
  • ✓ Legacy: death cert required; 7-day pre-auth / 30-day request
  • ✓ Journey: honor-system verification (no audience to perform for)
  • ✓ Journey: trickle delivery over 1–4 week randomized window
  • ✓ Journey story: grief / Day 365 (not sobriety / Day 30)
  • ✓ "Vaults as starting templates" — added to philosophy
✨ New This Session
  • 🌿 Roots vault created — 6th vault type
  •     Wide squat ceramic crock · Deep Teal (#4A8A85)
  •     Place-anchored community vault with geofencing
  •     "Sprouted Here" vs. "Rooted Here" location provenance
  •     Lake Cove anchor story (family land, 3 generations)
  •     EXIF metadata reading for photo location provenance
  •     Discovery modes: Public / Invite-only / Hidden
  • 📋 Homework items #20–28 added (9 new items)
  •     #20 Place Vault geofencing spec
  •     #21 Cross-vault privacy model
  •     #22 Jar description field & default text
  •     #23 Vocabulary teaching & progressive disclosure
  •     #24 Vault type conversion & seed transfer
  •     #25 "Surprise Me Too" self-locking toggle
  •     #26 Fuzzy & estimated bloom dates
  •     #27 Failsafe delivery date
  •     #28 Journey delivery formula
🔓 Still Open
  • ◦ XV: Cross-vault chooser decision tree (full build)
  • ◦ Roots: Discovery / Join / Contribution defaults (TBD)
  • ◦ Security/Legal docs: add Guardian + death cert details
  • ◦ Journey curation algorithm spec (#28)
  • ◦ "Surprise Me Too" toggle UX details (#25)
  • ◦ Vault type conversion flow (#24)
  • ◦ Failsafe delivery date system (#27)
  • ◦ Landing page: update to show 6 vault types
Session Score
+12 decisions locked +1 vault type +9 homework items 5 vault cards resolved

What We're Still Working Through

Running list of ideas, decisions, and things to develop. Add items as we chat — nothing gets lost.

01
Surprise "Hatch Family" Vault — Surprise Schedule Mode
Product Vault Mechanics
Default Grove vault schedule is always "Surprise" — everyone receives the bloom at the same random time. Countdown clock exists but nobody knows who sent it. Group anticipates together. Strong retention mechanic.
● Idea — Needs Development
02
Pooled Storage — Family / Group Investment Model
Business Storage & Monetization
Can storage be pooled across a group? One person pays, everyone in the group gets access. Shared capacity bar visible to all members. Need to build out full storage mechanics and pricing model.
● Idea — Needs Development
03
Pressed vs. Compost — Vault Preservation & Storage Lifecycle
Product Storage UX
"Pressed" = permanent, added to your Pressed Flowers collection. "Compost" = organic decay — photos lose resolution over time, text is last to go. Needs: compost window duration, decay mechanics, "Compost Soon" filter UX, whether sender knows the outcome, storage tier integration.
● Core concept documented — Needs UX flow design
04
Gardener Profile Settings — Personal Display Names
Product Profile UX
Recipients rename gardeners in their own settings — "Judy Blue" becomes "Grandma" everywhere (seeds, filters, notifications). Like renaming a phone contact. Needs: settings UX, where the name appears, privacy rules, personal avatars.
● Idea — Needs Development
05
Vault Sharing Permissions — Lead Gardener & Delegation
Product Permissions & Legacy
Four roles: Original Gardener → Lead Gardener → Gardener → Recipient. A grandparent assigns a daughter as Lead Gardener so future grandkids (even unborn) can be added. Critical for legacy vaults that outlive their creator. Needs: permission model UX, succession flow, storage ownership on transfer.
● Idea — Needs Development
06
Location-Locked Vault Type — Vault-Level Geofencing
Product Vault Mechanics
The entire vault stays sealed until you physically arrive — not just one seed, the whole jar. Childhood home, engagement spot, family's country of origin. Different from location-triggered seeds. Needs: GPS UX, sealed jar visual treatment, arrival notification design.
● Idea — Needs Development
GV
Grove — Relationship changes, contributor death, non-planters
✅ ResolvedGroveProduct
Locked decisions: Seeds planted before a relationship change (divorce, death) still bloom — the moment of planting is honored. Seed recall: yes, contributors can recall any time before bloom. Pending invites: small vaults show faded circles, large vaults show a count. Surprise window tiers: 30 days / 90 days (default) / 1 year max. Occasion defines Milestone, not contributor count — a multi-contributor vault for a specific birthday is Milestone, not Grove.
● Decisions locked April 9, 2026 — ready to build
PV
Personal — Line between Personal, Milestone, and Legacy
✅ ResolvedPersonalUX
Locked decisions: The occasion drives the vault type, not the contributor count. A solo parent planting for a child's 18th = Milestone (occasion-driven), not Personal. A grandparent planting for a grandchild because of legacy intent = Legacy. Personal = ongoing, untimed, no specific occasion — the planter is planting for themselves or someone close with no specific event as the anchor. Decision tree for vault chooser: Q1 is "Is this tied to a specific occasion or milestone?" → yes = Milestone, no = continue.
● Decisions locked April 9, 2026 — vault chooser can now be built
MV
Milestone — Is it really a distinct vault type?
✅ ResolvedMilestoneProduct
Locked decisions: YES — Milestone is its own distinct vault type and stays that way. The occasion is what makes it Milestone, not contributor count. One planter or many, if there's a specific occasion (18th birthday, graduation, wedding day) it belongs in Milestone. Vaults are starting templates — you can have a fuzzy graduation year with multiple graduation types in one vault; fuzzy/estimated bloom dates are supported with a confirmation prompt. The vault chooser should ask about the occasion first to route correctly.
● Decisions locked April 9, 2026 — Milestone stays distinct
LV
Legacy — Posthumous delivery mechanism
✅ ResolvedLegacyLegal / UX
Locked decisions: Legacy Guardian model (mirrors Apple's Digital Legacy Contact) — a designated trusted person who triggers delivery after death. Guardian role is delivery-only; vault content is sealed to them. Death verification: death certificate required. Two paths — pre-authorized (7-day waiting period) or request-based (30-day waiting period). Seeds planted before a contributor's death still bloom. These details need to be reflected in the Security/Legal reference docs.
● Core mechanism locked April 9, 2026 — UX delivery screen still needs design
JV
Journey — How does "temporal community" actually work?
✅ ResolvedJourneyProduct
Locked decisions: Honor system verification — there's no audience to perform for in Journey, so privacy-first self-reporting is correct. Trickle delivery: seeds arrive randomized over a 1–4 week window, so a sparse pool and a full pool feel indistinguishable to the recipient. Curation algorithm still needs defining (HW #28). Journey story updated: grief/Day 365 is the anchor story, not sobriety. The "Surprise Me Too" self-locking seed toggle applies here too (HW #25).
● Core mechanic locked April 9, 2026 — curation algorithm still needs spec (see HW #28)
XV
Cross-Vault — Chooser UX and minimum planting ritual
All VaultsUX
The vault chooser needs decision logic, not just descriptions. "Is someone else planting with you? → Grove. Is this for a specific event? → Milestone." Also: what is the minimum viable planting ritual? How long should it take? What confirms to the planter that this moment has been honored?
● Design this flow before launch

Build Tracker

7
Live Pages
11
Visual Concepts
37
Reference Notes
55
Total Items
Overall Site Development 44% Complete
Live — Deployed & styled
In Progress — Has visual concept
Notes Only — Reference doc exists
Pending — Not yet started

Launch Readiness Scorecard

A clear-eyed look at where DandyLine stands today — and what's needed before going public. The personal/family MVP is roughly 60–70% of the full product. The remaining 30–40% is hardening for public trust and compliance. These aren't dealbreakers — they're known, solvable gaps with a clear path forward.

65%
Personal / Family MVP

Core app — vaults, planting, bloom — is conceptually complete and buildable for trusted users (family & friends).

35%
Public Launch Ready

Infrastructure, security, trust systems, and legal compliance are still needed before opening to strangers.

Product Design & Vision
A–

Core concept is locked. Vault types are defined. Brand language and emotional UX philosophy are clear. A few open questions remain (vault chooser logic, Milestone vs. Personal distinction) but the vision is genuinely strong.

✓ Vision locked ✓ Brand defined
Brand & Marketing
A

Landing page is live, brand guide and ethos pages are published, ad concepts exist, and the emotional positioning is sharp. This is a standout strength — DandyLine looks and feels like a real product.

✓ Landing page live ✓ Brand guide live
Business Strategy & Financials
B+

Strong strategic notes, investor page live, financial model in progress. Monetization, fundraising, and TAM analysis are documented. Needs pricing model finalized and go-to-market plan tightened for launch.

~ Investor page live Financials in progress
App Build (Working Product)
C+

Visual concepts and UX flows are well-documented. No working app exists yet — the product lives in HTML prototypes and notes. Core vault logic still needs a few decisions before a real build can start.

~ Prototypes exist No working app yet
Infrastructure
Gap — Identified Apr 9
D

Personal/family MVP can run on cheap, small hosting — totally fine. Going public requires scalable, reliable infrastructure. The code is largely the same; what changes is where and how it runs. This is solvable, but has real cost implications at scale that should be planned for.

MVP: not a blocker Public: cost + scaling plan needed
Security & Trust
Gap — Identified Apr 9
D

With trusted family users, basic security is fine. With strangers, you need: proper authentication, account management, data access controls, abuse prevention, and data deletion policies. DandyLine's emotional content — memories, legacy messages, children's vaults — makes trust infrastructure especially critical to user adoption.

MVP: trusted users OK Public: full auth + controls needed
Legal & Compliance
⚠ High Priority — Address Early
F

Public launch requires: privacy policy, terms of service, and — critically — COPPA compliance (Children's Online Privacy Protection Act). Since DandyLine is specifically designed around named child vaults and legacy messages to minors, COPPA is a significant legal requirement before any public launch or monetization. For personal/family-only use, these don't apply yet — but get legal advice on this before opening to strangers or adding real payments.

MVP: family use OK Public: COPPA required first Privacy policy needed

Bottom line: The vision, brand, and product design are genuinely strong — those A grades are real and hard to earn. The gaps (Infrastructure, Security, Legal) aren't surprises or dealbreakers. They're the expected work of turning a personal passion project into a public product. Build the MVP first, validate with people you trust, then tackle hardening one layer at a time. COPPA is the one item to get legal advice on early — before any public launch or onboarding users with children's vaults.


Are You Ready to Start?

These are the accounts, decisions, and files you need in place before opening a build session. Most take 5–10 minutes to set up. Do these once — then you're ready to start Step 00 any time you have 30 minutes.

Step 1 of 3 · Accounts
Create These Free Accounts
Supabase — supabase.com
Free. Your database + magic link login. The backbone of the whole app. Sign up with your Google account for speed.
Resend — resend.com
Free up to 3,000 emails/month. Sends magic link login emails and bloom notifications. Connect your dandyline.app domain.
Twilio — twilio.com
Free trial included. Sends SMS bloom notifications ("Something is blooming for you."). Less than $0.01/text after trial. Optional for family beta — set up when you're ready for it.
Cloudflare R2 — Already your account ✓
You're already on Cloudflare Pages. R2 is in the same dashboard. Just needs a bucket created — Claude will walk you through it in Step 05.
Step 2 of 3 · Decisions
These Are Already Locked ✓
Platform: PWA — web app installable to home screen. iOS + Android.
Login: Magic link only. Email → tap → in. No passwords.
Notifications: Email (Resend) always. SMS (Twilio) optional opt-in.
Storage: Cloudflare R2 for media. Supabase for data.
Hosting: Cloudflare Pages. Already live at dandyline.app.
Build approach: Real code with Claude. You own every line.
Phase 1 goal: The full loop — plant → schedule → bloom → receive. For you + family first.
Step 3 of 3 · Session Setup
Have These Open When You Build
Cowork open with DandyLine folder selected — so Claude can read and write files directly.
Supabase dashboard open in a browser tab — you'll be looking at it a lot.
This homework page open — so you can reference the step you're on and check off when done.
30+ minutes of focused time — don't start a step if you might get pulled away mid-build. Steps 05 and 08 need 3-hour blocks specifically.
Tell Claude which step you're starting — just say "let's start Step 02" and the session begins immediately.
When you're ready to build:
Create your Supabase + Resend accounts, then come back and say "I'm ready — let's start Step 00." That's it. Everything else happens in the session.
Two More Things · Easy but Often Missed
1. Verify dandyline.app with Resend
So magic link emails arrive from hello@dandyline.app instead of a Resend address — which looks unprofessional and can hit spam folders. This requires adding a couple of DNS records in your Cloudflare dashboard (Claude will walk you through it during Step 02). You just need to know it's coming. Takes about 5 minutes. Decide your "from" address now: hello@dandyline.app is the recommended choice.
Decide: what's your "from" email address?
2. UX doesn't need to be finalized first
You already have strong UX references: ux-vaults.html, ux-bloom-reveal.html, ux-planting-flow.html. The MVP build uses these as starting points — it doesn't need perfect final specs. The 3–4 screens that don't have prototypes yet (login screen, vault list after login, seed confirmation) will be designed in real time during the build session. Seeing it on your phone will make those decisions faster than any planning session. Don't let UX completeness block you from starting.

Everything at a Glance

Home / Landing Page
Live Website
Brand Ethos
Live Brand
Brand Guidelines
Live Brand
Brand System
Live Brand
Ad Ideas & Concepts
Live Marketing
Visual Concept v5 — Reference UX Mockup
Reference Product
Investor Page
Live Business
Competitive Landscape Deep Dive
Live Strategy
Bloom Reveal Animation (v3)
Visual Concept Product
Brand System v2
Visual Concept Brand
Coaching Dashboard (v2)
Visual Concept Product
Dandelion Explorer (v3)
Visual Concept Brand
Deep Dandelion Seed Visuals
Visual Concept Brand
Copy Vault
Visual Concept Content
Vault Master (v2)
Visual Concept Content
Dandelion Variations
Visual Concept Brand
Glow Hover Study
Visual Concept Brand
Journey Color Picker
Visual Concept Brand
Vault Flow (v1)
Visual Concept Product
Master Vision & Concept Proposal
Notes Only Strategy
Master Business Document v1
Notes Only Strategy
Category Naming & Brand Strategy
Notes Only Strategy
Category Domination Roadmap
Notes Only Strategy
Product Differentiation Blueprint
Notes Only Strategy
Strategic Opportunities & Founder Roadmap
Notes Only Strategy
Go-To-Market Strategy Blueprint
Notes Only Strategy
Growth & Conversion Engine Blueprint
Notes Only Strategy
Landing Page & Waitlist Strategy
Notes Only Strategy
Founder Launch Roadmap
Notes Only Strategy
Founder Strategic Expansion Notes
Notes Only Strategy
MVP Build & Validation Plan
Notes Only Strategy
App Experience Visual Concept Walkthrough
Notes Only Product
Bloom Experience (Locked Concept)
Notes Only Product
Dual Timeline Home Architecture
Notes Only Product
Roots Memory Map Experience
Notes Only Product
Seed Planting Deep UX Flow
Notes Only Product
Future Connection Retention Loop
Notes Only Product
Grandparent Legacy Flow
Notes Only Product
Surprise "Hatch Family" Vault — Surprise Schedule Mode
Homework Product
Pooled Storage — Family/Group Investment Model
Homework Business
Pressed vs. Fade — Vault Preservation Lifecycle
Homework Product
Financial Model & Funding Overview
Notes Only Business
Financial Projections (Planning Version)
Notes Only Business
Monetization & Premium System Blueprint
Notes Only Business
Monetization + Security & Trust Blueprint
Notes Only Business
Fundraising Strategy & Psychology
Notes Only Business
TAM, Category Size & Moat Strategy
Notes Only Business
Security & Content Moderation Architecture
Notes Only Business
Investor Narrative & Founder Pitch Story
Notes Only Investor
Investor Emotional Narrative
Notes Only Investor
Viral Growth Ad Library (10 Concepts)
Notes Only Marketing
Emotional Ad Concepts & Brand Symbol
Notes Only Marketing

Live Pages

These pages are fully built, styled, and deployed to dandyline.app


Visual Concepts & Experiments

These exist as standalone HTML files — visual ideas and interactive prototypes not yet integrated into the main site.

Concept

Bloom Reveal Animation (v3)

The signature vault-opening animation — seeds dispersing and reforming as revealed content. Three iterations of the core emotional moment.

AnimationCore UX
Concept

Brand System v2

Updated brand system with refined tokens, expanded color palette, and new component variations.

Design SystemUpdate
Concept

Coaching Dashboard (v2)

User guidance interface — prompts, tips, and encouragement to help new users build their planting habit.

DashboardOnboarding
Concept

Dandelion Explorer (v3)

Interactive dandelion visualization — explore different seed types, colors, and animation states.

InteractiveVisual
Concept

Deep Dandelion Seed Visuals

High-fidelity seed renderings — detailed visual explorations of the core dandelion seed metaphor.

Art Direction
Concept

Copy Vault & Vault Master (v2)

Content library and master vault views — all copy, messaging, and content organized for reference.

ContentCopy
Concept

Dandelion Variations & Glow Studies

Mark variations, hover states, and glow effect studies for the dandelion icon system.

IconAnimation
Concept

Journey Color Picker

Interactive color selection tool for personal journeys and vault theming.

UXPersonalization
New

Vault Flow (v1)

Vault interaction flow — how users create, manage, and experience vault opening moments.

UX FlowVaults

Strategy & Planning

📝

These are working notes exported from ChatGPT planning sessions. They contain valuable strategic thinking but haven't been developed into full site pages yet. View all strategy notes →


Product Experience Design

📱

Detailed UX flows and experience architecture for core DandyLine features. View all product notes →

Notes

App Experience Walkthrough

Complete walkthrough of the DandyLine app experience — screens, flows, and interaction design.

Notes

Bloom Experience (Locked)

The core emotional moment — how vaults bloom open, the reveal animation, and the feeling it creates.

Notes

Dual Timeline Architecture

Past and future timeline views — how users navigate between planted memories and upcoming blooms.

Notes

Roots Memory Map

Visual memory map — how memories connect, grow roots, and form a personal constellation over time.

Notes

Seed Planting UX Flow

The core interaction — how users plant a seed, choose vault type, set bloom triggers, and attach memories.

Notes

Connection & Retention Loop

How DandyLine keeps users engaged — the emotional loop that brings people back.

Notes

Grandparent Legacy Flow

Intergenerational use case — grandparents planting memories for grandchildren to discover years later.

Homework

Surprise Vault — Hatch Family Grove

Surprise schedule mode where everyone receives blooms at the same random time. Countdown without knowing who sent it — pure anticipation.

Vault MechanicsRetention03.27.26
Homework

Pooled Storage — Group Investment

Family members pool storage capacity together. One person pays, everyone accesses. Shared progress bar fills up visually.

StorageMonetization03.27.26
Homework

Pressed vs. Fade — Storage Lifecycle

"Pressed" = preserved forever in your cloud. "Fade" = graceful expiration for unclaimed content. Need branded terminology and UX flow.

Storage UXPreservation03.27.26

Business, Finance & Investors

💰

Financial models, monetization strategy, investor narratives, and fundraising planning. View all business notes →


Marketing & Ad Concepts

🎤

Viral concepts, emotional ad frameworks, and campaign strategy notes. View marketing notes →

Founder Dashboard Homework Home