The Homework Board

Every idea, open question, and thing we still need to figure out — in one place. Nothing gets lost.

Last updated: April 18, 2026

BUILD · 2026-04-25 · B.10 · +6 cards from EOD spot-check feedback (HW#167-172 in quest-infrastructure-ops): cards-as-columns bug, audit Next-5 + Paused + What-to-start widgets, fix View Toggles, build top tracker (HW/week + Quest progress bars), build Quest TOC navigation. 167 total · all tagged · 23 Quests


🌱 What to start next session
Finish Rounds 3 & 4 of the Planting Flow unknowns — Journey vault (3 Qs) is the most undefined area in the whole product and deserves a fresh head.
Specifically, in order:
Q7 — How does the Journey "temporal community" actually work? (How many seeds arrive at a milestone — one, a handful, all?)
Q8 — How are Journey milestones verified? (Self-reported / honor-based / verification mechanism?)
Q9 — Does Journey need its own entry point separate from the main vault chooser?
Q10 — Media limits per tier (free / premium / Legacy).
Q11 — Surprise trigger algorithm behavior.
Q12 — Posthumous delivery for Legacy (mostly covered by Seed Key / Guardian already).
Q13 — Minimum viable "planting ritual" — can we collapse steps for casual use?

Then: dive into the vault-type deep dives (HW#86) — bring Personal / Grove / Milestone / Legacy / Journey up to the Roots-page level of definition depth. That's the foundational documentation debt.

Last session close: April 18, 2026. 9 of 13 planting-flow decisions resolved. HW#81–86 added for design work spawned from the decisions. Section C added to QUESTIONS-FROM-ASHLEY.md for Josh.
Seeds Bloomed
Items completed all time
Seeds Growing
Still in progress or needs development
Field Progress
— of — items resolved

Next 5 will populate once cards are retro-tagged with data-priority and data-status (Phase B + D).
Loading…
View Cards grouped by how close to bloom they are. Use the filter chips below to actually hide/show cards today.
Filter:

Quest · vault-rendition-system

Vault and jar visual design — shapes, orbs, animations, dandelion mark, bloom moments. The visual heart of the product. · 10 cards

38
Journey Vault Shape & Orb Animations — Finalize Wayfinder Style
Design Animation Roots Dev
Wayfinder was selected as the winning shape for the Journey vault (from the Shape Lab in roots-jar-compare.html — angular, octagonal edges like a compass housing). However, the session ended on HOLD because the orb animations inside the jar had drifted significantly from Ashley's preferred style. Before closing out this card: (1) Ashley needs to find the reference file or session showing the orb animation style she preferred, (2) open the ROOTS_Development session to pick up where we left off, (3) restore orb animation to the preferred style, then (4) finalize and commit the Wayfinder as the official Journey vault shape across all product pages. Do not change the Wayfinder shape decision — that is locked. Only the animation style is open. Added 04.12.26.
🔨 Build Session
🎨 Visual / UX Design
● In Progress — HOLD — Resume in ROOTS_Development session
#70 — Vault/Jar Renditions · TOP PRIORITY · Decisions Pending · Resume Next Session
Design System Brand Jars & Vaults On Hold
Where to jump back in: Open brand-vault-renditions.html. Full end-to-end vault rendition system built over two sessions: icons with per-vault dot language (Section 01, LOCKED), vault interior phone mockups with jar as background hero (Section 02), animated sealed jar + unsealing flow (Section 03), deep dandelion close-up destination (Section 04), and 10 additional rendition ideas (Section 05).

✓ LOCKED this session (don't re-decide):
  • Mix 6 colors — Grove #7A9E7E sage · Personal #8BAEC8 sky · Milestone #D4A853 gold · Legacy #6B5B8A purple · Journey #3A7A75 deep teal · Roots #C4704A terracotta
  • Wayfinder shape — Journey's new 8-sided angular compass-housing silhouette (replaces the old amber rectangle)
  • Icon system — two sizes (Tiny 28×36 + Compact 60×78). Halo ON = selected/active state, halo OFF = default/unselected state. Halo radius = min(W,H)×0.62, center alpha 0.16, gentle pulse.
  • Per-vault dot language — Grove: 3 orbiting · Personal: 1 centered · Milestone: 1 large pulsing · Legacy: 1 low + 2 layer lines · Journey: 6 ascending lighting path · Roots: 5 converging. Never swap or simplify.
  • V2 dandelion rendering — gold→cream→vault-color gradient stems, ripple rings on deeper active orbs, Mix 6 seed palettes per vault, jellyfish float, golden center pulse with specular highlight

Decisions pending (review + lock next session):
  • Section 02 Vault Interior — does the new "jar as background hero" layout feel right? Jar now fills the phone, text floats over it with backdrop blur on contributor chips, countdown replaces Blooming Now CTA on Stella's
  • Section 03 Unsealing Flow V3 — rest-state dandelion visibility bug fixed, lid now fades aggressively to prevent layering weirdness. Does it feel like ONE continuous motion?
  • Section 04 Deep Dandelion Close-Up — does the destination state (5 active + 19 inactive seeds, vault-color tinted, sample popup overlay on Stella's tile) feel right as the endpoint?
  • Transition wiring — do we wire Section 03's unsealing to TRANSITION INTO Section 04's close-up? Jar fully dissolves at peak, deep dandelion takes over.
  • Countdown treatment on Stella's phone — size, position, gold coloring — does it feel right?
  • Section 05 — pick priority renditions to build next: Single Seed Bloom (most product-critical), Empty State, Vault Shelf, Inline Pill, Sealing animation, Thumbnail/Avatar, Held in Trust, Conversion, Grove Stack, Compost State

After locks → SWEEP these pages (critical — don't lose this list):
  • product-vaults.html — six-vault overview grid + dandelion-in-jar canvas. Old amber Journey rectangle → Wayfinder + Mix 6. VC config seed palettes → update to new Mix 6 semantics.
  • product-roots.html — Place Vault hero + Interactive Prototype V2. DO NOT LOSE OR RUIN the Interactive Prototype V2 animation — it's the reference dandelion we adapted from. Only update the jar shape/color references, not the working prototype.
  • brand-guide.html — Ritual Vocabulary section, any small jar icons
  • brand-system.html — component inventory, jar references
  • brand-color-system.html — color naming rules + Mix 6 documentation (Journey changed from amber to deep teal; Grove changed to sage; Milestone changed to gold; Roots changed to terracotta)
  • ux-vault-flow.html — vault chooser flow (where the selected-state halo will really shine)
  • ux-bloom-reveal.html — uses old SVG-based jar rendering, update to canvas
  • biz-dev-command-center.html — TOC jar glyphs
  • ux-planting-flow.html, ux-field-homepage.html, site-landing.html — any jar imagery
  • Also sweep old-palette language: any page still referencing amber Journey, gold Grove, or sage Milestone (pre-Mix 6 colors) needs updating
  • Run a final grep for #C4704A as Journey (old), #4A8A85 as Roots (old teal), and anywhere the Journey straight-sided rectangle path still exists

Connects to HW#69 (Button System): Once jar renditions lock, button project (pill vs rounded rectangle, CTA styles) will feel more grounded — we'll know which vault-color accents are locked. Button sweep should follow the jar sweep.

Constraint to remember: When sweeping product-roots.html, the Interactive Prototype V2 animation is untouchable. Ashley explicitly said it's "sooo good." Only update surrounding shape/color references, never the working prototype.
🧠 Deep Project
🏗️ Build with Claude
⏸ On Hold — TOP PRIORITY Next Session

#126 — Calm Memory Garden · Home Screen Visual Philosophy

Parked Ashley Medium Quest #1 · Vault Rendition

The emotional-design direction for the home screen: quiet, hopeful, intentional, uncluttered. No ads, no chaotic feeds. Users see a soft horizon timeline with floating seeds drifting at different depths — closer = blooming soon, distant = years away. Looking forward in life, not scrolling backward.

What's Next
  • Review during Phase C — consolidate into the canonical Vault Rendition card or keep standalone for home-screen specific guidance.
Highlights
  • Core principle: "Looking forward in life rather than scrolling backward"
  • Seed color language: warm gold glow = opening soon; soft blue = reflective; pink = love/family; green = growth/journey
  • Motion language: gentle drift = long-term; subtle pulse = upcoming bloom; still seed = distant future
  • References: Source was biz-dev-notes-product.html (retiring Apr 22, 2026)
Working Pages
Notes — Full cleaned prose

Home Screen — Future Memory Timeline

The home screen should feel quiet, hopeful, intentional, and uncluttered. There are no ads, no chaotic feeds, and no pressure to perform. Instead, users see a soft horizon timeline with floating seeds drifting gently at different depths. Closer seeds represent memories opening soon. Distant seeds represent years into the future. Each seed shows: memory title, bloom countdown, subtle emotional glow color. Users can tap seeds, sort by time or person, and plant new memories. This screen should feel like looking forward in life rather than scrolling backward.

Seeds Waiting to Bloom — Visual Language

Each seed has emotional visual meaning. Warm gold glow = opening soon. Soft blue glow = reflective memory. Pink glow = love or family. Green glow = growth or journey. Motion also communicates time: gentle drift = long-term memory; subtle pulse = upcoming bloom; still seed = distant future. Time becomes emotional instead of numerical.

Vault Screen Layout

When a user taps a seed, they see a vault card represented as a glass jar silhouette. Inside is a faint preserved dandelion shape showing: number of seeds inside the capsule, number of contributors, creation year. Users then enter the vault.

Dandelion Capsule UI — Core Experience

Inside the vault, users see a full floating preserved dandelion. Each seed represents a memory contribution. Seeds show: media icon (photo, video, voice note, text), contributor indicator, unlock timing. Glowing seeds are ready to open. Locked seeds show countdown timing. When a seed is opened, the memory appears in cinematic viewer mode, the seed becomes marked as opened, the visual color shifts slightly, and the seed subtly settles lower on the dandelion. This creates a feeling of gradually harvesting memories.

Locked Seed Interaction

If a locked seed is tapped, the user sees: "From Grandma · Recorded when you were 3 · Opens in 6 months." This builds anticipation and emotional connection.

Emotional Notification System

Notifications feel poetic and gentle. Examples — Bloom Ready: "A memory you planted years ago is ready to bloom." Upcoming Bloom: "In 3 days, you'll hear from your past self." Location Root: "There are deep memories planted where you're standing." Contribution: "Mom planted a new seed in your life capsule." Reflection Prompt: "Today might be worth preserving." Notifications are never urgent or sales-driven — they invite reflection and meaning.

Experience Philosophy

DandyLine should feel like a calm memory garden. Users are not overwhelmed by content. They are surrounded by meaningful moments waiting to unfold. The experience encourages intentional memory creation, emotional anticipation, and long-term reflection. The app becomes a peaceful space where time itself becomes part of the storytelling experience.

Cleanup applied: Removed sun/moon/stars celestial framing (retired). Language preserved otherwise.

History
  • Migrated from biz-dev-notes-product.html (lines ~143-253) before notes-page retirement. Celestial language stripped.

#141 — Living Wind (Dandelion Gust Animation)

Thinking Ashley Medium UX · Dandelion

Periodic gentle wind passes through the dandelion every 8–14 seconds. Front seeds sway more than back seeds (parallax). Occasionally a single seed catches a stronger gust and drifts a few pixels off its base before settling. Background gradient subtly shifts to suggest the wind passed through. Differentiation: most app dandelions are static or single-loop — "wind that comes and goes" makes the screen feel like a living place, not a graphic.

What's Next
  • Decide gust frequency (8s? 14s? random range?)
  • Decide whether to build as a prototype extension on top of TEMP-dandelion-concepts.html
  • Lock in spec only after prototype feels right

#143 — Time-Color Dandelion (Glanceable Status)

Thinking Ashley Low effort · High clarity UX · Dandelion

Each active seed on the dandelion colored by its time-distance bucket (Purple 1+ year / Sky 31-364 days / Gold 0-30 days / Gold-Light imminent / Sage bloomed — per the locked spec). At a glance, the dandelion's overall color tells you the state of your entire memory portfolio. Implementation: already supported by color system — just apply per-seed instead of global. Low effort, high information density.

What's Next
  • Decide: is this on by default, or a toggleable "view mode"?
  • Resolve visual conflict with vault-tint (do seeds prioritize vault color or time color?)
  • Prototype on top of existing concepts page if approved

#144 — Constellation Mode (Tap Vault → Connect Seeds) ⭐

Prototype Built Ashley High · Flagship UX · Dandelion

Second-highest-leverage concept. Tap a vault chip → that vault's seeds glow in vault color, others dim, faint gold lines connect the seeds into a constellation. Solves a real problem (how do you see "what's in this vault" without leaving the dandelion?) AND adds visual delight. The constellation metaphor pairs with "your memories are stars across time." Prototype interactive in TEMP-dandelion-concepts.html. Ashley feedback 2026-04-24 evening: "Constellation mode feels better, softer, elegant. Love the stem glow!" — promoted to flagship-tier. Asked whether this is "just filtering" — answer: core mechanic IS filtering, but with two visual upgrades that make it feel alive (selected stems shift to vault color, gold connecting lines show belonging).

What's Next
  • Tap the prototype chips and react — lines feel like constellation (good) or network diagram (too techy)?
  • Tune line thickness, opacity, curvature, fade-in speed based on feel
  • Decide: does it live on the Field homepage dandelion, or only in vault interior?
  • If approved, canonicalize into DESIGN-SPEC.md Section 9H (Field Homepage)
Highlights
  • Prototype: TEMP-dandelion-concepts.html
  • Cross-reference: Entry 013 in ux-inspiration-library.html (3D globe concept complements this)
  • Ashley-approved enhancements (2026-04-24 evening) for v2 prototype:
    • Vault name label fades in when selected ("Sparks Family · 3 seeds") — gives context to the filter
    • Selected seeds breathe slightly faster or larger ("you called us" response — subtle, not gimmicky)
    • Unselected seeds slightly recede backward (depth illusion) instead of just dimming — makes the constellation feel more dimensional

#145 — Anticipation Whisper (4th Pulse Tier)

Thinking Ashley Polish tier UX · Dandelion

A subtle new state between "Blooming Soon" (gold) and "Bloom Now" (gold-light). When a seed is within ~24 hours of blooming, its glow develops a faster fluttering whisper — almost like a held breath. Users who check the app often will notice the whisper start and feel the bloom approaching. Tiny UX gift for attentive users. Low effort — extends existing pulse system with a 4th speed tier.

What's Next
  • Decide trigger threshold (24h? 6h? 1h?)
  • Decide pulse speed (faster than Bloom Now? same? different amplitude?)
  • Can live inside existing pulse formula — see DESIGN-SPEC.md Section 5 Orb Pulse System

#146 — 3D Dandelion Bloom-Globe (Rotate to Discover) ⭐⭐

Prototype Built Ashley High · Flagship Moat UX · Dandelion · Discover

The biggest concept. Alternate "Home / Discover" view replacing the static vault grid. Translucent 3D dandelion sphere floats in a star-flecked sky. Seed-fluffs stick out in all directions — drag to spin the globe, release and it idle-drifts at ~120s/revolution (Apple Maps pattern). Seeds you've forgotten about drift into view from the back of the sphere. Built in pure Canvas 2D with 3D math in TEMP-dandelion-globe.html — no Three.js dependency so Josh can port directly. From Inspiration Library Entry 013.

What's Next
  • Try the prototype — drag, release, let the idle drift surface seeds
  • Decide: is Globe view the primary Home, or a toggle alternate alongside Grid view?
  • Josh feasibility spike — canvas 2D holds up to 60 seeds well; test with 100-200 for heavy users
  • Post-MVP: pinch-to-zoom (requires touch event handling + matrix scaling)
  • Post-MVP: tap-to-focus (seed card flies out to fill screen)
  • Add to Inspiration Library entry as "prototype built, see TEMP file"
  • 2026-04-25 (Ashley): Globe rotates but feels rigid — no floating bob on the whole dandelion or on individual seeds/stems. Per-seed jellyfish pulse spec exists in DESIGN-SPEC.md §5 but may not be applied to the globe; whole-globe vertical bob was never spec'd at all. Fix scope: (1) layer per-seed pulse over rotation transform, (2) add gentle whole-assembly vertical drift. Ashley taking up in a separate session.
Highlights
  • Prototype: TEMP-dandelion-globe.html
  • Source inspiration: Entry 013 in ux-inspiration-library.html — Apple Maps 3D globe + Flighty flight-path pattern
  • Why it's the moat: First interaction in the app that visually fulfills the dandelion metaphor. Makes DandyLine's 3D brand story literal. No competitor has anything remotely like this.

#163 — Unsealing Flow V3 Fix (Portal Moment + Timing Sync)

Thinking Ashley High · MVP Ceremony UX · Animation

Ashley flagged the current Unsealing Flow V3 visual in brand-vault-renditions.html as "pretty poor." Deep read identified 3 specific failures: (1) timing desync — lid fades at ~1.35s but dandelion keeps scaling/moving until 3s, reads as two disconnected animations instead of one ceremony; (2) no portal moment — no visual cue at the lid opening marking "this is where the dandelion emerges"; (3) layering conflict — jar fades while dandelion is still inside jar bounds, so dandelion briefly appears to push through jar walls instead of emerging through the lid. This is the ceremony that happens on every bloom reveal — it must feel like one continuous birth, not a 2-phase transition.

What's Next
  • Delay dandelion scale-up until lid is fully cleared (lid 0-1.35s, dandelion 1.35-3s)
  • Add gold-glow portal at the lid opening as dandelion emerges (birth-through-specific-point cue)
  • Clip the dandelion to above the rim until emergence moment (no push-through-walls)
  • Build a new prototype (`TEMP-unsealing-v4.html`) before committing to the spec
  • Once approved, replace V3 in brand-vault-renditions.html AND add to DESIGN-SPEC.md Section 7 Animation Specs
Highlights
  • Current V3 code: brand-vault-renditions.html lines 343-345 (grid container) and 679-706 (lid/rim lift logic), 995-999 (emergeT calculations), 1072-1084 (dandelion rest position)
  • Why it matters: Unsealing happens every bloom — it's the single most-repeated emotional moment in the product. Get it right once, ship forever.
  • Cross-reference: DESIGN-SPEC.md Section 9C Bloom Delivery Flow Step 2 — "~4.6 seconds for the full sequence"

#164 — Single-Seed Bloom Animation (Most-Used Animation)

Thinking Ashley High · MVP Flagship UX · Animation

Per brand-vault-renditions.html Section 05 Idea 05, the Single-Seed Bloom is "the most product-critical animation because it's the most-used." When a single seed blooms, one orb lifts from the dandelion, drifts up through the lid opening, and opens into the bloom-reveal view. This happens every single time a seed is ready to reveal — potentially multiple times per user session. Spec is currently open: lift trajectory, easing curve, duration, transition into bloom-reveal content, whether the orb "opens" or dissolves. Related to HW142 (Bloom Lift-Off) which is the same idea with a prototype already built.

What's Next
  • Review HW142 Bloom Lift-Off prototype (TEMP-dandelion-concepts.html) — it IS this animation, just not yet canonicalized
  • Decide: does the orb dissolve into content, or physically transform into the bloom card?
  • Lock trajectory — straight up, gentle arc, or scatter-like dandelion puff?
  • Lock duration — ceremonial 1.5s? Swift 0.9s?
  • Coordinate with HW163 — if single-seed bloom happens inside a vault (not on the Field dandelion), does it trigger an Unsealing first, or skip straight to the lift-off?
  • Once locked, canonicalize into DESIGN-SPEC.md Section 7 Animation Specs
Highlights
  • Related homework: HW142 (Bloom Lift-Off — has working prototype)
  • Source: brand-vault-renditions.html Section 05 "Additional Renditions Ideas" Idea 05, line ~456
  • Why it matters: Single most-used animation in the product. If it's off by 100ms or the easing is wrong, users feel it every bloom. Worth overdesigning.
📎 Merged In · From HW#142 (was: "Bloom Moment (needs rework — literal lift-off felt cheesy)")

Merge reason · Bloom Moment and Single-Seed Bloom Animation are the same animation (cards explicitly cross-reference each other). Original card consolidated 2026-04-25.

Description: Ashley feedback 2026-04-24 evening: "Bloom Lift-Off feels cheesy and way off." Original prototype was too literal — seed detaching + stem wilting + particle trail = three competing effects, lift distance too big (90px), reads as cartoon eject rather than ceremonial release. Recommended direction: Path B — scrap the "lift off" metaphor entirely. Real dandelion flowers don't lift — they OPEN. Bloom in place: orb expands outward, pulses into gold-light, transforms into content card. Stem stays. No physical lift. This also better aligns with the actual dandelion life cycle (wind-scattering comes later as a separate moment — maybe reserve lift for the "Plant Forward" action or Wind-style event). Previous prototype in TEMP-dandelion-concepts.html should be considered stale.

Original What's Next:
  • Watch the prototype and decide: keep lift height, tune particle density, adjust wilt dramatic-ness
  • Decide: does the lifted seed float off-screen, or settle somewhere (Pressed archive icon?)
  • Decide: single-seed lift vs. simultaneous multi-seed (for Grove vaults)
  • If approved, canonicalize timing into DESIGN-SPEC.md Section 7 (Animation Specs)
Original Highlights:

Quest · seed-lifecycle-preservation

Seed planting → composting → release. Storage tiers, preservation states, the lifecycle that defines the brand. · 9 cards

195
V4 Polish · post-tone-color-lock follow-ups (3 items captured 2026-04-27 evening)
UXV4Polish
Three small V4 polish items Ashley spotted at end-of-session reviewing the tone-color port. Bundle these into one focused pass next time you open V4.

Re-entry point: Open TEMP-dandelion-globe-V4.html. Tackle in this order:

① Filter panel lifecycle icons need to match the new behavior-icon style · The filter panel's Lifecycle pill row currently uses .fp-dot colored dots (from the old lifecycle-color model). The bottom-sheet "Seed Lifecycle Key" was just rebuilt to use behavior-preview icons (animated rings for Bloom Now, rotating orange dashed ring for Composting, sparkle pattern for Pressed, dotted geofence for Location-Locked, etc. — see .ic-now / .ic-soon / .ic-pressed / etc. CSS in TEMP-seed-color-demo-on-globe.html). Port the same icon styles into the filter panel's lifecycle pills so the two surfaces match. Visual consistency: a "Bloom Now" pill in filters should preview the same mechanic as a "Bloom Now" cluster in the key.

② Hint chip "Showing X of Y · open in Library →" looks misaligned at high density · Ashley's screenshot at density 60 shows the hint chip overlapping the toggle area awkwardly — looks like an extra button stuck onto the chrome. Investigate position/styling at the 60 / 120 / Stems Only thresholds and tighten alignment.

③ Composting · Practical popup also sticks at bottom of dandelion · Same back-hemisphere popup-stuck issue Ashley flagged earlier for Drifting (HW#186 item ②). The Composting popup has the same problem. The fix in HW#186 ② (raise seed.projZ threshold or check rendered orb visibility before showing tooltip) should cover both — but verify both Drifting AND Composting are resolved when that fix lands.

What's NOT in this card (handled elsewhere):
· Ring/donut counter for the Field bottom sheet → HW#186 item ① (also includes the field-bar gradient drift question per the Apr 27 evening tone-color lock)
· Globe / Library toggle rename → HW#186 item ⑥
· Tier 1 → Tier 2 click expansion QA → HW#186 item ⑧

Filter pill avatar+name concatenation bug · already fixed Apr 27 evening (commit 84b38c4) — clicking "Ashley" was showing "AAshley" in the active-filter chip row because pill.textContent was reading the avatar circle's letter + name together. Now reads only direct text nodes.
Medium
🎨 UX/Polish
● 3 sub-items · pair with HW#186 next session · all small fixes
186
V4 Dandelion-Globe · Round 2 follow-ups (8 items captured 2026-04-27 EOD)
UXV4Round 2
Consolidated follow-up work for TEMP-dandelion-globe-V4.html from Ashley's Apr 27 EOD feedback. Pick up next session in this order — items are scoped so you can ship them in one or two focused passes.

Re-entry point: Open TEMP-dandelion-globe-V4.html. Snapshot first. Tackle in roughly this order:

① RING VISUAL (the main "I misread the brief" item) · Build the canonical donut/ring counter from ux-field-homepage-v3-motionmark-depth.html (lines 252-267 HTML + 370-442 JS) into the Field bottom sheet. Outer R 78, inner R 58, breathing pulse, segment glow per lifecycle color, big "47 SEEDS" in center. KEEP the existing bar chart — Ashley is TBD whether she'll prefer ring or bar. Add a small toggle to switch between the two if both stay.

② Popup-stuck for back-hemisphere orbs (Drifting/Composting) · ✅ RESOLVED 2026-05-01 · Per-lifecycle threshold added in positionTooltipsByUid — Drifting + Composting now require projZ > 0.20; everyone else stays on > 0.05. Verified via direct unit test on the function. Also closes HW#195 sub-item ③ (Composting popup-stuck — same root cause).

③ Lifecycle filter split · Filter panel's Lifecycle row currently mixes pre-bloom + post-bloom in one long pill row. Split into two groups: Sealed (warming: Bloom Now/Blooming Soon/Approaching/Patient/Distant/Location-Locked) + Memory (post-bloom: Bloomed/Drifting/Composting/Pressed). Group labels TBD — "Sealed / Memory" or "Coming Soon / Bloomed."

④ Mode badge cleanup + per-vault metadata swap · Badge currently reads "ROOTS · COVE · SINGLE VAULT" (three units, redundant). Drop the "single vault" suffix. Also: when filter narrows to a different vault (e.g. Grove), the badge changes but contributor avatars + jar metadata (Started by KeKe · Summer 2023 · "Anyone who loves the Cove...") don't swap — feels inaccurate. Build a per-vault metadata lookup so jar info actually changes when filter changes (mock data is fine).

⑤ Composer mini jar icons · Vault-picker chips in the Plant composer currently show colored dots — should use canonical mini jar SVG icons per brand-vault-renditions.html drawIconJar() + ux-vault-flow.html createGroveJar / createPersonalJar / createLegacyJar.

⑥ Toggle rename · ✅ RESOLVED 2026-05-01 · Picked Puff / Roll. Applied to topbar toggle in TEMP-dandelion-globe-V4.html + the descriptive note in the future-renditions list ("Puff → Roll transition"). Verified live in preview.

⑦ High-density rendering at 60/120 + Stems Only mode breaking down · Investigate. Stem density math may need cap; Stems Only mode probably needs an explicit empty-state visual ("plant your first seed" CTA in bottom sheet?). The "perpetual depth" rule (HW#143 ref) should make 120 feel intentionally abundant, not chaotic.

⑧ Tier 1 → Tier 2 click-expansion QA · Ashley reported "pop-ups don't expand currently." DOM eval confirmed the handler is wired + the card opens with correct data. Possible: she may want a more prominent/dramatic expansion (currently 230px wide, may not read as "expanded enough"). Verify in real browser; if confirmed insufficient, bigger card / more lift feel.

⑨ Search function · Add a search input above the filter pill row. Lets a Gardener type to find Seeds/Vaults by name, contributor, date, or content type. Pairs with — but doesn't replace — the existing lifecycle/Vault/contributor filters. Mocked results for now; real wiring waits on the API. Inspired by Moleskine intake (May 2, 2026 session).

What's already done in V4 (don't redo): Garden mode default · Apr 28 vocabulary lock · tooltip identity bug fix · density toggle 12→120 · 10 lifecycle states (Drifting added) · anchored-depth popups · 5-popup cap · floating chrome + backdrop blur · pill-based filter panel · push-aside→modal-overlay · sheet pull-up gesture · Tier 1→2 click handler wired · vault-picker on Plant FAB · Starlight Cove cast · canonical avatars · field stats bar · labels on/off eye toggle · Drift Oat + Compost Terra in brand palette.

Snapshots to roll back from if needed: 5 dated V4 snapshots in folder + git history e8fbe7d ← 91d57ec ← 0cf90d2 ← 69d03a2.
🧠 Deep Project
🎨 UX/Build
● 8 sub-items · pick up next session · ① ring visual is the highest-impact
185
Inline Plant Composer — full design (vault-pick → media-pick → details → plant)
UXPlantingComposer
Captured 2026-04-27 from V4 dandelion-globe build. When the gardener taps the gold Plant FAB in the bottom nav, an inline composer should slide up — letting them quickly plant a seed without leaving the Field/vault context. Currently stubbed in TEMP-dandelion-globe-V4.html as: Step 1 vault picker (chips for Grove/Personal/Legacy/Roots/Journey + New vault) → Step 2 media-type picker (Photo/Video/Voice/Note/Mix). Long-press on Plant FAB opens the full ux-planting-flow.html.

What needs to be designed: the post-picker UX (capture surface for each media type · title field · emotion tag picker · timing chooser · recipient field · plant CTA · how it ties back to the canonical full planting flow). Should the inline composer be the ONLY composer, with the full flow being for first-time setup? Or is full-flow always available for advanced cases (multi-recipient, location-locking, Held-in-Trust setup)?

Linked: ux-planting-flow.html · HW#75 (compost trigger) · brand vocab Mix as the 5th media type (per product-roots-storyline-starlight-cove).
🌿 Medium Project
🎨 UX/Build
● Stubbed in V4 · full design pending
184
"Drifting" timing — when does a Bloomed seed start drifting toward compost?
ProductLifecycleStorage & Monetization
Vocab decision locked 2026-04-27: "Drifting" is the warning state between Bloomed and Composting — a bloomed seed approaching its compost window where the user gets a last chance to Press it before passive degradation begins. Visualized in TEMP-dandelion-globe-V4.html as the 10th lifecycle state (warm cream/oat color, italic state label).

What's TBD: the trigger logic itself. Options to evaluate: (a) auto after N days post-bloom regardless of opens · (b) auto after N days unopened · (c) when storage tier is being reclaimed · (d) hybrid — softer warning at X days, hard tip into Composting at Y days. Picking the right formula depends on understanding storage cost economics and how conservative/aggressive DandyLine should be with the degradation window.

Why we're parking this: No need to lock the formula yet. Visualization + vocab are in V4 so the concept is captured. Decision can be tweaked later. Hard deadline: before broader onboarding (don't ship to non-internal users with this undefined — the implications hit real user data).

Linked: HW#75 (Compost Trigger Logic — auto vs opt-in), HW#76 (Storage Visibility), HW#90 (Released ceremonial UX). Memory: see feedback_lifecycle_vocabulary.md for the full lifecycle order.
📋 Decision Session
📋 Product Decision
● TBD — Vocab + visual locked, trigger formula deferred (storage-cost dependent · resolve before broader onboarding)
72
"Preserve Entire Jar" Option — One-Tap Vault Preservation
ProductStorage & Monetization
Allow gardeners to preserve an entire jar with one action. Show hidden detail of full jar size (excluding items others already preserved). Display vault-wide preservation status and rules. Design logic for edge cases: what if some seeds are already pressed by others? Can you "double-preserve"? Needs visual treatment in jar details view. Ashley wants this to feel like peace of mind, not a sales pitch.
🧩 Medium Build
📋 Product Decision
● Idea — Needs Development
75
Compost Trigger Logic — Auto vs. Opt-In at Plant Time
ProductStorage & Monetization
Does composting auto-trigger (assume nothing is pressed)? Or do gardeners opt to press/preserve at planting time? Or both? Ashley's concerns: "what if no one ever opens it to trigger composting?" "what if every user preserves everything?" Consider: compost countdown notifications — do they get more aggressive over time? Emotionally weighted prompts for monetization ("Are you sure you want to compost 'Secret Drunk Chicken Family Recipe' from Grandpa?"). Options on compost card: Compost (schedule delete), Preserve/Press, Download to Device, Delete Now. Ties to existing compost homework items — merge/update as needed.
🧩 Medium Build
📋 Product Decision
● Idea — Needs Development
76
Storage Visibility Interface & Purchase Flow
UXStorage & Monetization
Design storage visibility dashboard with easy access to add storage and see pricing/packages. Ashley took 4 Apple iCloud storage screenshots (April 15) as inspiration — reference those. Needs: current usage bar, breakdown by vault, easy upgrade path, price/package options visible. Should feel empowering ("look how much you're preserving") not alarming. Tie to Preserve Jar (HW#72) and compost prompts (HW#75).
🧩 Medium Build
🛠 Build Task
● Idea — Needs Development
90
Released — Ceremonial UX for the Release Moment
UXAnimationCompost
When a Gardener taps "Release Now" in the Compost bin — choosing to permanently release a seed before the 30-day window expires — this is a conscious, intentional act. It deserves a ceremonial moment. Proposed: the seed dissolves into dandelion wisps that float upward and away. Gone, but gently. The automatic case (30-day timer expires with no one watching) could trigger a soft notification: "A seed was released today" — tapping it shows the same brief floating animation. Open question: does the notification-triggered ceremony feel right, or does it feel like being summoned to watch something disappear? Could be lovely, could feel wrong — needs a design sprint to find out. High priority polish item, not a launch blocker. Build after the core compost flow is live. Vocabulary locked: Released = permanently gone. Press = preserve. Composting = decay window.
🌿 Medium Project
🎨 UX/Animation
● High Priority Polish — After core compost flow ships
95
Artwork Seeds — Photo Upload + "You Told Me This Was..." Caption Layer
Strategy PMF Product Seed Types
Artkive charges $75 for a mail-in art book. DandyLine can do this in the planting flow for free, with more emotional depth. An "Artwork Seed" photo type that adds a custom overlay field: "You told me this was ___." The parent photographs the crayon drawing, types what the child said it was ("a rocket ship that flies to the moon for snacks"), and the seed preserves both the artwork and the story behind it. When it blooms in 10 years, the child sees the art and reads what they told their parent about it. This is the Artkive play, but the story layer is the differentiator — Artkive just archives, DandyLine archives + contextualizes. Needs: a new seed type variant (or a metadata field on photo seeds), the caption overlay design, and the bloom card layout that presents artwork + caption as a paired unit. Added 04.22.26.
🔨 Build Session
📋 Product Decision
● Idea — Needs Development
96
Artwork Collage Bloom — End-of-Year Art Book Output Feature
Strategy PMF Product Export
Pairs with HW#95 (Artwork Seeds). If a parent plants 20+ Artwork Seeds over a year, DandyLine could auto-generate an "Art Year" collage when the year-end Journey Vault blooms — a beautifully laid-out digital page (or physical book upsell) showing all the artwork from that year with captions. Think of a kindergarten memory book, but made from seeds the parent already planted throughout the year. The magic: no extra work required at bloom time. The parent planted the seeds one by one. DandyLine assembles the collage automatically. Competitors (Artkive, Chatbooks) require you to gather everything at the end. DandyLine's content is already organized because it was planted with intention. This feature requires: vault content filtering by seed type, collage layout algorithm or template, digital output design, optional print-to-book upsell. A premium output feature that drives both upgrades and emotional purchase decisions. Added 04.22.26.
🧠 Deep Project
📋 Product Decision
● Idea — Needs Development

Quest · family-mvp-build

Core MVP features for families — vault types, sharing, pricing, permissions, surprise vaults, profile system. · 18 cards

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. Needs: full UX flow for Surprise mode, notification design, how countdown displays when sender is hidden.
🧠 Deep Project
🏗️ Build with Claude
● 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. Needs: pricing tiers, shared bar visual, whether multiple people can contribute to the same pool, what happens if the payer stops paying.
🧠 Deep Project
📋 Product Decision
● 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 later. Critical for legacy vaults that outlive their creator. Needs: permission model UX, succession flow, storage ownership on transfer.
📋 Decision Needed
📋 Product Decision
● Idea — Needs Development
21
Vault Visibility & Join Settings — Cross-Vault Privacy Model
Product Privacy All Vaults
Ashley raised a critical question while designing the Roots vault: do visibility and join settings exist for ALL vault types, not just Roots? The current design doesn't address this. Three distinct settings need to be defined and applied across all vault types: (1) Discovery — who can see the vault exists? Options: fully private, visible by name to invited people only, open/searchable. (2) Join access — who can become a member? Options: open, request-to-join (owner approval required), invite-only. (3) Contribution rules — who can plant seeds? (Mostly relevant for Grove + Roots, but applies to any shared vault.) For Roots these are especially rich because of the geofence dimension — discoverable-but-invite-only is a unique mode where the vault appears when you arrive, but you must request permission to join. Needs: decision on whether all 3 settings apply to all vault types or only select ones, UI for the settings panel, and how this surfaces in the vault chooser flow. Added 04.09.26.
📋 Decision Needed
📋 Product Decision
✅ RESOLVED April 21, 2026 — Planter chooses at creation time. Three options: Invite-only (DEFAULT), Link-based, Searchable. Opt-into openness, never opt-out. Schema: visibility enum on vaults table (invite_only | link | searchable). See QUESTIONS-FROM-ASHLEY.md Section F2.
22
Jar Description Field & Default Text — What You See When You Open a Jar
Product UX Copy All Vaults
When a user opens or selects a jar, there should be a brief description visible — not just the title, contributor count, and seed count. The owner can write a custom description when creating the jar, but if they don't, a default kicks in. Defaults should feel alive, not generic. Options: a single rotating default per vault type, or 2–3 curated variations the system cycles through. Also locked: two copy lines for Roots arrival/join moments — "Plant something true to this place." (arrival notification, before joining) and "This jar holds what this place has held." (invitation or jar open screen). Hard-rule jars (strict GPS enforcement) get firmer copy like "Only what was captured here belongs here." Needs: default description copy written for all 6 vault types, UI placement in the jar view, and settings panel for owner to write/edit custom description when building a jar. Added 04.09.26.
🔨 Build Session
✍️ Copy & Writing
● Idea — Needs UX Copy & Settings Design
24
Vault Type Conversion & Seed Transfer — Changing a Vault After Creation
Product Vault Mechanics UX Flow
A user should be able to change a vault's type after creation — within reason. Real example: a solo parent builds a Personal vault (blue) contributing to it for years, then wants to gift it to their child on their 18th birthday. A Personal vault showing up as the gift feels wrong — it should become a Milestone vault (green). The conversion flow: system prompts "Do you want to transfer your seeds into a different vault type? Here are your options." It then sorts seeds — some may transfer cleanly, some may not comply with the new vault's rules (e.g., hard-location seeds moving to a non-location vault). Seeds that can't transfer are flagged separately. The owner keeps access as the original Gardener after gifting. The recipient (the child) sees a Milestone vault, sees what's already bloomed, sees countdowns for future unlocks. Key rules to define: which vault type conversions are allowed (Personal → Milestone, Personal → Grove, etc.), what triggers a conversion prompt vs. an error, what happens to non-compliant seeds, and whether partial conversion is allowed. The gifting flow is its own mechanic — separate from conversion but often paired with it. Added 04.09.26.
🧠 Deep Project
📋 Product Decision
● Idea — Needs Full Product Logic Definition
25
"Surprise Me Too" Toggle — Self-Locking Seeds & Title/Gardener Visibility
Product Seed Settings UX
Default: a planter can always access their own seeds even when they're scheduled/locked for others. Optional toggle: "Surprise me too" — hides the seed from the planter themselves until it blooms. Use cases: the Grove Hatch Family vault where everyone gets surprised at the same time including the planter; a personal sobriety journey vault where you want to rediscover what you captured. When a seed is self-locked, the planter can still see: the date it was planted, that they planted it, and optionally the title (toggleable). Title visibility and Gardener name visibility should each be separately controllable — default is both visible (builds anticipation), but planter can hide either. Gardener name should always default to visible because it's a point of emotional connection and enticement. Needs: toggle UX design, decision on what metadata is always visible vs. optionally hidden, and whether self-locked seeds can still be recalled (yes — but recalling breaks the surprise). Added 04.09.26.
📋 Decision Needed
📋 Product Decision
● Idea — Needs UX Design & Seed Settings Definition
25
Vault Templates — Starter Archetypes & Inspo Library
Product Onboarding Vault UX
When a new user creates a vault, they shouldn't start from a blank box. Vault Templates are pre-named, pre-configured starting points with a mood, a suggested schedule rule, and example seed ideas built in — so a user instantly understands what kind of vault they're making. Needs: a full library of template archetypes to develop. Starting examples to build upon: (1) The Joke Vault — a Grove or personal vault where everything is set to "Surprise" scheduling. Anyone in the Grove can drop in a funny meme screenshot, a voice memo of Dad's worst dad joke, a typed-out text of something ridiculous a friend said, or a video clip of a chaotic accidental moment. Nobody knows when it blooms. Pure joy. (2) Kids Vault — a parent-curated space for things a child says, does, or becomes. (3) Legacy Vault — messages from someone important, sealed for a future moment. (4) Journey Vault — a shared travel or milestone vault that fills over time and blooms at the end. (5) Future Self Vault — notes, photos, and voice memos to your own future self. Goal: when someone sees these templates at onboarding, they immediately picture themselves using one. Vault Templates are also a marketing asset — each archetype is its own story to tell. Added 04.09.26.
🔨 Build Session
✍️ Copy & Writing
● New Concept — Needs Template Library Built Out
26
Fuzzy & Estimated Bloom Dates — Confirmation Prompts & Default Fallback
Product Milestone Seed Settings
When a planter sets a bloom date far in the future around an event they can't pinpoint exactly (child's graduation, estimated ~2038), they set an approximate date and get prompted later to confirm the exact date as it approaches. Mechanism: set estimated date → system sends periodic reminders as it gets closer → if confirmed, fires on confirmed date → if never confirmed (including if planter has died), fires on the original estimated date. Also: a single Milestone vault can hold seeds across multiple related milestones (high school, college graduation). The vault has a default date but individual seeds can override to their own date within the same vault. Needs: reminder cadence design, UI for updating an estimated date, and how this interacts with posthumous delivery if the planter dies before confirming. Added 04.09.26.
📋 Decision Needed
📋 Product Decision
● Idea — Needs Product & UX Definition
27
Failsafe Delivery Date — What Happens to Seeds With No Scheduled Date
Product All Vaults Legacy
What happens to a seed that never gets a delivery date — especially if the planter dies? Options to evaluate: (1) Mandatory default — planter must set at least a fallback date at creation, even if vague. (2) System-assigned default — DandyLine assigns a default window (e.g., 5 years) if nothing is set. (3) Open default — unscheduled seeds are accessible immediately. (4) Compost default — unscheduled seeds begin composting after X years if never claimed or scheduled. For Legacy specifically: if no date is set and the planter dies, the Legacy Guardian should be prompted to set the delivery date when they activate the legacy — the vault doesn't auto-fire without human confirmation. This connects to the Pressed vs. Compost mechanic (#03) and the fuzzy dates system (#26). Needs: decision on default behavior per vault type, and Guardian activation flow for Legacy. Added 04.09.26.
📋 Decision Needed
📋 Product Decision
● Idea — Needs Product Definition Across All Vault Types
195
Weather Update — Vault Name & Description Change Notifications
UX Notifications Weather Updates Spawned from HW#53
Spawned from HW#53 on April 27, 2026 when the vault settings editability decisions were locked. When a vault admin/owner changes the vault name or description, every member needs a soft signal that something shifted — but it shouldn't disrupt them.

Spec direction: Add to the Weather Update system as a passive in-app notification. NOT a push notification. Styled like a group-chat name change ("Ashley changed the vault name from 'Family Memories' to 'Hatch Family Legacy'"). Engaged users will see it in their feed; others get the signal next time they open the app.

Optional UI flourish — 90-day transition marker: show "(formerly: Old Name)" in parentheses next to the new vault name for ~90 days after a rename, so members aren't disoriented if they haven't been in the app for a while. Soft, contextual, fades on its own. Same idea for description changes — though those probably don't need the parenthetical, just the Weather Update entry.

When this gets built: Pairs with HW#41 (Notification System Design) and any Weather Update spec already in progress. Should be one of the first non-bloom Weather Update entry types defined, since vault renames are likely to happen earlier than other notification types.

What this card needs: Visual mockup of the Weather Update entry · copy template ("X changed the vault name from Y to Z") · decision on whether description changes also get the parenthetical or just the feed entry · timing/decay behavior for the 90-day marker.

Added 2026-04-27.
🌿 Medium Project
📋 UX Spec · Notifications
● Spec direction set — needs visual mockup + copy template before build
27
Download & Export Permissions — By Vault Type
Product Privacy Vault Mechanics
DandyLine's data portability promise means content should always be downloadable — but the rules around who can download what, and when, likely vary by vault type. The core tension: private family vaults feel open and trusting (anyone in the Grove can save content), but community or semi-public vaults may need creator-level controls to feel safe. This is NOT an MVP problem — don't add complexity to the first build. But it needs to be thought through before any community vault feature ships. Starting framework: (1) Personal vault — full download always, it's just yours. (2) Family/Grove vault — open by default, lead gardener can optionally restrict. (3) Community vault — restricted by default, lead gardener can open it. (4) Legacy vault — timed download; content may only become downloadable after the bloom. Key design constraint: this should never hit the user as a wall of settings on upload. Think contextual defaults that feel obvious, not a permission grid. Also consider: screenshots are always possible anyway — so download restrictions are about friction and intent signaling, not true prevention. Note the Snapchat parallel: people save before posting precisely because they don't trust platforms to preserve original quality. DandyLine's download default should always preserve original quality — that's the differentiator. Added 04.09.26.
📋 Decision Needed
📋 Product Decision
● Post-MVP — Needs Design Before Community Vaults Ship
41
Weather Hub & Notification System — Signals, Prompts, Action Buttons
NotificationsResendTwilioAll Vaults
Resend (email) and Twilio (SMS) are in the stack, but there's no design for the notification system itself. What triggers a notification? Who gets one — the planter, the recipient, or both? Notifications to think through: (1) "Your vault is about to bloom — X days away." (2) "A seed has bloomed for you." (3) "Someone planted a seed in your Grove." (4) "Your vault is getting full." (5) "A seed you planted X years ago just bloomed." Each of these needs copy, timing, and a decision about email vs. SMS vs. both. This is a prerequisite for building the bloom delivery pipeline in Step 6 of the build sequence. Added 04.12.26.

Updated 2026-05-02 — Weather Hub umbrella spec (Moleskine intake):

Weather is the in-app surface that surfaces all time-sensitive signals to the Gardener. It REPLACES "daily tasks" and "today's schedule" patterns from generic productivity apps. Each Weather item is a signal plus an action button that navigates the Gardener to the relevant surface.

Signal types (tied to notification types from this same card):
— "Your Seed has bloomed" → goes to Bloom reveal
— "A Seed has been planted for you" → goes to Held in Trust / claim flow
— "You have N Seeds ready to bloom" → goes to bloom queue
— "Your Vault hasn't been tended in [time]" → goes to that Vault
— "Time to contribute to [Grove/Journey]" → goes to contribute flow
— "You have N Seeds in your Seed Packet — ready to plant?" → goes to Seed Packet (HW#201)
— + posthumous variants (HW#54), Vault rename announcements (Weather Update card), On This Day surfacing (HW#140)

Layout — TBD: dashboard, feed, or card-stack are all viable. Plan: "draft three" pass at build time before committing.

Hard NO: "Today's Schedule" framing. Wrong metaphor.

Sister cards feeding Weather: HW#54 (posthumous notification language), the Weather Update — Vault Name & Description card, HW#140 (On This Day + Weather-at-Bloom). These are sub-specs that feed the umbrella Weather Hub.

Connection: notification types and Weather signals are the SAME underlying events — same source, two surfaces (push/SMS for notifications; in-app Weather hub for in-app prompts).
🌱 Deep Work
✍️ Ashley + Claude · Copy + UX design
● Not started — needed before Step 6 of the build
42
Recipient Onboarding — What Happens When a Bloom Arrives for Someone Without an Account?
OnboardingBloom UXCritical Path
If I plant a seed today for my daughter's 18th birthday, she doesn't have a DandyLine account yet — and may not in 18 years. When the bloom arrives, what does she receive? An email with a link? Does she need to create an account to open it? If yes, what's the minimum signup? If no, how does she access it securely without one? This is one of the most emotionally charged moments in the entire product — a person receiving a message from someone they love — and right now it has no design at all. Decide this before building the bloom delivery system. Added 04.12.26.
🌱 Deep Work
🤔 Ashley decides · Claude designs the flow
● Not started — needed before bloom delivery can be built
44
Grove Invite Flow — How Do You Actually Invite Someone to Contribute?
GroveMulti-ContributorUX
Grove vaults are multi-contributor — multiple Gardeners plant seeds into the same vault. But the mechanics of how that works have never been designed. How does the lead Gardener invite contributors? (Email link? QR code?) Does a contributor need a DandyLine account to contribute, or can they submit as a guest? What can a contributor see — just their own seeds, or all seeds? Can the lead Gardener remove a contributor's seed? Can a contributor remove their own seed before it blooms? These decisions directly shape the Grove data model and auth system. Added 04.12.26.
🌱 Deep Work
🤔 Ashley decides · Claude designs the flow
● Not started — needed before Grove can be built
77
Community Garden — Browse & Join Public Vaults
ProductUX
A "Community Garden" where you browse open/public vaults you can join. Shows: title, # contributors, description, general rules, # bloomed seeds, # pending seeds. Ties to Roots ghosted discovery (C1-C5) but broader — could include Journey vaults and other public types. Ashley referenced ux-mockup-reference.html jar browser visual as rough starting point. Needs: discovery mechanism, join flow, role assignment on join. See also C4 vault roles/ownership notes.
🧠 Deep Project
📋 Product Decision
● Idea — Needs Development
99
Sharing as Contribution Motivator — Document & Design the Insight
Strategy PMF Growth Retention
Insight surfaced in competitive research: for platforms like FamilyAlbum, sharing a photo motivates more contributions. The act of contributing (seeing others respond, seeing the shared space fill up) creates its own flywheel. DandyLine is NOT social — but this dynamic still applies. When a Grove vault gets a new seed, contributors see "3 more seeds have been planted" without seeing what's inside. The unsealed vault is growing visibly. That's a contribution motivator that doesn't break privacy. Design principle to formalize: visible growth signals should show QUANTITY but not CONTENT before bloom. "Your vault has 7 seeds and counting" creates anticipation and motivates others to add more. This applies to: Grove vault contribution prompts, Journey vault progress states (a progress bar from 0 → 12 monthly seeds), and the "Something is growing for you" recipient tease (HW#59). This isn't a separate feature — it's a design principle that needs to be formalized in the UX system and explicitly documented in the brand guide as a distinction from social media mechanics. "We show growth, not reactions." Needs: design principle documented, specific UX applications across vault types, copy guidelines for "vault is growing" language. Added 04.22.26.
🔨 Build Session
✍️ Copy & Writing
● Idea — Needs Development
104
Pricing Model Final Decision — Lock Subscription Price & À La Carte Numbers (Priority 3)
Business Pricing Revenue Workbook Priority
Hybrid model (subscription + à la carte) is the chosen direction. What's still open is the exact numbers. Three test scenarios to work through before locking prices:

Test Scenario 1 — Wedding Organizer: You're organizing a wedding vault with 4 seeds (1-week, 1-year, 5-year, 10-year bloom dates). Would you pay $9.99 to unlock multi-seed vault functionality for this event? Or is $9.99 too much / not enough?

Test Scenario 2 — Guest Contributor: You're a guest invited to a wedding vault. The organizer paid already. On bloom day, you get an email with a blurred preview. Would you download the app to see the full reveal? What would make you say yes vs. no?

Prices to Confirm (currently at these numbers — are they right?):
— Add a seed to a vault (à la carte): $2.99 — or should it be $1.99?
— Unlock vault for 5 seeds: $9.99 — or should it be $19.99 for the premium event use case?
— Export vault as PDF: $4.99 — feels right, but confirm
— Monthly subscription: TBD — $4.99/mo? $9.99/mo? $0.99/mo (ultra-low barrier)?

Freemium Conversion Target: What % of free users should convert to paid within 90 days? This sets the growth model expectations for investors. Pick a number to aim for — even if it's a guess. (Industry benchmarks: 2-5% for consumer apps; 10-20% for high-intent tools.)

Note: see HW#80 (Revenue Model) for the broader monetization strategy context. This card is specifically about locking the numbers.
📋 Decision Needed
💰 Business & Monetization
● Decision Pending — Numbers TBD · Hybrid model chosen, prices not locked
📎 Merged In · From HW#051 (was: "Pricing Model Spec — What's Actually Free vs. Paid, and What Are the Hard Limits?")

Merge reason · Pricing Model Spec is the predecessor of Pricing Model Final Decision (same topic, different stage). Original card consolidated 2026-04-25.

Description: The freemium model is in the strategy notes but has never been fully spec'd. Before building, you need to know: What does the free tier include? (1 vault? 3 vaults? 500MB storage?) What triggers an upgrade prompt — and what does it say? What does the paid tier cost per month, and what does it unlock? What happens to someone's vaults if they stop paying — are their seeds held safely or do they lose access? These decisions affect the data model, the UI, the onboarding flow, and the investor story. A vague "freemium with storage upgrades" is not enough to build against. Write out the exact tier table before starting the build. Added 04.12.26.

Original Status: ● Not started — needed before MVP build begins

📌 Sub-section added 2026-05-02 — Free-tier storage cap (Josh consult)

The free-tier storage cap is unset and gates the rest of the pricing tiers. Asking Josh in dandyline-app/QUESTIONS-FROM-ASHLEY.md Section M (added 2026-05-02): cap size recommendation, cost framing per cap, hot vs cold storage angle for sealed Vaults. Don't lock pricing tiers until Josh weighs in. Linked: HW#184 (Drifting timing — also depends on storage cost economics).

#129 — Financial Model & Funding Overview · MVP Cost + Phase 1/2 Split

Parked Ashley Medium Quest #4 · Family MVP

The full financial model: pricing assumptions ($69/yr premium, $120/yr family), conversion rates, storage math, operating cost estimates, profitability trajectory, and the two-phase build split (Family MVP at ~$0 cost → Public Scale requires pre-seed). Stack note: Supabase references in the original have been updated to the April 12 Cloudflare-only decision.

What's Next
  • Pair with HW#109 (Four Growth Loops) + any MVP-build cards when revisiting the economics. Update pricing numbers after Phase 1 beta data lands.
Highlights
  • Pre-seed target: $750K–$1.2M, 18-month runway, used for Phase 2 public build + validation
  • Phase 1 (Family MVP) cost: ~$0 build, $0–$50/month running, functional in under 30 days
  • Pricing: Premium $69/yr · Family plan $120/yr · Year 1 conversion 3% → Year 5 conversion 12%
  • Margin profile: 60–70% gross margin possible Year 5+ with sealed-majority content
  • ⚠️ Stack update: Original referenced Supabase. Superseded by Apr 12, 2026 Cloudflare-only decision (Pages + D1 + R2 + Workers + Cron + Resend). No Supabase.
Working Pages
Notes — Full cleaned prose (Supabase refs updated)

Financial Model & Funding Overview · Confidential · March 2026

These are directional startup assumptions designed to support build, funding, and pacing decisions — not guarantees. Numbers are intended to help founders make build, funding, and pacing decisions.

Key Assumptions

  • Premium subscription: $69/year
  • Family plan: $120/year
  • Conversion rates — Year 1: 3% · Year 3: 8% · Year 5: 12%
  • Average storage — Free user: 1.5 GB · Paid user: 30 GB
  • Estimated storage cost: ~$0.50 per GB per year (blended hot/warm/cold)

Other Operating Cost Estimates

  • Engineering team — Year 1: $600K · Year 3: $1.8M · Year 5: $3.5M
  • Trust & moderation team — Year 3+: $500K → $1.2M
  • Marketing / growth — 10–25% of revenue reinvestment
  • Legal / compliance — $100K–$300K annually at scale
  • AI compute / recap generation — 5–10% of storage cost initially

Profitability Trajectory

Likely unprofitable Years 1–2. Break-even potential Year 3–4 depending on growth efficiency. Strong profitability possible Year 5+ with 60–70% gross margin.

Strategic Financial Insights

  • Storage cost is manageable if most content stays sealed
  • Conversion improvement has massive revenue impact
  • Family plans dramatically increase lifetime value
  • Emotional retention reduces marketing cost over time
  • Legacy plans create high-margin revenue spikes

MVP Build Cost Estimates — Updated April 9, 2026

Two-phase build model. Phase 1 (family/personal MVP) is built with AI assistance at near-zero cost. Phase 2 (public scale) is where pre-seed funding becomes necessary.

Phase 1 — Family MVP (PWA, built with Claude)

Build cost: ~$0. Stack (updated Apr 12): Cloudflare Pages (already live) + Cloudflare D1 + Cloudflare R2 + Cloudflare Workers + Cron Triggers + Resend. Timeline: 14–16 focused hours across sessions, targeting functional in under 30 days. Monthly running cost: $0–$50/month. Annual cost at family/100-user scale: $0–$600/year. This phase does not require pre-seed funding. It generates the traction (real users, real usage data) that makes fundraising from strength possible.

Phase 2 — Public Scale (requires pre-seed)

Previous estimate of $120K–$300K applied to Phase 2 at scale — hiring engineering staff, hardening infrastructure, legal/COPPA compliance, and a full App Store build. This remains accurate for the public launch phase. The key change: Phase 1 now happens first, before any of this spend, reducing risk and improving fundraising position significantly.

Pre-Seed Fundraising Ask

Round: Pre-Seed. Target: $750K–$1.2M. Runway: 18 months. Primary use: MVP build + validation + category launch.

Use of Funds Breakdown

  • Engineering (core MVP build): ~50–60%
  • Design, UX & branding: ~15%
  • Infrastructure, legal, compliance: ~10–15%
  • Early marketing & community building: ~10%
  • Operations & founder salary buffer: ~10%

What Success Looks Like at 18 Months

  • MVP launched and validated with 100–300 beta users
  • Emotional retention signals confirmed (users returning before first bloom)
  • Willingness-to-pay validated
  • Category narrative established
  • Seed-round readiness with meaningful data

Cleanup applied: Original referenced Supabase in Phase 1 stack. Updated to current Cloudflare-only stack per Apr 12, 2026 decision.

History
  • Migrated from biz-dev-notes-business.html (lines ~135-204). Supabase reference updated to Cloudflare-only stack.

Quest · guardian-seed-key-system

Guardians, Seed Keys, trust circles, posthumous delivery, claim flows. The trust and delivery infrastructure. · 9 cards

52
Seed Key & Guardian System — Full Product Spec ✅ DESIGNED
ProductSeed KeysGuardianLegacyAll Vaults
DESIGNED April 12, 2026. Full spec in product-seed-keys.html. Covers: Seed Key generation and sharing, four recipient states (Active, Invited, Held in Trust, Open Claim), Guardian assignment and acceptance flow, content-blind guardianship, planter-set passphrases, posthumous delivery with death verification, multi-recipient vault logic, and schema implications for D1. Josh cliff notes in JOSH-UPDATE-APRIL-12.md. Remaining open questions documented in Section 11 of the product page.
🧠 Deep Project
📋 Ashley + Claude · Product Design
● ✅ Designed — product page live. Schema additions flagged for Josh. Open questions remain.
55
Guardian Succession — What Happens If the Guardian Also Dies?
ProductGuardianLegacyLegal
A vault's planter dies. The Guardian takes over. But what if the Guardian also dies — or becomes incapacitated? Does the vault persist and wait indefinitely? Is there a secondary Guardian (chain of succession)? Does the system eventually release the content after a long enough period? This is a low-frequency but high-stakes edge case. For MVP, "vault persists indefinitely" may be the right answer. At scale, a secondary Guardian option or an estate-level release mechanism may be needed. Related to HW#18 (digital legacy planning). Added 04.12.26.
💜 Decision
🤔 Ashley decides · affects Guardian system architecture
● Not started — needed before public Legacy vault launch
57
The Dandelion Drop — Event-Based Open Claim Vaults
ProductSeed KeysRevenuePartnerships
Open Claim Seed Keys could power event-based experiences. Wedding planners print QR-code Seed Keys on place cards — 150 guests scan, plant seeds (video, photo, note), couple's vault fills in real time, blooms on the anniversary. Applies to corporate retreats, graduation ceremonies, baby showers. Revenue opportunity: per-event pricing or bulk Seed Key packs. Partnership channel: event planners, wedding coordinators, corporate retreat organizers. Needs pricing model, bulk key generation UX, and event-mode vault settings. Added 04.12.26.
🔨 Build Session
✍️ Ashley + Claude · Product + Business Model
● Not started — revenue opportunity to explore
61
Guardian Network — Trust Circles (Multi-Guardian)
ProductGuardianSecurityTrust
Instead of a single Guardian, allow a trust circle — 2-3 people who collectively manage delivery if the planter passes. No single person bears the full weight. Adds redundancy (what if the one Guardian also dies?). Could use voting: 2 of 3 Guardians agree → action proceeds. Connects to Shamir's Secret Sharing concept already in open questions. Needs: trust circle UX, voting mechanics, what happens on disagreement, minimum circle size. Added 04.12.26.
🔨 Build Session
✍️ Ashley + Claude · Product + Security Architecture
● Not started — scale feature, design now
64
Orphaned Guardian Recovery — Broken Trust Chain
ProductGuardianEdge Cases
Guardian dies before planter. Or Guardian goes inactive — deleted account, lost phone, moved countries. Trust chain is broken. Connects to HW#55 (Guardian Succession) but needs a concrete fallback design. If Guardian unreachable for X months → system prompts planter to reassign. If planter also gone → vault enters 'community trust' state where DandyLine itself becomes temporary custodian (content-blind). Needs: inactivity detection, reassignment flow, community trust rules, legal framework for platform-as-custodian. Added 04.12.26.
🔨 Build Session
✍️ Ashley + Claude · Product + Legal
● Not started — needed before public Guardian launch
81
Default Guardian — Profile-Level Setting & "My Guardianships" View
ProductUXSpawned from Planting Flow
Born out of the April 18 planting-flow session. Add a profile-level setting called "My Default Guardian" (or similar) that auto-fills as the suggested Guardian every time a Gardener plants a new vault. Must be editable on the vault itself so any single vault can override the default. Includes a sibling "My Guardianships" view showing (a) vaults I've been named Guardian for, (b) vaults I'd inherit via Grove/Roots default, (c) guardianship acceptance status, (d) ability to decline. Design considerations: how is the default set? (empty by default — first time a user assigns a Guardian, prompt "make this your default?"); how is it changed? (profile settings + "change default" nudge on every 5th vault); can a user have no default? (yes — opt-in, not forced). This is a RETENTION feature — it gives returning users a reason to maintain their account so their guardianship chain stays intact.
🧩 Medium Build
🛠 Build Task
● Idea — Needs Development
82
Super Lock — Permanent Bloom Date Mechanic
ProductUXSpawned from Planting Flow
Born out of the April 18 planting-flow session. Super Lock is a one-way toggle during planting that makes the bloom date completely immovable — not by the Planter, not by a Guardian, not by a Premium subscriber, not by anyone. Used for sacred/ritual dates: "bloom on her 18th birthday," "bloom the day he gets married," "bloom on our 50th anniversary." UX needs: (1) friction-heavy confirmation — this cannot be undone; (2) clear visual treatment on the vault card ("🔒 Super Locked — {date}") so nobody forgets it's permanent; (3) recipient-facing notice "this date is immovable — it was sealed by {planter} at planting time"; (4) Guardian-facing notice on the vault dashboard explaining why the date can't be edited even if they'd otherwise have authority; (5) edge-case handling — if the Planter Super-Locks then dies, Guardian still can't move the date (which is the point). This is the feature that lets Gardeners trust the system with their most sacred commitments.
🧩 Medium Build
🛠 Build Task
● Idea — Needs Development
📎 Merged In · From HW#089 (was: "Super Lock Behavior for Date TBD Vaults")

Merge reason · Super Lock Date TBD edge case folds into the main Super Lock card. Original card consolidated 2026-04-25.

Description: Raised April 21 during messaging decisions session. Super Lock makes a bloom date immovable forever — great for sacred fixed dates ("bloom on her 18th birthday"). But for "Date TBD" vaults (like a wedding day vault planted when Baby Jaden is born), Super Lock should be unavailable or blocked with a clear explanation: you can't permanently lock a date that hasn't been set yet. UX decision needed: (1) Should Super Lock be quietly hidden/disabled in the planting flow until a specific date is entered? (2) Or should it be shown but greyed out with a tooltip — "Set a bloom date first"? (3) What happens if a Planter sets a date, Super Locks it, then tries to change to Date TBD? Likely block: once Super Locked, the date field itself becomes read-only. Spec lives adjacent to HW#82 (Super Lock mechanic). Resolve before Super Lock UX is built.

Original Status: ● Open

84
Guardian Replacement UX — Subtle Notify Flow
UXSpawned from Planting Flow
Born out of the April 18 planting-flow session. When a Planter replaces a Guardian (e.g., divorced husband swapped for sister), the system must notify BOTH the outgoing and incoming Guardian — but the notification tone matters. Decision: subtle and dignified, not dramatic. Design: (1) outgoing Guardian gets an in-app + email notice "{planter} has updated guardianship for their vault '{vault-name}.' You are no longer named as Guardian. No action needed." — NO "why" field, NO apology text, NO rejection framing; (2) incoming Guardian gets standard guardianship acceptance flow; (3) the vault's Guardian changelog (visible only to the Planter) logs the swap with timestamp; (4) no public-facing notice anywhere — guardianship changes are private between Planter and the Guardians involved. Stress-test edge cases: what if outgoing Guardian had already accepted and was holding seeds in trust? (Seeds revert to Planter's vault control, Guardian loses access cleanly.) What if outgoing Guardian is dead? (Swap silently — no notification attempt.)
🧩 Medium Build
🛠 Build Task
● Idea — Needs Development
85
Grove Hybrid Guardian Model — Vault Guardian + Contributor Guardian
ProductGroveSpawned from Planting Flow
Born out of the April 18 planting-flow session. Groves (shared vaults with multiple Gardeners) need two guardianship layers because personal ownership must survive inside a shared container. (1) VAULT GUARDIAN — structural/admin role: can the vault itself continue if the owning Gardener dies or account-deletes? Manages membership, lifecycle, archive. Defaults to the Grove creator; Grove members can vote to replace. (2) CONTRIBUTOR GUARDIAN — per-person role attached to each member's own planted seeds inside the Grove. If Grandma Memaw contributes 40 seeds to a family Grove and passes away, HER seeds respect HER Contributor Guardian (a daughter she named), not the Vault Guardian. Build scope: data model (two FK columns on seed records — vault_guardian, contributor_guardian); UX for setting your Contributor Guardian when joining a Grove; dashboard view showing "seeds I've planted + who guards them"; vault-level dashboard showing both layers. Stress-test: Grove Vault Guardian dies AND Contributor Guardian for a deceased contributor dies — is the Grove ever orphaned? (Falls into the 3-Layer Ladder — nudges, then Held in Trust, then Sunset.)
🧠 Deep Project
📋 Product Decision
● Idea — Needs Development

Quest · sound-design

Audio cues, swooshes, whispers, chimes, pops. Subtle sound design that gives the app its texture. · 1 cards

08
Develop Sounds UX — Swooshes, Whispers, Chimes, Pops, etc.
Product Audio UX Sound Design
Define the full sonic identity of DandyLine — what does planting a seed sound like? What does a vault opening sound like? Explore a palette of micro-interactions: swooshes (navigation/transitions), whispers (intimate/personal moments), chimes (bloom delivery, celebration), pops (taps, confirmations). Needs: sound direction/mood board, trigger mapping across key moments, and decision on opt-in vs. ambient-on approach.
🧠 Deep Project
🎨 Visual / UX Design
● Idea — Needs Development

Quest · journey-vault-mechanics

Journey vault: temporal community, wayfinding, Roots, monthly prompts. Time as the participation pattern. · 9 cards

09
Roots Map — Visual & UX Design
Product UX Design Roots
What does the Roots map actually look like? Visual direction already set: organic and calm, not utilitarian — soft terrain textures, glowing underground root systems, floating seed markers, warm light pulses for emotional intensity. Needs: full map UI design, how locations are represented as pins vs. clusters, zoom behavior, seed density at a single location, and the entry point into the map from the main nav.
🧠 Deep Project
🎨 Visual / UX Design
● Idea — Needs Design Sprint
11
Sprouted Here vs. Rooted Here — Popup Card Visual Treatment
Product Brand Roots
Location seeds have two sub-states that need subtle visual distinction on the popup card. "Sprouted Here" = GPS auto-captured, memory was born at this place (the wormhole experience). "Rooted Here" = manually assigned, memory was intentionally dedicated to this place. Both remain purple. Needs: icon variation exploration (root-anchor vs. dedicated-pin feel), sub-label placement on the popup card, and a subtle info icon or hover tooltip that explains the difference without interrupting the emotional moment.
📋 Decision Needed
🎨 Visual / UX Design
● Idea — Needs Design Exploration
🔥
Place Vault — Community Jar with Geofence Arrival & Jar-Level Location Rules
Product Roots / Geolocation Vault Mechanics Community
A new vault type (or major Roots mode): a community jar anchored to a physical location. When someone arrives at the location, a geofence notification fires — "Our roots run deep here. Want to garden?" — and they can join and contribute. All contributors can see what others planted (some open, some time-locked). Every seed shows provenance: taken here vs. tagged here vs. manually placed. Key distinction from #06 (Location-Locked): that vault can't be OPENED until you arrive. This vault can't be CONTRIBUTED TO unless you're there — or the creator allows otherwise. Jar-level location rules: creator chooses soft mode (anyone can contribute from anywhere) vs. hard mode (GPS must be live, only media captured at this exact location allowed — no imports, no uploads from other places). Hard mode creates a "window in time" — the jar feels like a living record of a place. Needs: new vault type definition (or Roots sub-mode), arrival notification UX, join-the-jar flow, contribution rule settings, provenance labeling on seeds, and how this integrates with the Roots Map (#09). Added 04.09.26.
● New Idea — Major Roots Feature — Needs Full Product Definition
28
Journey Delivery Formula — Trickle Pacing, Notification Copy & Curation Algorithm
Product Journey Notifications
Journey seeds trickle in at randomized intervals after someone hits a milestone — not all at once. Creates the feeling that someone just thought of you in real time, even if the seed was planted years ago. Time as the medium applied to delivery itself. Low seed volume is invisible — sparse pools feel as meaningful as full ones. Re-engagement is earned. Needs: max seeds per milestone (suggested 3–5), delivery window (suggested 1–4 weeks), spacing logic (randomized, not fixed schedule), curation logic (tone variety, media type variety), and notification copy that makes each arrival feel handpicked — not algorithmic. The notification copy is especially high-value creative work. Added 04.09.26.
📋 Decision Needed
📋 Product Decision
● Needs Product Formula & Notification Copy Definition
33
Journey Vault Community Feed — Soft Moderation & Sentiment Signal
Product Journey Community
Journey Vaults expose users to a community pool — the algorithm surfaces others at the same milestone (e.g., both on Day 30 of sobriety). Problem: what happens when surfaced content clearly doesn't belong, or is upsetting? The solution is not upvoting/downvoting (too social) or formal reporting (too punitive). Instead: a private, lightweight "soft sentiment signal" — something like "this didn't feel right" or "unrecommend" — that the creator never sees, generates no public count, and quietly feeds the algorithm. One flag = personal filter (never show me this again). Enough flags = pool-wide de-weight (content fades from circulation without anyone being notified). Seeds rotate in a growing pool — there are no view counts, no validation metrics. The act of sharing is the thing, not the reception of it. Key design questions: what does the gesture look like (long-press? swipe? single tap?), whether to offer soft category options or a single signal, how the algorithm handles personal vs. pool-wide flags, and how this interacts with hard vault rules set by the Journey creator. Migrated from coaching dashboard 04.09.26.
🧠 Deep Project
🏗️ Build with Claude
● Needs UX design — gesture, algorithm logic, and vault rule integration
59
The Waiting Room — Pre-Bloom Anticipation UX
ProductUXRetentionEngagement
The emotional space between planting and blooming is currently invisible to recipients. What if recipients with pending vaults could see a 'Something is growing for you' indicator? Not what's inside. Not when it blooms. Just that something exists. Like a wrapped present under the tree. Drives retention (people check back), creates anticipation, and makes the bloom moment even more powerful. Needs UX design: where does this show up? How much do you reveal? What if the planter wants it to be completely secret? Added 04.12.26.
🔨 Build Session
✍️ Ashley + Claude · UX Design
● Not started — high-impact engagement feature
93
Journey Vault Template — Monthly Prompted Upload Habit
Strategy PMF Product Journey Vault
The Short Years built a business on one habit: plant one photo per week, get a beautiful book at the end of the year. DandyLine can do this better. A "Monthly Moments" Journey Vault template that sends a monthly prompt ("What's the most surprising thing that happened this month?") and nudges one photo or voice upload in response. At the end of 12 months, the vault blooms — not as a generic photo dump, but as a curated timeline of intentional moments. Key differences from The Short Years: cross-media (photos + voice + text), no printing required (but could trigger print upsell), family-shareable, and the bloom is a revelation rather than a product delivery. Needs: prompt library (12 monthly questions), notification UX for the monthly nudge, end-of-year bloom experience design, optional print-to-book upsell trigger. This is the "habit formation" template that solves the empty-vault problem — users who don't know what to plant now have a guided container. Added 04.22.26.
🔨 Build Session
📋 Product Decision
● Idea — Needs Development
98
Baby Book Journey Vault — Milestone Template (Kept Competitor Play)
Strategy PMF Product Milestone Vault
Kept Collection sells a single $59 book that spans birth to age 18 — a "baby book for parents who never started one." It's purely physical, no app, no digital companion. DandyLine's native answer to this is a Milestone vault template called "Baby Book" that does the same job digitally — pre-seeded with milestone bloom dates (first word, first steps, first day of school, first birthday, 5th birthday, 13th birthday, 18th birthday) and a library of prompted seed ideas for each milestone. The emotional hook is the same: "you always meant to document this, now you finally have a place." But DandyLine's version is never empty because you start adding to it the day you create it, seeds bloom to the child when they're old enough, and the whole lifecycle lives in one place. The Kept differentiator was "beautiful analog permanence." DandyLine's response: premium digital presentation + optional physical book export at any milestone. Needs: Milestone vault template with pre-set bloom dates, prompt library per milestone, and a moment-by-moment growth map that parents can visualize. Added 04.22.26.
🔨 Build Session
📋 Product Decision
● Idea — Needs Development
JV
Journey — How does "temporal community" actually work?
🔥 HotJourneyProduct
When someone hits Day 30 of sobriety, how many seeds do they receive? From whom? Curated or random? Can they receive multiple? How does DandyLine verify a Journey milestone without violating privacy? If self-reported, what prevents abuse? Does the honor system work here?
● Most novel feature — needs defined interaction model before Journey can be built

Quest · pmf-concierge-testing

Real-user testing, wedding pilot, financial projections, growth-loop validation. · 4 cards

40
PMF Pre-MVP: Concierge Testing with 3–5 Real People
PMF Signal Strategy Priority
PMF score is stuck at 3 because signups are intent, not behavior. You can close some of that gap before a full product exists using "concierge MVP" testing — manually simulating the DandyLine experience for a small number of real people. The goal is to find 3–5 real users (not friends being nice — actual potential users who have the problem) and walk them through the experience one-on-one. Start by identifying the specific moment in each person's life when they feel the problem most sharply. Then design a manual version of the plant-a-seed flow tailored to that moment — even if it's just you sending a message at the right time. The PMF signal you're looking for: are they upset when it doesn't work, or relieved that it did? One real person saying "I would have paid for that" is worth more than 100 waitlist signups. This could move PMF from 3 → 4 or 5 before any code ships, and gives you a real story to tell investors. Started as a coaching session (HW: Improve Market Fit Score) — pick up there for prompts and framework. Added 04.12.26.
🤝 Needs Outside Help
🤝 Ashley + Real People
● Strategy thread started — needs execution with real users
49
Wedding Vault Pilot — Concrete Execution Plan for 3 Couples
PMFGTMPilots
The coaching advice is clear: find 3 couples getting married in the next 90 days, offer them a free vault, and document the experience. This is the fastest path to a real traction data point for investors and to moving PMF from 3 → 5. But "find 3 couples" is not a plan. A plan looks like: (1) Who specifically will Ashley reach out to? (2) What does she offer them? (3) What's the ask in return — feedback call? Permission to share their story? (4) What does she actually give them right now — a prototype, a manual experience, a promise? (5) How does she document it? This session is where that plan gets written. Added 04.12.26.
🤝 Needs Outside Help
🤝 Ashley + Real People · Claude builds the offer doc
● Strategy exists — execution plan is missing

#109 — Four Growth Loops: From Shared Seeds to Public Inspiration

Spec-Ready Ashley High Quest #8 · PMF Concierge

Four core growth mechanics, ranging from immediate viral coefficient (Shared Seeds) through event-based scaling (Event-Based Vaults) to trust-driven adoption (Founder Journey Vault, Public Vault Inspiration). Loop 1 identified as strongest.

What's Next
  • Pick top 2 loops to instrument in the Phase 1 PMF test (Loop 1 + one other)
  • Design onboarding so Loop 1 (Shared Seeds) fires on user's first planted seed
Highlights
  • Strongest loop: Loop 1 — Shared Seeds (high viral coefficient, immediate timeline)
  • Slow-burn loop: Loop 2 — Event-Based Vaults (very high viral but years-long timeline)
  • Depends on: Quest #8 PMF test design; Quest #11 Planting Flow Design (share mechanic)
  • References: Drafted April 18 in biz-dev-notes-strategy.html (pre-retirement)
Working Pages
Notes — Full cleaned prose (April 18, 2026)

Loop 1: Shared Seeds — STRONGEST

User plants a Seed → addresses it to a friend → Friend gets notification: "You've been added to a vault" → Friend must download app to see their Seed → Friend explores vault, plants their own.

Viral coefficient: High (each Seed can invite 1–10 people). Timeline: Immediate.

Loop 2: Event-Based Vaults

Wedding Gardener creates vault → Invites 20 guests → Each guest downloads app to contribute → 20 bloom notifications over 2 years → Guests create personal vaults.

Viral coefficient: Very high (1 event = 20+ downloads). Timeline: Slow (vaults bloom over years).

Loop 3: Founder Journey Vault

New user sees DandyLine journey vault → Feels inspired (founder is vulnerable, real) → Trusts platform (founder is using it) → Creates their own vault.

Viral coefficient: Medium (emotional trust, not explicit sharing). Timeline: Day 1.

Loop 4: Public Vault Inspiration

User browses public vaults (wedding, birth, personal journey examples) → Gets inspired by use case → Creates their own vault with same theme → Invites friends.

Viral coefficient: Medium. Timeline: Week 1–2.

Cleanup applied: No celestial. No military. No Supabase.

History
  • Migrated as gem #3 from biz-dev-notes-strategy.html (drafted April 18).

#130 — Financial Projections · 5-Year Planning Model

Parked Ashley Low Quest #8 · PMF Testing

The 5-year user-growth and revenue projection model — directional startup assumptions for planning only. Year 1: 50k users / $103k revenue → Year 5: 3M users / $24.8M revenue. Paired storage cost projection shows the business is sustainable if most content stays sealed.

What's Next
  • Low priority — reference doc for investor conversations only. Numbers get re-forecast after Phase 1 beta retention data lands.
Highlights
  • User growth curve: 50k Y1 → 200k Y2 → 800k Y3 → 1.8M Y4 → 3M Y5
  • Revenue curve: $103k Y1 → $690k Y2 → $4.4M Y3 → $12.4M Y4 → $24.8M Y5
  • Storage cost scaling: $60k Y1 → $5.8M Y5 (manageable because most content stays sealed)
  • References: Source was biz-dev-notes-business.html (retiring Apr 22, 2026)
Working Pages
Notes — Full projections

Purpose

Directional startup assumptions. Numbers help founders make build, funding, and pacing decisions. Not guarantees.

User Growth Scenarios

Year 1: 50,000 users · Year 2: 200,000 users · Year 3: 800,000 users · Year 4: 1.8M users · Year 5: 3M users.

Revenue Projection

  • Year 1: 50k users × 3% paid = 1,500 paid users · Revenue ≈ $103,500
  • Year 2: 200k users × 5% paid = 10,000 paid users · Revenue ≈ $690,000
  • Year 3: 800k users × 8% paid = 64,000 paid users · Revenue ≈ $4.4M
  • Year 4: 1.8M users × 10% paid = 180,000 paid users · Revenue ≈ $12.4M
  • Year 5: 3M users × 12% paid = 360,000 paid users · Revenue ≈ $24.8M

Storage Cost Projection

Year 1: ~$60k · Year 2: ~$220k · Year 3: ~$1.2M · Year 4: ~$3.1M · Year 5: ~$5.8M.

Profitability Trajectory

Likely unprofitable Years 1–2. Break-even potential Year 3–4 depending on growth efficiency. Strong profitability possible Year 5+ with 60–70% gross margin.

Strategic Financial Insights

  • Storage cost is manageable if most content stays sealed.
  • Conversion improvement has massive revenue impact.
  • Family plans dramatically increase lifetime value.
  • Emotional retention reduces marketing cost over time.
  • Legacy plans create high-margin revenue spikes.
History
  • Migrated from biz-dev-notes-business.html (lines ~210-308) before notes-page retirement.

Quest · military-families-partnership

Military families go-to-market — deployed families, deployment-aware seeds, partnerships. · 1 cards

30
Military Families Campaign — Deployed & At-Home Audiences
Marketing Campaign Target Audience
Two complementary use cases that tell a powerful, specific story — worth developing as a targeted campaign or landing page, not a core brand narrative. **Direction 1 — The Deployed Gardener (Outbound):** A service member preparing to ship out plants a vault of seeds before they leave — scheduled to bloom on birthdays, holidays, first days of school, milestones. They may not have reliable internet access while deployed, but the seeds are already planted and will bloom on schedule regardless. The dandelion framing writes itself: you blow the seeds before the wind carries you away, and they land when they're meant to. Message to the family: I was here. I thought of you. I planned for this moment even when I couldn't be in it. **Direction 2 — The Family at Home (Inbound):** The family preserving the life happening while their person is away — capturing the moments their loved one is missing — so when they return, there's a vault of everything they missed, ready to bloom all at once or over time. A "here's what you came home to" experience. **The dandelion hook:** The dandelion is actually the official flower of military children — children raised to bloom wherever the wind carries them. This can be a marketing hook for this specific audience without needing to be the central brand story for everyone. **Potential partners:** USAA, Blue Star Families, Military OneSource, National Military Family Association. **What needs developing:** A campaign concept (which direction leads, or do both?), a landing page story, a specific vault template ("Deployment Vault"), and a pitch to at least one military-adjacent organization. Added 04.09.26. **Brand-sweep note (2026-05-02):** The "official flower of military children" reference was removed from biz-mktg-ad-ideas.html line 277 (the Ad Philosophy section — brand-narrative territory) and reframed as the dandelion-experience ("a flower you find without looking, a wish you make in a single breath, a seed that floats forward"). **The principle (Ashley clarified 2026-05-02):** Military-children / "dandelion people" / "carry your roots with you" language is *welcome inside campaign creative aimed at those specific audiences* — military families, immigrants, diaspora communities. It is *not welcome in brand-narrative material* (why-dandelion philosophy, brand ethos, founder story, ad-philosophy intros) where it would imply the metaphor describes everyone. **Reference uses that are correct (don't sweep):** The "Audiences" section of biz-mktg-ad-ideas.html (lines ~996-1000, "Long-Distance Families" card with "The original dandelion people") is a *correct* use of this language — it's audience targeting, not brand identity. **The partnership opportunity is preserved here** as a campaign-specific GTM angle — exactly as Ashley framed it: pitching DandyLine as a product for military families to preserve and schedule memories when they're unavailable. Develop the campaign here; do not reintroduce military-children language into brand-narrative files.
🧠 Deep Project
📣 Marketing & Growth
● Idea — Needs Development

Quest · vault-type-deep-dives

Per-vault-type definition: Personal, Grove, Milestone, Legacy, Journey, Roots, Pressed vs Compost. · 8 cards

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. Emotional stakes: the bloom is something you could lose. Needs: compost window duration (~1yr free?), decay mechanics, "Compost Soon" filter UX, whether sender knows the outcome, storage tier integration.
📋 Decision Needed
🎨 Visual / UX Design
● Core concept documented — Needs UX flow design
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 (which are one seed inside an otherwise-accessible vault). Needs: GPS UX, sealed jar visual treatment, re-lock mechanics, arrival notification design.
🧠 Deep Project
🏗️ Build with Claude
● Idea — Needs Development
14
Buy a Jar — Permanent Preservation Model & Vault Compost Notification
Product Monetization Vault Mechanics
"Buy a jar" = purchase a vault that permanently preserves everything inside it, no subscription required. Ideal for Legacy vaults and milestone collections. Also giftable — a grandparent could buy a preserved jar for a grandchild. Paired idea: vault compost notification — when a vault's payer stops paying, all members get notified that seeds are at risk, can see which seeds are already pressed by someone vs. unclaimed, and anyone can rescue an at-risk seed into their own storage. Needs: one-time vs. fixed-term purchase options, notification design, "Keeper" recognition for the volunteer contributor who funds the vault, and product pricing model.
🧠 Deep Project
💰 Business & Monetization
● Idea — Needs Product Definition
18
Digital Legacy Planning — What Happens When a Gardener Dies
Product Business Model Infrastructure Legal
This is one of the most consequential product questions DandyLine will face. When a gardener dies: (1) their unsealed future blooms must still bloom on schedule — the scheduler can't just stop; (2) their whole garden (pressed flowers, vaults, seeds) needs to go somewhere; (3) someone needs to be able to access or export everything. Competitors in the "digital estate" space include GoodTrust and Everplans — there's a whole category here. DandyLine's angle is different and more emotionally rich. Options to explore: designate a digital executor in advance (like a trusted contact), pre-paid legacy export purchase (one-time fee that funds a full archive delivery after death), or subscription tier that includes estate planning. Big infrastructure question: in a zero-knowledge encryption model, how do we pre-authorize a digital executor to decrypt the garden without compromising security during life? Added 04.09.26.
🧠 Deep Project
🔒 Legal & Privacy
● Idea — Needs Product & Legal Definition
53
Vault Settings Editability — What Can Change After Creation & After Sealing? ✅ DIRECTION LOCKED
ProductVault MechanicsSeed KeysSettings
✅ Direction locked April 27, 2026. Core principle: treat the mechanics like Google Drive — admin/owner level vs. invited contributor level, with most changes allowed at admin level even after seal.

Decisions per setting:

(a) Add new recipient to a sealed vault — YES, allowed. Set as an option, not a default. Real use case: gifting — someone could buy/seal a vault and want to add the recipient later (gift card scenario). Treat like Google Drive's "share with new person" flow.

(b) Swap Guardian after seal — YES, allowed. Already locked in Section C7 of QUESTIONS-FROM-ASHLEY.md (Guardian replacement uses subtle notify flow — outgoing Guardian gets a dignified non-dramatic message). Guardian assignment provides flexibility regardless of whether the planter is alive or gone.

(c) Move bloom date after seal — RESTRICTED. The compromise: bloom date IS movable, because locking it is almost pointless (a planter could just delete + replant to work around it). But:
Only the planter can move the bloom date by default.
An assigned Guardian can move bloom dates if the planter has explicitly designated them with that authority — either for the whole vault or for specific seeds. Guardian designation provides flexibility "regardless of whether I'm here or not."
Super Lock remains the override. When Super Lock is engaged, the bloom date is permanently immovable — no override, not even by Guardian. Super Lock is a PREMIUM feature (see HW#83 Premium Features). Adds to premium tier list.

(d) Edit vault name/description — YES, but ADMIN/OWNER level only. Don't let invited contributors change vault name on a whim — vaults evolve over time, but the framing should be stable. Like Google Drive: only admin can rename. Description updates make sense as the vault grows.
NEW · "Weather Update" passive notification when name/description changes: Subtle in-app notification (NOT a push), styled like a group-chat "X changed the vault name from Y to Z" announcement. Optional UI idea: show "(formerly: Old Name)" in parentheses for ~90 days as a transition marker. Goal: passive awareness without disruption — engaged users see it, others get a soft signal next time they're in the app. Add this to the Weather Update system spec (relevant card to scope: see notification system + bloom-prep flow).

Underlying mental model — like Google Drive: Owner/Admin (planter) has full editing rights. Invited contributors can plant/contribute but can't change vault-level settings. Co-admin role is a separate question that needs its own design pass — see HW#56 spawned questions for the co-admin/co-owner model design blocker.

Open scenarios Ashley wants prompts on (not yet decided):
• Gray area: changing who a specific seed is assigned to within the vault after seal
• Gray area: revoking a Seed Key before it's claimed (different from after-claim removal which is harder)
• Gray area: changing claim limits on Open Claim keys after issue
• Open: how do peer products (Gmail's drafts, Drive's shared docs, iOS Photos shared albums) handle these scenarios? Worth a survey before locking.

Original card added 04.12.26. Direction locked 2026-04-27 with Claude.
💜 Decision
🤔 Direction locked · 4 sub-decisions · spawned premium-tier addition for Super Lock + Weather Update notification spec
● Direction locked — primary settings answered · 3 gray areas remain (seed reassignment, key revocation, claim limit changes)
196
Co-Admin / Co-Owner Permission Model — The Google Drive Distinction
Product Vault Permissions Foundational Spawned from HW#53 + HW#56
Spawned April 27, 2026 from HW#53 (Vault Settings Editability) and HW#56 (Generational Forwarding). The co-admin / co-owner model is the actual underlying design blocker behind several gray-area questions, and needs its own dedicated design pass.

The core question: When someone is invited into a vault, what role can they hold? Today the assumption is "contributor" — they can plant seeds. But several recent decisions assume there's another tier — someone who can manage the vault (rename it, swap the Guardian, take on responsibility/weight when the planter is gone). Like the Google Drive distinction between Editor and Owner / Co-Owner.

Why this is foundational: Without a co-owner role defined, several other decisions are underspecified:
HW#53 (Vault Settings Editability) — the "admin-level only" gating for vault name/description changes only works if there's a clear admin/co-admin tier.
HW#56 (Generational Forwarding) — when the planter dies and there's no Guardian, who picks up the vault? A co-owner is the natural answer.
HW#85 (Hybrid Grove Guardian) — Vault Guardian vs. Contributor Guardian distinction overlaps with co-owner mechanics.

Tiers to consider (Google Drive-inspired):
1. Owner / Planter — full control. Can rename, change description, swap Guardian, modify settings, transfer ownership.
2. Co-Owner / Co-Admin — same powers as Owner except can't transfer or delete the vault. Can add other admins. Picks up vault management if Owner is gone.
3. Contributor — can plant their own seeds inside the vault. Cannot change vault-level settings. Can press their own seeds. Default invite role.
4. Viewer / Recipient — can see/receive blooms but cannot plant. Most restricted role.

Per-vault-type implications: Co-owner makes obvious sense for Grove (multi-contributor) and Legacy (intergenerational), but probably doesn't apply to Personal vaults (solo). Milestone and Journey are gray. Each vault type's deep dive (HW#86) should explicitly answer whether co-owner is allowed, default-on, default-off, or disabled.

What this card needs:
• Permission matrix: rows = actions (rename · invite · change Guardian · move bloom date · press · plant · etc.), columns = roles (Owner · Co-Owner · Contributor · Viewer)
• Per-vault-type defaults — which roles are available, which is the default invite role
• UX for "promote to co-owner" — should be deliberate, not casual
• Edge case: what happens when the Owner tries to leave / delete the vault and there's a Co-Owner? Does ownership transfer? Does the vault keep going?
• Schema impact: new vault_member_role column (or similar) replacing any binary "is_admin" flag

Peer-product reference points: Google Drive (Editor / Commenter / Viewer / Owner / Co-Owner) · Notion (Workspace Owner / Member / Guest) · iOS Photos shared albums (Owner / Subscriber). Worth a 30-min survey before locking the model.

Added 2026-04-27. Direction blocker for HW#53, HW#56, HW#85, HW#86.
🧠 Deep Project
🤔 Foundational design · blocks 4 other cards
● Idea — Needs dedicated design session · blocking HW#53/#56/#85/#86 gray areas
86
Vault-Type Deep Dives — Bring Others Up to Roots-Level Depth
ProductDocumentationSpawned from Planting Flow
Born out of the April 18 planting-flow session. The Roots vault page has the deepest, most resolved thinking of any vault type — it documents triggers, edge cases, identity, verification, ownership, location mechanics, abandonment, and Guardian logic in a way the other vault types don't yet match. Use it as the TEMPLATE and bring the other 5 vault types up to parity: (1) Personal Vault Deep Dive, (2) Grove Vault Deep Dive (pairs with HW#85), (3) Milestone Vault Deep Dive — must capture the "one vault, multiple internal bloom dates" structure (Wedding vault holds seeds for the wedding, 1-year, 5-year, 10-year anniversaries) with a minimum bloom floor; (4) Legacy Vault Deep Dive — must capture the non-morbid use cases (living grandparent to unborn grandchild, 50th-anniversary plant-today-bloom-later, company time capsule, teacher messages for future students) and the decision that Guardian is STRONGLY RECOMMENDED not REQUIRED; (5) Journey Vault Deep Dive. Each page should follow the Roots structure: Overview → Triggers → Who Can Plant → Seed Shape → Guardian Defaults → Edge Cases → Open Questions. This is foundational documentation debt — once done, the planting-flow doc can reference these as the source of truth instead of re-explaining each time.
🧠 Deep Project
📋 Documentation
● Idea — Needs Development
📎 Merged In · From HW#120 (was: "Grove — Relationship changes, contributor death, non-planters")

Merge reason · Grove vault-type detail folds into the Vault-Type Deep Dives hub. Original card consolidated 2026-04-25.

Description: What happens when a contributor's relationship changes (divorce, death) before bloom? Can a seed be recalled? What if a contributor was invited but never planted? Does the recipient see individual seed counts per contributor, or one unified bloom?

Original Status: ● Decision needed before building Grove

📎 Merged In · From HW#121 (was: "Personal — Line between Personal, Milestone, and Legacy")

Merge reason · Personal vault-type detail folds into the Vault-Type Deep Dives hub. Original card consolidated 2026-04-25.

Description: Where exactly is the line? A solo parent planting for a child's 18th = Personal or Milestone? A grandparent at 78 planting for a grandchild = Personal or Legacy? The vault chooser needs decision logic — not just descriptions, but decision questions the user answers.

Original Status: ● Decision needed before building vault chooser

📎 Merged In · From HW#122 (was: "Milestone — Is it really a distinct vault type?")

Merge reason · Milestone vault-type detail folds into the Vault-Type Deep Dives hub. Original card consolidated 2026-04-25.

Description: Milestone may be Personal + occasion context. If so, collapsing them simplifies the product without losing features. Also: the "five friends" story currently in Milestone is actually Grove — needs a real Milestone replacement example (one planter, one recipient, one occasion).

Original Status: ● Decision needed before building vault chooser

📎 Merged In · From HW#123 (was: "Legacy — Posthumous delivery mechanism")

Merge reason · Legacy vault-type detail folds into the Vault-Type Deep Dives hub. Original card consolidated 2026-04-25.

Description: If the planter has died, who confirms delivery should happen? Is there a "legacy guardian" who holds a key? How is identity verified at bloom? What happens to the vault if the account lapses? The posthumous delivery screen must not feel like a notification.

Original Status: ● Most complex feature — needs design before anything else in Legacy is built

#127 — Bloom Experience · Revised Product Walkthrough (Locked Concept)

Parked Ashley Medium Quest #10 · Vault Types

The full walkthrough of what happens when a vault finally blooms: notification → sealed jar opens → preserved dandelion revealed → seeds explored one by one → multi-contributor reveals → long-term capsule evolution. This is the central DandyLine ritual and differentiator from any social memory format.

What's Next
  • Cross-reference with ux-bloom-reveal.html and product-vaults.html during Phase C. Fold into Vault Type Deep-Dives canonical card or keep as a companion reference.
Highlights
  • Core insight: "Closure + anticipation simultaneously" — opened memories visible, future memories still locked within the same vault
  • Differentiation: "Not a feed. Not a slideshow. An interactive preserved life artifact."
  • Status: Marked as "Locked Concept" in the source — foundational product behavior
  • References: Source was biz-dev-notes-product.html (retiring Apr 22, 2026)
Working Pages
Notes — Full cleaned prose

A Seed Is Ready to Bloom

The user receives a notification: "A seed planted 6 years ago is ready to bloom." They open the app. Instead of content immediately playing, they see: a sealed glass vault jar that has finally opened. Inside the vault is a preserved dandelion seed head. This represents the full memory capsule.

The Dandelion Capsule View

Each individual seed on the dandelion represents a memory contribution. When the user enters this view, they see a full dandelion with dozens of seeds. Subtle icons on each seed indicate media type (photo, video, voice note, text message). Each seed shows contributor indicator (who planted it), timestamp, and unlock timing. Some seeds are glowing softly — these are ready to open. Others show "Opens in 6 months" or "Opens on your 14th birthday." This creates layered anticipation. The capsule is open. But the story is still unfolding.

Exploring the Seeds

The user can hover or tap each seed. When opened, the memory appears in full original quality; context appears (date recorded, contributor, optional note). After viewing, the seed becomes part of the opened memory album within that vault. Seeds that are still locked remain visible. This is important psychologically: users can see future memories waiting inside an already opened life chapter. This creates a powerful emotional dynamic — closure + anticipation simultaneously.

Multi-Contributor Vaults

Capsules can be shared. For example, a child's life capsule. Parents, grandparents, friends can all be invited to contribute seeds. Each person chooses what to record, when it unlocks, how it reveals. When the vault opens years later, the user sees a full dandelion made from the love and memories of many people. Not just a single timeline. A community-built emotional artifact.

Long-Term Capsule Evolution

Over time, more seeds unlock, the opened album grows, the locked seeds become countdown anchors. A vault is not just a one-time reveal. It becomes a living time capsule unfolding across years.

Why This Is So Strong

This structure mirrors physical memory boxes, supports legacy storytelling, creates gamified anticipation, reinforces the seed metaphor, enables deep social contribution, and differentiates from any social media memory format. It is not a feed. It is not a slideshow. It is an interactive preserved life artifact.

History
  • Migrated from biz-dev-notes-product.html (lines ~271-356) before notes-page retirement.

#128 — Roots Memory Map · Location-Based Memory Discovery

Parked Ashley Medium Quest #10 · Vault Types

The full Roots concept: memories planted into real-world locations that unlock through presence, timing, or shared experience. Includes private root discovery, personal root trails, public roots layer, unlock mechanics, and the April 7 architectural decisions that rehomed Roots from its own vault type into a seed-level metadata variable.

What's Next
  • Cross-reference with product-roots.html and ux-roots-arrival.html. Most decisions are already canonical — this card exists to preserve the narrative framing and risk notes.
Highlights
  • Done: Architecture locked (Apr 7) — Roots is a seed variable (location metadata), not its own vault type
  • Done: Two location tag states locked — Sprouted Here (GPS auto-captured) vs Rooted Here (manually assigned)
  • Carry-forward: Strong privacy controls, thoughtful location precision, curated public content are essential to maintain trust
  • References: Source was biz-dev-notes-product.html (retiring Apr 22, 2026); canonical home is product-roots.html
Working Pages
Notes — Full cleaned prose + Apr 7 decisions

Core Concept

Some memories are tied not just to time or people, but to places. The Roots Memory Map allows users to plant emotional memories into real-world locations. These become meaningful discovery points that can unlock through presence, timing, or shared experience.

Private Root Discovery

When a user physically arrives at a meaningful location, the app may gently notify them that there are deep roots there. A hidden memory seed can appear and unlock simply because the user is present at that place. This makes memory discovery feel sacred and intentional rather than algorithmic.

Personal Root Trails

Users can view a map showing meaningful places that shaped their life. Examples: childhood home, college campus, first apartment, wedding venue. These locations form an emotional geographic timeline that users can revisit at any time.

Public Roots Layer

Some memories can be shared publicly and tagged by sentiment such as love, loss, courage, or hope. When visiting a location, users may discover anonymous public memory seeds that offer emotional storytelling tied to that place.

Unlock Mechanics

Roots memories can unlock in multiple ways: location-only unlock, location plus specific date, shared presence unlock, journey sequence unlock. These mechanics create ritual, adventure, and deeper meaning.

Visual Experience

The Roots Map should feel organic and calm rather than utilitarian. Design direction: soft terrain textures, glowing underground root systems, floating seed markers, warm light pulses indicating emotional intensity. Zooming out reveals a network of rooted life moments.

Emotional Example

A woman returns to a park where her father once taught her to ride a bike. Her phone gently notifies her of a rooted memory. She opens the app and discovers a voice note he recorded years earlier. This transforms the location into a living emotional time bridge.

Strategic Value

The Roots feature anchors memories in the physical world, encourages intentional travel, supports memorial behaviors, and differentiates DandyLine as a spatial emotional network rather than a traditional memory app.

Decisions — 04.07.26 (locked)

Architecture: Roots is a seed variable (location as metadata on a seed), not its own vault type. Seeds without a location tag simply do not appear on the Roots map — intentional and fine.

Location mechanics in the planting flow: Borrow the Meta/Instagram model. If location services are on, GPS auto-grabs and suggests nearby places — user confirms or adjusts. Manual search/type is also available. Location is always optional and skippable. Active users who want arrival notifications can opt into always-on location (Snapchat model — their choice, never forced).

Location as a bloom condition: Location is just another bloom trigger — same UX as timing, just triggered by physical arrival instead of a date. When you arrive at a location, seeds tagged there become available to bloom (purple activates). User sees a count breakdown by source (personal, vault members, public/strangers) and filters to what they want to bloom.

Two location tag states — naming locked: Sprouted Here = GPS auto-captured at this location (the memory was literally born here; the "wormhole" filter). Rooted Here = Manually assigned (person chose to root this memory to this place — e.g., uploading an old family photo and tagging it to the childhood home). Dedicated to this place, not born there.

History
  • Migrated from biz-dev-notes-product.html (lines ~481-549) before notes-page retirement. Apr 7 decisions preserved.

Quest · planting-flow-design

The planting UX — vault chooser, seed cards, medium-first entry, the planter ritual. · 6 cards

10
Roots — Location as a Seed Setting in the Planting Flow
Product UX Flow Roots
Location needs to be a clearly available option when first planting a seed — both in the planting flow settings and as a nav entry point in the app. Model: if location services are on, auto-grab GPS and suggest nearby places (user confirms or adjusts). Manual search/type always available. Always skippable — location is never required. Needs: planting flow UI update to include location picker, nav placement decision for Roots access.

✅ DECIDED (April 15): Location granularity uses GPS with radius + named place ("Grandma's House"). Choose per seed or when setting up Roots jar.
🔨 Build Session
🏗️ Build with Claude
✅ RESOLVED April 21, 2026 — Combination approach locked. Named place = place-aware boundary via places API. Custom pin = ~150m default radius with slider. "Plant here" = GPS quick-plant. Places API decision delegated to Josh (OpenStreetMap for MVP, Mapbox at scale recommended). See QUESTIONS-FROM-ASHLEY.md Section F1.
73
Planting Flow UX — Medium-First Entry + Vault Rules Gate
UXProductBuild Priority
🔥 PRIORITY. The planting flow starts from the medium (what you're planting) after tapping the Plant nav icon. Then prompts vault selection — established vault or new one. Vault rules gate what's allowed (schedule, type, etc.). If rules conflict, user gets: "The 'XXX' Vault has rules that only allow XXX. Do you still want to plant here? Or build/plant in a new vault?" Needs connection to A1 stat counter vault-building flow. Reference: ux-mockup-reference.html (screen order is close but layout needs work). Note: current mockup says "choose date for vault to bloom" which conflates vault unseal date and seed bloom date — must separate. Ashley's notes: see A1 Plane Workbook.
🧠 Deep Project
🛠 Build Task
🟡 In Progress — 9 of 13 decisions resolved (April 18, 2026). Remaining: Journey vault (3 Qs), Technical & Monetization (4 Qs), planting ritual minimum. See ux-planting-flow.html Unknowns section.
74
Pop-Up Seed Cards — Per-Media-Type Development
UXBuild Priority
Each seed media type needs its own bloom/reveal pop-up card design. Photo cards exist (ux-bloom-reveal.html screen 10). Voice memo needs: animated visual + transcript display (is transcription an added tool?). Notes need: rich text rendering — do we allow emojis/formatting when planting text seeds? Also need "After the Bloom" prompts per media type. Heavy dev — this is a huge part of the experience. Reference: ux-bloom-reveal.html.
🧠 Deep Project
🛠 Build Task
● Idea — Needs Development
102
Multi-Seed Vault UI Design — Curator View, Guest View & Roots Filter (Priority 1)
Product UX Design Vault Mechanics Workbook Priority
One vault holding multiple seeds with different bloom dates is a premium feature worth designing carefully before building. Three sketching tasks to complete:

Curator View (Gardener managing 4 seeds with different unlock dates):
— Dashboard layout: how does a gardener see all 4 seeds at once?
— Unlock timeline visualization: a horizontal or vertical timeline showing each seed's bloom date
— Per-seed controls: edit date, add/remove contributors, silence notifications
— How does the gardener see "who can contribute what"?

Guest View (someone added to a multi-seed vault):
— Initial view: all seeds visible (locked + unlocked), grouped by bloom date
— Filtered view: guest can show "only 1-year seeds" or "only bloomed"
— Countdown timers on each locked seed — how prominent? How styled?
— What happens when one seed blooms but others are still locked?

Roots Filtering System ("roots" = unlock date categories):
— Each unlock date = one "root" in the garden metaphor
— Visual hierarchy: show all seeds, but group by root/unlock date
— Filter by root: "Show only 1-year seeds" / "Show only bloomed"
— Users see full garden OR filtered garden view

Open Question to decide first: How many preset unlock date options do curators need? Options: 1-week, 1-year, 5-year, 10-year, custom. Or just custom always? Presets reduce friction for event-based vaults (weddings). Custom is more flexible but requires more input. Decide before sketching the curator controls.
🧠 Deep Project
🎨 Visual / UX Design · Build with Claude
● Idea — Needs UI Sketching + Decision on Preset Dates First
201
Seed Packet — Staging Area for Un-Planted Seeds
Product UX Brand Vocab Planting Flow
A Gardener-owned staging area for Seeds they want to keep but haven't decided where to plant. The brand-aligned version of "drafts / inbox / saved-for-later." Use cases: quick capture, "I don't know which Vault yet," holding for an upcoming Vault someone else will plant, quick-hits.

Behavior: Has its own icon. Lives near the Plant action. Seeds inside are NOT yet planted — no Vault, no bloom date, no Guardian. Weather (HW#41) can prompt: "You have N Seeds in your Seed Packet — ready to plant?"

Spec needed:
— Lifecycle state — does an un-planted Seed in the Packet have a state in product-seeds.html? (Likely yes — a new pre-Sealed state.)
— UX — entry from Plant FAB? Inline option in the Plant flow ("plant later")?
— Limits — does the Packet count against storage cap?
— Surfaces affected — product-seeds.html, ux-planting-flow.html, Weather (HW#41), Plant FAB
— May warrant its own product page: product-seed-packet.html

Inspired by Moleskine intake (May 2, 2026 session). Brand vocab: Seed Packet replaces "drafts / inbox / saved-for-later" universally.
🔨 Build Session
🎨 Visual / UX Design + Product Spec
● Idea — Needs Development
114
Visual Interactive Workflow Map — ux-planting-flow.html Redesign
UX Design Visual Brand Product
The ux-planting-flow.html file holds the most thorough UX decision map in the entire project — 8 decision layers, 5 vault types, 5 media types, 7 bloom triggers, 26+ unique paths. Right now it's presented as an expandable decision-tree document, which works but doesn't feel like DandyLine.

The vision: redesign it as a visual interactive workflow map. Strong visual. A little subtle animation to keep it fun and alive. Hover or click each node to expand and read the detail underneath. The reader should be able to trace a path through the flow visually — not just scroll through a long document.

Must reference existing brand decisions for visual accuracy:
brand-logo-marks.html — logo, marks, app icons
brand-icon.js — dandelion mark renderer
product-dandelion.html — canvas rules, animation reference
product-vaults.html — canonical in-vault dandelion & jar rendering, dot language per vault
product-seeds.html — seed color specs, lifecycle, state rules
brand-shared.css + brand-system.html — tokens, palette, type

Design principles: no hard angles, no sharp animation easing (per brand-guide Don'ts), dark background, warm gold accents, organic/breath-like motion. Nodes should feel alive — not static diagram shapes.

Scope note: this is a full design session, not a cleanup pass. Do not combine with other work. When it's time, open with Opener D (thinking session) to sketch direction before building.

Added April 22, 2026 from the ux-planting-flow cleanup conversation.
🧠 Deep Project
🎨 Visual / UX Design
● Idea — Needs Development
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

Quest · brand-sweep-vocabulary

Brand voice, vocabulary, visual sweeps, language polish across all pages. · 9 cards

15
Update Brand Seeds Page & Vault Pages — Preservation State Visuals
Brand UX Design Seeds
product-seeds.html and the vault UX pages need updates to reflect the new preservation state design decisions. Specifically: the crystallized/shimmer visual for pressed seeds, the brown/amber composting tier appearance, the third "shared access" color state, and the "already preserved by [name]" indicator on shared seeds. The brand standards keep evolving as product decisions are made — this sweep should happen after Homework #13 (pressed seed visual) is resolved so changes can be applied consistently across all pages at once.
🔨 Build Session
🎨 Visual / UX Design
● Idea — Needs Design Sweep After #13
📎 Merged In · From HW#013 (was: "Pressed Seed Visual Treatment — Crystallized / Shimmer Effect")

Merge reason · Pressed Seed Visual Treatment is one specific visual within the Preservation State Visuals sweep. Original card consolidated 2026-04-25.

Description: A pressed seed needs a distinct visual signal that it's permanently protected — precious, locked in time. Explore: a subtle crystalline shimmer or frost overlay on the orb, a small sparkle animation that fires once on pressing then settles to a steady glow, a slightly different interior texture vs. standard sealed seeds. Should feel unmistakably different but not loud. Also needs: "Already preserved by [name]" indicator on shared seeds so vault members can see what's already safe and avoid paying to duplicate storage of the same memory.

Original Status: ● Idea — Needs Visual Exploration

24
Founder Story Update — "The Moment I Never Want to Forget"
Brand Founder Story Marketing
The current founder story captures the preservation angle well, but a new dimension emerged in session: the raw, everyday capture problem. Not just "I want to send this forward" — but "my kid just said the most hilarious, heartbreaking, perfect thing and I have nowhere to put it right now." The example: a funny thing a child said in their sleep, or an unexpectedly deep/embarrassing question they asked out of nowhere. You caught it in the moment. No video. No recording. Just your memory. And that memory will fade. Everyone — parent or not — has this feeling. The founder story should gain a beat that names this specific pain: the preciousness of a fleeting moment that has nowhere to go except a notes app nobody looks at. Keep examples vague and universal (avoid specific holidays or religious references). Also tie in the "personal vault as a joke archive" angle — even a solo vault set to Surprise scheduling, full of things-you-never-want-to-forget, is a deeply relatable use case. Added 04.09.26.
⚡ Quick Win
✍️ Copy & Writing
● Homework — Story Update Needed
32
Daytime Mode Theme — Complete or Cut Before Launch
Product UX Design Brand
The nighttime skin has full design love. The daytime version doesn't. When the day/night toggle switches to light mode, several elements get lost or feel unfinished. Decision required before launch: either give the daytime skin proper full treatment (explore a "negative effect" approach — inverting the nighttime design logic so the two skins are true counterparts), or remove the toggle entirely and add full light mode as a future milestone. The toggle should not ship half-done. If removed short-term, document "Full Light Mode / Daytime Skin — Platform-Wide" as a post-launch item. Once built, the daytime color logic should be formalized in the Brand Standards & Design Guidebook alongside the nighttime system. Migrated from coaching dashboard 04.09.26.

✅ DECIDED April 21, 2026: Dark mode ships first. Light mode is HIGH PRIORITY before wider release — target after first 100 users. Approach: CSS variable swap (define a [data-theme="light"] override set — same variables, different values). Canvas elements and glows need individual attention but this is ~20-30% of original design effort, not a redesign. Accessibility driver: older users and bright environments. No toggle until light mode is fully designed.

Vocab note (locked 2026-05-02): "Theme" is the official term for visual day/night modes app-wide — replaces "Skin" everywhere. Distinct from "Bloom Mode" (HW#94), which is the reveal-experience layer for a Vault, not a visual theme.
🔨 Build Session
🎨 Visual / UX Design
● High Priority — After first 100 users, before wider public release. Not a launch blocker for family MVP.
37
Vault Storylines — Write 6 Vault Stories (One Per Vault Type)
Brand Marketing Copy
Started in a dedicated session — working notes saved in dandyline-story-project-notes.md. One story per vault type: Grove, Personal, Milestone, Legacy, Journey, Roots. Milestone was attempted but kept feeling off because it started from the product mechanic (here's what it replaces, here's how timing works) rather than from a single human truth. The fix: restart each story from one specific character, one specific moment, and let the vault reveal itself through the story — exactly the way the ad ideas work ("Before I Forget," "Still Arriving"). Milestone re-entry point: try the bride's mom who quietly set the whole thing up without telling anyone, or the groom the night before. Reference biz-mktg-ad-ideas.html for tone and structure before writing each story. Read dandyline-story-project-notes.md before starting. Added 04.12.26.
🔨 Build Session
✍️ Copy & Writing
● In Progress — HOLD — See dandyline-story-project-notes.md
#69 — Button Design System · Finalized
Design System UX
What we built: Created ux-button-system.html — a full interactive button design system explorer with 15 sections and 71 variant cards. Every button type DandyLine needs is in there with pill vs. rounded-rectangle options side by side.

Sections completed: Primary CTA (8 variants), Secondary (6), Selection/Options (6), Toggles + iOS switch (7), Nav CTAs (6), Icon Buttons & FABs (6), Destructive/Compost (4), Tags & Chips (4), Size Scale, Avatars & Profile Icons (6), Card Selectors — seed types/bloom triggers/vault cards (5), Segmented Controls (4), Tab Nav Bar with Plant hero button (3), Stat Chips & Notification cards (4), Combo Demos (4 family groups).

From Ashley's screenshots (captured, not lost):
  • Solid-color avatar circles from homepage (preferred over ring style) → AV2/AV3 in explorer
  • Icon-top card selectors (Photo, Video, Voice Note) with dashed Guided Prompt variant
  • Vault detail cards with jar icon + seed count from planting flow
  • Big gold circle Plant CTA in bottom tab nav — 3 variants (solid, gradient, breathing glow)
  • Stat counters (Vaults/Bloomed/Soon/Sealed) with vault-colored numbers
  • Compost warning + weather update notification card patterns

Re-entry point: Open ux-button-system.html in browser. Star your favorites in each section. Tell Claude which ones win → Claude writes the locked design rules document and updates biz-dev-command-center TOC.

Key decisions still open:
  • Pill vs. rounded rectangle — which shape direction for DandyLine?
  • Primary CTA style — gradient fill (P1/P2), solid gold (P3/P4), outline-to-fill (P5/P6), or soft glow (P7/P8)?
  • Avatar style — solid fill (AV2, preferred) or solid + glow (AV3)?
  • Plant hero button — flat solid gold (TAB1), gradient ring (TAB2), or breathing glow (TAB3)?
  • Once locked → sweep all existing UX pages to update buttons to the chosen system
🧠 Deep Project
🏗️ Build with Claude
✅ Finalized — April 18, 2026 — ux-button-system.html locked as the canonical button reference. To be shared with Josh as a build reference.
113
Feeling Tag System — Pick the Canonical List ✅ BLOOMED
Product Brand Seeds
✅ Resolved April 27, 2026. The canonical tone library now lives in product-seeds.html — a 21-word tone library organized by color family, not a flat list. The system auto-detects 1–2 dominant tones from the seed's title and notes (the gardener never picks a color manually). Two-tone seeds get halo treatment.

Canonical 21-word tone library (by color family):
Gold — Joyful · Proud · Warm · Funny · Playful · Hopeful
Sky (default if no match) — Reflective · Quiet · Peaceful · Nostalgic · Timeless · Practical
Purple — Wise · Awe · Wonder
• Plus tones in additional families (Pink for Tender, Sage, etc.) — see product-seeds.html Section 02 for the full library.

Why both old lists were wrong: List A was too sparse (4 tones · couldn't hold grief), List B was too flat (no color-family structure). The new system is richer than either — it has emotional range AND drives a visual color system simultaneously.

How this got missed in homework: HW#113 was filed April 22; the tone library work happened in the April 27 parallel color-model session and updated product-seeds.html directly. The card didn't get back-updated at the time. Flagging as a closing-ritual / dashboard-sweep gap to watch for in future parallel sessions.

Source of truth: product-seeds.html (Section 02 · "Color says WHO the seed is") — auto-detection logic + halo behavior for cross-family vs same-family pairs both documented there. Bloomed 2026-04-27.
⚡ Quick Win
📋 Product Decision · Bloomed
● BLOOMED — Canonical 21-word tone library locked in product-seeds.html · 2026-04-27

#131 — Master Vision & Concept Proposal (cleaned)

Parked Ashley Medium Quest #12 · Brand Sweep

The foundational DandyLine vision: why it exists, what it solves, what it is, the meaning behind the name and dandelion symbolism, core taglines, capsule types, emotional story examples, and the "why now" cultural case. Celestial framing (sun/moon/stars) and military-children framing have been stripped per the April brand-sweep decision.

What's Next
  • Use as the canonical long-form vision doc. Cross-reference with brand-ethos.html and biz-mktg-founder-story.html for consistency.
Highlights
  • Core belief: "The most important moments in life are not meant to be consumed immediately. They are meant to return to us at the right time."
  • Tagline: "Preserve memories today. Let them bloom later."
  • Category: Emotional Storage Platform (new category)
  • Cleanup applied: Celestial sun/moon/stars framing removed. Military-children framing removed (Quest #9 still owns the military partnership GTM separately).
Working Pages
Notes — Full cleaned prose

Preserve memories today. Let them bloom later.

Vision

We are living in the most documented era in human history — yet meaningful memories feel more disposable than ever. Moments are posted instantly. Posts are often performative. They are scrolled past quickly and buried beneath ads, outrage, news cycles, and algorithmic noise.

DandyLine is built on a simple belief: the most important moments in life are not meant to be consumed immediately. They are meant to return to us at the right time. DandyLine restores patience, anticipation, and emotional rediscovery to memory. It is a protected space where memories are preserved with intention and rediscovered when they matter most.

The Why — What This Solves

Today's memory behaviors reveal a deep cultural tension. People capture everything, but rarely revisit anything in meaningful ways. Signals already show demand for a new approach: social media feeds are crowded with ads, negativity, and performative pressure; many people post milestones mainly to store them somewhere; old photos and videos degrade due to compression and platform changes; camera rolls are overwhelming; scrapbooks and memory books go unfinished because they are too time-consuming; posting publicly can feel less genuine and more audience-driven. DandyLine enables more personal, private, and authentic memory capture — removing performative pressure and restoring emotional ownership of moments.

What Is DandyLine

DandyLine is a future-facing memory platform. Users plant memories as seeds — photos, videos, voice recordings, or written notes — and schedule them to bloom later. Memories are sealed in a vault and cannot be reopened until their bloom date arrives. When the bloom moment occurs, the memory gradually reveals itself, recreating the emotional context of the original moment. Over time, memories form a living Roots Archive connecting life events, people, places, and identity across time.

The Name Behind the Vision: What a Dandelion Means

The dandelion is the most misunderstood plant on earth. Dismissed as a weed, fought with weedkiller, pulled from manicured lawns — yet it returns. Every time. It persists through concrete. It survives being cut down. And when it finally opens into that iconic white sphere, a single breath transforms it into dozens of tiny stars drifting toward futures unknown.

DandyLine takes its name and its spirit from this remarkable plant. The dandelion's lifecycle mirrors DandyLine's arc — the golden flower fully alive, the silver puffball preserved and waiting, the seeds dispersing on the wind. Plant, preserve, bloom.

The Art of Intentional Release

The universal tradition of blowing on a dandelion and making a wish before the seeds disperse is one of the most recognized acts of childhood hope in the world. It's an act of intentional release — the belief that if you hold your breath and your intention, what you release into the world will find its way to where it belongs. Planting a memory in DandyLine is the same act. You hold a moment. You attach an intention to it — a feeling, a future recipient, a milestone worth waiting for. And then you release it, trusting it will bloom when the time is right.

Transformation as the Core Promise

The dandelion's lifecycle is one of the most dramatic transformations in the plant world. From a bold, unapologetic golden flower — to a suspended, luminous sphere — to an explosion of individual seeds, each carrying its own destination. The same plant, three entirely different forms of beauty. DandyLine mirrors this arc: Plant (the moment fully alive, captured at its brightest) → Preserve (held in the vault, glowing softly, waiting) → Bloom (the seed in flight, arriving at exactly the right time). What we call 'blooming' in DandyLine is not just a metaphor. It is the full realization of a moment — the point at which something preserved becomes something experienced.

Core Taglines

  • Preserve memories today. Let them bloom later.
  • Social media archives memories for attention. DandyLine preserves them for the future.
  • The internet forgot how to wait. DandyLine remembers.
  • Some moments are meant for later.
  • Memories deserve more than a scrolling feed.

Main Capsule Types

Personal Reflection Capsules — Messages to future self, career transitions, emotional growth. Family Memory Capsules — Everyday photos, texts, and voice notes for children to open gradually across life. Friendship & Life Chapter Capsules — Trips, shared experiences, and milestone memories. Event Capsules — Weddings, graduations, births, and anniversaries. Location Capsules — Memories tied to meaningful places that bloom upon return. Legacy Capsules — Messages from older generations preserved for future family members.

Emotional Story Examples

IVF Journey: A woman plants memories during fertility treatments. Years later a bloom reveals her past self hoping to one day hold her child — now she is. Everyday Parenting: Small texts, silly photos, and ordinary moments bloom years later for a grown child. Grandparent Legacy: A grandparent records recipes, stories, and advice that bloom long after they are gone. Friendship Capsule: A college friend group opens a shared capsule ten years later and reconnects emotionally.

Why Now

Cultural shifts indicate readiness: nostalgia trends, digital legacy awareness, social media fatigue, desire for intentional living, overwhelming personal archives. The opportunity exists to create a new category: future memory experiences.

Cleanup applied: Celestial (sun/moon/stars) framing and military-children ("dandelion people") framing have been removed per retired brand narrative. Core dandelion-as-seed symbolism preserved. Military partnership GTM continues separately under Quest #9.

History
  • Migrated from biz-dev-notes-strategy.html (lines ~135-308). Celestial and military-children framing stripped.

#132 — Emotional Storage · Category Creation & Differentiation

Parked Ashley Medium Quest #12 · Brand Sweep

The "Emotional Storage" category positioning: why DandyLine isn't inventing new tech but recombining proven tech into a new emotional category. Differentiation vs Apple/Google Photos (media backup) and social media (attention platforms). The positioning reduces technical risk while increasing adoption potential.

What's Next
  • Anchor phrase for the brand-positioning sweep. Cross-reference with HW#108 (Six-Layer Moat) and HW#110 (Dandelion Landing Metaphor).
Highlights
  • Core insight: "Differentiation is not technical novelty. The differentiation is emotional framing, time-based experience design, and trust-centered memory preservation."
  • Category name: Emotional Storage Platform
  • Pillars: Meaning · Anticipation · Legacy · Reflection · Intentional sharing
  • References: Source was biz-dev-notes-strategy.html (retiring Apr 22, 2026)
Working Pages
Notes — Full cleaned prose

Core Positioning Insight

DandyLine is not inventing new technology at its core. It is recombining proven technologies — cloud storage, media sharing, delayed messaging, and memory organization — into a new emotional platform category. The differentiation is not technical novelty. The differentiation is emotional framing, time-based experience design, and trust-centered memory preservation. This positioning reduces technical risk while increasing adoption potential.

Category Creation: Emotional Storage Platform

Traditional storage platforms focus on file access and convenience. Social platforms focus on attention and immediacy. DandyLine focuses on: Meaning · Anticipation · Legacy · Reflection · Intentional sharing. This creates a new category: Emotional Storage.

Differentiation vs Apple Photos / Google Photos

They provide: media backup, AI sorting, search convenience. DandyLine provides: future-delivery memories, relationship-based vaults, emotional timeline design, story-driven resurfacing, legacy preservation planning.

Differentiation vs Social Media Platforms

Social media optimizes for performance, attention, and immediacy. DandyLine is designed for reflection, legacy, and emotional continuity. Every platform in the space competes on storage. DandyLine competes on time. The file is just the container — time is the medium.

History
  • Migrated from biz-dev-notes-strategy.html (lines ~1245-1288) before notes-page retirement.

#165 — Reconcile 25-Year Guarantee / 50-Year Legacy Promise / Sunset Offboarding into One Canonical Home

Thinking Ashley Medium Brand · Promise

DandyLine has made a real brand commitment — the "25-year guarantee," "50-year Legacy Promise," and "Sunset offboarding" plan if the company ever shuts down. Today the language lives in three separate places (product-vaults.html Legacy section, product-seed-keys.html Section 15, biz-competitive-landscape.html) with no single canonical home. Risk: pages drift, numbers fall out of sync, investors and lawyers can't point at one source of truth. Bigger question Ashley flagged: is this still a promise we want to make once we understand the real long-term storage costs? Card holds both the language-reconciliation work AND the financial-modeling decision until storage-cost analysis lands.

What's Next
  • Wait for long-term storage cost analysis (R2 / archival economics over 25+ years)
  • Decide: keep the 25/50 promise as-is, scale it, or replace with a different commitment
  • Once decided, pick a canonical home (likely product-vaults.html Legacy section since it's already most substantial)
  • Sweep the other two pages to point at the canonical home rather than restate the promise
  • Optional: add a single "Our Promises" section to brand-ethos.html as a brand-level home
Highlights
  • Currently lives in: product-vaults.html Legacy section · product-seed-keys.html Section 15 · biz-competitive-landscape.html
  • Why it matters: Investors, lawyers, and customers will ask "where is your promise documented?" — having three answers is a trust signal in the wrong direction.
  • Origin: Flagged by the 4/22 evening ripple check; deferred for Ashley's call. Greenlit on 4/25 with the cost-side condition attached.

Quest · investor-founder-narrative

Founder story, pitch deck, TAM, category dominance, monetization story. · 5 cards

31
Stats & Proof Points — Find a Visible Website Home
Website Content Investor
The original homepage "Problem" section had strong stats and proof points (2800+ camera roll photos, 30-min social post half-life, 0 platforms built for later, 22% photo compression, 58% lost-in-transit stat, memory decay timeline, four problem cards: Performative Trap / Lost in Transit / Timing Problem / No Future Orientation). These were replaced on the homepage with the new emotional elevator pitch section on April 9, 2026. The copy is saved in the Copy Vault under "Founder & Investor Proof Points." The full original HTML with all visual treatments (animated counters, decay timeline, glass cards) is archived at archive/site-landing-problem-section-ORIGINAL-2026-04-09.html. These stats MUST live somewhere visible on the site — not buried in footnotes or reference docs. Best candidates: investor page, founder story page, or a dedicated "Why DandyLine" section. The visual treatment was strong — don't just dump the text, rebuild or relocate the original design. Added 04.09.26.
🔨 Build Session
🎨 Visual / UX Design
● Don't Lose This — Needs New Home on Site
103
Founder's Vault Commitment — "The Bloom" Vault Decision (Priority 2)
Growth Product Personal Action Workbook Priority
New users would automatically be added to a vault showing Ashley's journey building DandyLine in real-time. Some seeds pre-unlocked on Day 1; others unlock gradually over months/years. The question is whether Ashley commits to doing this or not — and if not, what growth mechanism fills the same role.

⚡ The Decision (Yes or No):
Will you document DandyLine in DandyLine? This is the core commitment question.

If YES — What to plan next:
— Name your first 3 seeds (examples: "Why I built this" voice note · Original logo + evolution timeline · First failure moment)
— Set bloom dates for each
— Plan cadence: weekly text (wins/failures/decisions), biweekly photos (UI before/after), monthly video (talking-head, honest, 3-5 min)
— Identify past content you can backfill: original pitch deck screenshots, early UI mockups, team photos, moments of doubt, breakthrough moments

If NO — What to answer:
— What other growth strategy excites you?
— Why doesn't the Founder Vault feel right? (discomfort, positioning, time?)
— What replaces Loop 3 (Founder Journey) in the growth model?

Tone Guide (NON-PERFORMATIVE):
✅ "I was terrified. Still am." · "This feature took 2 weeks and we're still not sure it works." · "I almost gave up here. Here's what changed my mind." · "We failed at this. Here's what we learned."
❌ "So grateful for this journey!" · "Excited to announce..." · "I'm so blessed to be building this"

Risk to mitigate: Could feel like "follow the founder" instead of "use the platform." Balance with public vault templates from 5+ different user types (weddings, births, personal journeys, collaborations).
📋 Decision Needed
📋 Product + Personal Commitment
● Decision Pending — Has not been locked yet

#107 — The Grandparent Legacy Flow: A Seven-Phase Emotional Journey

Spec-Ready Ashley High Quest #14 · Investor Narrative

This narrative traces a grandmother's emotional journey using DandyLine to preserve moments for her newborn granddaughter — from first realization through legacy continuity. It illustrates retention-through-love, relationship gravity, and how time-delayed memory delivery creates ongoing engagement. This is the anchor story for the founder/investor narrative.

What's Next
  • Use as the anchor narrative in the investor deck v2 (opens the emotional case)
  • Extract 3-4 emotional hooks for landing-page hero and waitlist nurture copy
Highlights
  • Status: Fleshed out as a 7-phase arc; ready to convert into deck slides or landing copy
  • Depends on: Quest #14 investor deck build; Quest #13 Site & Landing
  • References: Originally drafted in biz-dev-notes-product.html (pre-retirement)
Working Pages
Notes — Full cleaned prose

Planting Love Into the Future

Phase 1 — The First Moment of Realization

Granny is 67. Her granddaughter Stella has just been born. She takes photos constantly. Tiny hands. First smile. Sleeping on her chest. She thinks: "I hope she remembers me like this." But she knows she may not always be there. Someone tells her about DandyLine. Not as a tech tool. But as a way to leave moments behind that arrive later. This is the emotional entry point. Not memory storage. Future presence.

Phase 2 — Planting the First Seed

Granny opens the app. She records a simple video: "Hi Stella… you're only three weeks old right now…" She laughs. She cries halfway through. She also types a tiny note: "Today you made the funniest face when you sneezed. I laughed all afternoon." She chooses: Recipient → Stella; Bloom timing → Age 10. She seals the vault. The jar closes. The seed floats into Stella's future timeline. Granny sees: "Stella will receive this in 9 years." Time becomes tangible.

Phase 3 — Living With the Future Commitment

Years pass. Granny keeps using the app. Not because she receives memories. But because she is building them. She plants seeds: First day of school message; Advice for teenage years; Story about Stella's parents; Family history recordings; Voice notes saying "I'm proud of you"; Tiny text memories like: "Today you dumped an entire bowl of cereal on the floor and looked so proud." / "You told me I was your best friend. I will never forget that." Each time she plants one, she sees: A future emotional milestone scheduled. Her timeline becomes: A garden of promises.

Phase 4 — Relationship Gravity

Granny invites Stella's parents. They contribute too. Stella's life capsule grows: photos, audio, handwritten note scans, funny videos, simple text notes capturing everyday magic. Granny checks the app sometimes just to see: How many seeds are waiting for Stella. This is retention through love. Not habit.

Phase 5 — The First Bloom

Stella is now 10. She has the app because: "Granny left you something for today." Stella opens her first vault. She sees: A full preserved dandelion. Dozens of seeds. Some glowing. Some locked. She taps one. Granny appears on screen. Younger. Healthier. Laughing. Stella freezes. This is not a memory. This is a time bridge.

Phase 6 — Emotional Feedback Loop

Granny receives a notification: "Stella opened your memory today." She sits down. She watches Stella's reaction video. She cries. Then she plants another seed. This moment alone can drive years more engagement.

Phase 7 — Legacy Continuity

Eventually Granny passes away. But Stella continues opening seeds: Age 13, Age 16, Graduation, Wedding day. Granny continues to "arrive" in her life. Not through static photos. Through intentional future presence.

Cleanup applied: Removed sun/moon/stars celestial framing (retired). No military references. No Supabase refs.

History
  • Migrated as gem #1 from biz-dev-notes-product.html. Cleaned of celestial framing.

#134 — TAM · 5-Layer Market Breakdown for Investors

Parked Ashley Medium Quest #14 · Investor Narrative

The 5-layer TAM story for investor conversations. Layer 1: Smartphone users (6.8B global). Layer 2: Paid digital storage behavior ($100B+ market). Layer 3: Life event economy (trillions). Layer 4: Digital wellbeing ($200B+). Layer 5: Generational legacy (under-digitized). Category positioning line: "If social media monetized attention, Future Memory Platforms will monetize emotional continuity."

What's Next
  • Pair with HW#108 (Six-Layer Moat) in the investor deck. The TAM layers answer "is this big enough" and the moat layers answer "can you defend it."
Highlights
  • Core thesis: Memory is a universal behavioral surface — every human experiences nostalgia, documents life moments, seeks meaning, fears forgetting
  • Reachable market (Layer 1): ~800M–1.2B users in developed + emotionally-engaged markets
  • Category positioning: "If social media monetized attention, Future Memory Platforms will monetize emotional continuity"
  • References: Source was biz-dev-notes-business.html (retiring Apr 22, 2026)
Working Pages
Notes — Full 5-layer breakdown

What Is TAM & Why It Matters

TAM stands for Total Addressable Market. It represents the total revenue opportunity available if a product achieves full adoption within its category. Investors look at TAM early because it answers: "Is this idea big enough to build a venture-scale company?" For DandyLine, TAM is not framed as a niche memory-app market — it's framed as a new behavioral category around how humans relate to memory, identity, and time.

Core Market Thesis

Memory is one of the largest emotional behaviors on earth. Every human experiences nostalgia, documents life moments, has relationships, moves through life transitions, seeks meaning and legacy, fears forgetting. This makes memory preservation a universal behavioral surface.

TAM Layer 1 — Smartphone Users

Global smartphone users: approximately 6.8 billion. If DandyLine targets emotionally engaged digital consumers, developed markets first, privacy-oriented users, and reflection-and-wellness adopters, the initial reachable market is approximately 800 million to 1.2 billion users.

TAM Layer 2 — Paid Digital Storage Behavior

Consumers already pay for iCloud, Google Photos, Dropbox, journaling apps, therapy apps, family legacy tools. Global consumer cloud storage market trajectory: over $100 billion. DandyLine positions itself as the emotional storage + experience layer.

TAM Layer 3 — Life Event Economy

Memory-driven industries include weddings, births, funerals, graduations, major travel, anniversaries, retirement. These represent trillions in emotional spending globally. DandyLine becomes the digital emotional layer across life transitions.

TAM Layer 4 — Digital Wellbeing Market

Rapid growth areas: meditation apps, therapy platforms, journaling tools, habit-reflection products. Projected emotional wellness ecosystem: $200 billion and growing. DandyLine sits at the intersection of memory + identity + reflection + time.

TAM Layer 5 — Generational Legacy Market

Includes ancestry platforms, estate planning services, memory preservation businesses, physical legacy products. This category remains under-digitized. DandyLine modernizes legacy behaviors for the digital era.

Category Scale Positioning Line

"If social media monetized attention, Future Memory Platforms will monetize emotional continuity."

History
  • Migrated from biz-dev-notes-business.html (lines ~684-820) before notes-page retirement.

#135 — Category Domination Roadmap · 3-Phase Plan (Years 0–7)

Parked Ashley Medium Quest #14 · Investor Narrative

The long-horizon plan for DandyLine to create and dominate the Emotional Storage category. Phase 1 (Years 0–2): Time Capsule Platform MVP + early adopters. Phase 2 (Years 2–4): Premium Memory Archive Service. Phase 3 (Years 4–7): Global Digital Legacy Platform. Includes defensibility moats and long-term outcome possibilities.

What's Next
  • Use as the "long-term vision" slide in investor decks. Cross-reference with HW#108 moat layers.
Highlights
  • Phase 1 goal: Achieve product-market fit and category recognition
  • Phase 2 goal: Become the preferred platform for intentional memory preservation
  • Phase 3 goal: Establish DandyLine as infrastructure for personal legacy
  • Long-term outcomes: Category-defining independent company · Acquisition by major tech/storage platform · Partnership with legacy or wellness ecosystems
  • References: Source was biz-dev-notes-strategy.html (retiring Apr 22, 2026)
Working Pages
Notes — Full 3-phase roadmap

Vision

DandyLine aims to create and dominate the category of Emotional Storage — a trusted global platform where people preserve meaningful life moments for future emotional experiences.

Phase 1 — Emotional Time Capsule Platform (Years 0–2)

Focus: MVP launch · Early adopters (parents, couples, legacy planners) · Core features (vaults, seeds, timed unlocks, contribution pods) · Subscription validation · Emotional brand storytelling. Goal: Achieve product-market fit and category recognition.

Phase 2 — Premium Memory Archive Service (Years 2–4)

Focus: Expanded storage tiers · AI memory organization and recap experiences · Physical exports (books, capsules) · Family network growth · Community journey pods · Seed packet marketplace. Goal: Become the preferred platform for intentional memory preservation.

Phase 3 — Global Digital Legacy Platform (Years 4–7)

Focus: Estate and inheritance integrations · Trusted contact protocols · Institutional partnerships · Cultural positioning as long-term life archive. Goal: Establish DandyLine as infrastructure for personal legacy.

Network Effects Strategy

  • Receiving capsules drives new user adoption
  • Family clusters create retention
  • Milestone prompts encourage repeated engagement
  • Emotional anticipation strengthens habit loops

Defensibility Moats

  • Category naming ownership
  • Emotional UX differentiation
  • High switching costs due to stored memories
  • Brand trust moat
  • Future identity claim infrastructure (patents / legal certificates)

Long-Term Outcome Possibilities

  • Category-defining independent company
  • Acquisition by major tech or storage platform
  • Partnership with legacy or wellness ecosystems
History
  • Migrated from biz-dev-notes-strategy.html (lines ~1181-1240) before notes-page retirement.

Quest · bloom-day-ritual

The bloom reveal experience — ceremony, presentation modes, release moments. · 1 cards

94
Bloom Mode — Vault Reveal Presentation
Strategy PMF Product Bloom UX
Vocab note (locked 2026-05-02): Renamed from "Vault Skin" to "Bloom Mode" to avoid collision with "Theme" (visual day/night, HW#32). A Bloom Mode is how a Vault reveals — wedding timeline carousel, baby book page-flip, sobriety counter+gallery, etc. Not a visual skin.

A Vault doesn't have to bloom the same way every time. Bloom Modes are different presentation modes that change how content is revealed when a Vault blooms — not the content itself, just the experience layer. Examples: a wedding Vault could bloom as a timeline carousel with music; a baby book Vault could bloom as a simulated book-flip; a sobriety journey Vault could bloom as a counter + gallery. Competitors (especially in the physical book space) have one output mode. DandyLine's digital-native model lets you pick the emotional experience, not just the container. Needs: a defined list of Bloom Modes (3–5 for MVP), design for each, and a "choose your Bloom Mode" step in the Vault creation flow. This is also a premium feature candidate — free tier gets the standard reveal; paid tier unlocks cinematic Bloom Modes. Added 04.22.26.
🔨 Build Session
🎨 Visual / UX Design
● Idea — Needs Development

Quest · post-launch-support

Notifications, abuse prevention, posthumous notification language, user support mechanics. · 2 cards

54
Posthumous Notification Language — When Blooms Arrive From Someone Who Has Passed
NotificationsLegacyCopyUX
When a bloom arrives from a planter who has died, every touchpoint needs a softer, more reverent version. This includes: email subject lines (no "Grandma just sent you!" energy), bloom reveal screen (slower animation, warmer tones), seed detail pop-up cards (gentle indicator acknowledging the planter is no longer here), and the Gardener tab status display. The system needs a planter_status field (alive/deceased) to trigger the right language. This connects to HW#41 (notification system design) and ux-bloom-reveal.html. Needs its own copy + UX design session. Added 04.12.26.
🔨 Build Session
✍️ Ashley + Claude · Copy + UX design
● Not started — needed before Legacy vault ships
62
Abuse Prevention — Unwanted Vault Rejection / Sender Blocking
ProductSafetyUXLegal
Someone could create a vault for an ex or someone who doesn't want contact. The notification 'Someone planted something for you' could feel creepy or harassing. Design needed: recipients must be able to reject/block a vault BEFORE seeing content. 'Someone planted a vault for you — Accept / Decline / Block sender.' Declined vaults return to planter with no explanation. Blocked senders can never target that person again. Needs: block list system, notification copy, what planter sees on rejection, legal implications for harassment edge cases. Added 04.12.26.
🔨 Build Session
✍️ Ashley + Claude · Safety + UX Design
● Not started — MUST solve before public launch

Quest · infrastructure-ops

Cloudflare, D1, R2, email workers, security architecture, technical co-founder, navigation systems. · 14 cards

16
Export Mechanics — Individual Download, Bulk Export & Expiring Links
Product UX Infrastructure
Once a seed blooms, recipients should be able to download individual media files (standard, likely free). But what about bulk export? If someone wants to export an entire legacy jar — all the photos, videos, voice notes from their grandmother — that's a different beast. Large vault exports generate significant retrieval costs from cold storage and could be a paid feature. Core mechanics to define: single-file download UX, expiring signed link behavior (the download link should expire — how long? 24hrs? 72hrs?), bulk vault export flow (async job + email link when ready), and whether bulk export is free or paid. Added 04.09.26.
📋 Decision Needed
📋 Product Decision
● Idea — Needs Product Definition & UX Design
🔥
PRIORITY — Security Architecture Brief Full Sweep
🔥 Hot Tech Consultant Doc
The Security Architecture Brief v2 (DandyLine_Security_Architecture_Brief_v2.docx) needs a full sweep to reflect decisions made since it was last updated. Key new areas that likely have implications: the preservation state model (pressed / composting / degraded tiers), shared vault storage economics (one payer, many beneficiaries), the buy-a-jar permanent storage concept, compost notification mechanics, and the volunteer Keeper model. Do not update in isolation — review the full doc first, cross-reference all product notes from 04.07.26 onward, then update comprehensively.
✓ Completed 04.09.26 — Updated to v1.2. Added Sections 5.5 (Buy-a-Jar), 5.6 (Export), 5.7 (Digital Legacy), 6.6 (Keeper Model), payment/billing questions, and export/legacy open questions. Next version (v1.3) should incorporate the cybersecurity consultant's recommendation on which time-lock approach to use (see Homework #34) — this decision directly shapes what the investor narrative can claim about cryptographic enforcement. Also needs a sealed-content moderation framework section: how does DandyLine handle content review when vaults are cryptographically sealed during the lock period (delayed detection window)?
34
Time-Lock Cryptography — Architectural Decision
Tech Security Infrastructure
How DandyLine enforces time-locked content — so that even DandyLine itself cannot open a seed before its scheduled bloom — requires an architectural decision with serious moat implications. Three options: (1) Third-party escrow — seed encryption keys held by a neutral third party, released at scheduled time. Simple to implement, introduces a trust dependency. (2) HSM (Hardware Security Module) — a physical enterprise device manages key release on schedule. High security, high cost, used by banks and payment processors. (3) Smart contract — a blockchain-based contract holds release logic in publicly auditable code. Trustless, but adds Web3 complexity and infrastructure overhead. The choice affects the security architecture brief, the investor narrative ("even DandyLine can't open your seeds early" is a strong moat statement if it's architecturally enforced), and the cost model. Foundational decision — needs technical advisor input before building. Migrated from coaching dashboard 04.09.26.
🤝 Needs Outside Help
🤝 External Action
● Needs technical advisor input — architectural decision with moat implications. Note: a new moat card has been added to biz-investors.html calling out the time-lock as a competitive differentiator (currently marked "In Design"). Once the consultant recommends an approach, update both the Security Architecture Brief (v1.3) and the investor moat card to reflect the confirmed architecture. Updated 04.10.26.
36
Technical Co-Founder / First Engineer — Hiring or Partnership
Business Team Priority
Every open technical item on the homework board — time-lock cryptography, GDPR selective deletion, the full build roadmap — ultimately needs a person to build it. The MVP can be constructed with Claude/AI assistance as a PWA, but the path from family MVP to public product at scale requires a technical lead who can own the architecture. Options: (1) Technical co-founder — equity-based, permanent partnership; ideally someone with consumer app experience and some background in media storage or security. (2) First engineer hire — post-pre-seed, transactional but clearly scoped. (3) Fractional CTO — part-time advisor available during MVP phase to make key architectural decisions, then steps back. Investors at pre-seed stage often want to see a technical lead or at least a credible technical plan — worth having someone in place before the round closes. Entry paths: wedding tech founders (warm via guest book vault angle), Alzheimer's/memory wellness founders, consumer app accelerators, YC network. Migrated from coaching dashboard 04.09.26.
🤝 Needs Outside Help
🤝 External Action
● Strategic priority — needed before public launch and pre-seed close
39
Pre-Build Step 00 — Account & Infrastructure Setup
MVP Build Priority In Progress
✅ DECISION LOCKED (April 12, 2026): Stack is now Cloudflare-only. Josh (technical advisor) recommended dropping Supabase in favor of Cloudflare D1 + Workers — keeps everything in one ecosystem, stronger architecture at scale. Ashley created Supabase and Resend accounts during this session but pivoted before integrating. Supabase account can be left idle or deleted — no integration was built. Resend account stays — still needed for email delivery (bloom notifications). NEW Step 00 plan: Josh is setting up Cloudflare D1 (database) and wiring wrangler.toml to bind D1 + R2 to the Pages project. The 4 core tables (profiles, vaults, seeds, bloom_schedule) will be recreated in D1 using SQLite syntax. Re-entry point: Josh completes D1 setup → come back to Claude to start writing Workers functions and the planting flow.
🤝 Josh (Technical Advisor) handling D1 + wrangler.toml setup
● In Progress — Waiting on Josh to complete D1 setup
45
File Type & Size Limits — What Can You Actually Plant?
TechnicalR2 StorageSeed Types
The 5 seed types are: photo, video, voice note, written note, and mixed. But the actual technical limits have never been defined. What file formats are accepted? (JPG/PNG only? HEIC from iPhone? MOV from iPhone video?) What's the max file size per seed? What's the max storage per vault? Per account on the free tier vs. paid? These decisions directly shape the R2 storage cost model, the upload UX, and what the Memory Health Bar (HW#12) actually measures. Without them, the storage model can't be finalized and the upload flow can't be built. Added 04.12.26.
⏳ Medium
🤔 Ashley decides · affects pricing + storage model
● Not started — needed before upload flow is built
46
Bloom Delivery Failure — What Happens When a Bloom Doesn't Reach Its Recipient?
TechnicalResendEdge Cases
The happy path: vault blooms → recipient gets email → they open it. But what about failure? The recipient's email no longer exists (typed 15 years ago). The email bounces. The link expires before they click it. For a 10-year bloom, some of these failures are almost guaranteed. Decisions needed: Does the planter get notified of a failed delivery? Is there a retry window? Is there a secondary SMS delivery via Twilio? Is there a recovery URL the planter can share manually? This needs to be designed before the Cloudflare Cron Trigger bloom scheduler is built (Step 7 of the build). Added 04.12.26.
🌱 Deep Work
🤔 Ashley decides · Claude designs recovery flow
● Not started — needed before bloom scheduler build (Step 7)
47
QA Testing Plan — How Do You Verify the Plant-a-Seed → Bloom Flow Actually Works?
QAPre-LaunchTesting
Before any real person uses DandyLine — even a family member — there needs to be a way to verify the full flow works end to end: plant a seed → seal a vault → set a bloom date → confirm the Cloudflare Cron job fires → confirm the email arrives via Resend → confirm the recipient can open the bloom. This is especially tricky because the whole point is a time delay. Plan needed: How do you set a "test bloom" for 5 minutes in the future? Is there a dev mode that bypasses the date lock? What's the checklist? Build this alongside the Cron Trigger step, not after. Added 04.12.26.
⏳ Medium
🛠️ Ashley + Claude · Build alongside Step 7
● Not started — build this alongside the Cron Trigger (Step 7)
50
Cloudflare for Startups — Apply for Free Credits
CloudflareCost ReductionQuick Win
Cloudflare has a Startups program offering free or deeply discounted credits for Pages, Workers, R2 — the exact stack DandyLine already runs on. Applying takes about 20 minutes and costs nothing. If approved, it reduces running cost at scale from ~$50/month to potentially $0 for a significant period. This has been mentioned in strategy notes and then dropped every session. It's a real-world action only — Claude can't apply for you. But Claude can pull up the application and walk you through it. Do this before the MVP launches. Added 04.12.26.
⚡ Quick Win
🔗 Ashley applies · ~20 min · cloudflare.com/for-startups
● Not started — do this any time, ideally before launch
79
Set Up Cloudflare Email Workers — Replace Resend
InfrastructureEmailDecision Locked
DECISION LOCKED: Switching from Resend to Cloudflare Email Workers (~$5/mo). Keeps the entire stack on Cloudflare — simpler billing, fewer vendors, native domain sending ([email protected]). Steps: (1) Set up Cloudflare Email Workers in the dashboard, (2) configure DNS records for sending from dandyline.app, (3) update Josh's API code to use CF Email instead of Resend, (4) remove any Resend API keys/configuration, (5) cancel Resend account if one exists. This is a priority because email verification and password reset already depend on a working email provider.
🎯 Focused Session
🔧 Infrastructure Setup
🔴 Hot Priority — Do Tomorrow
106
Web Contribution Security Research — 20-Min Learning Task (Priority 5)
Product Security Research Workbook Priority
Guests contributing to a vault from a web link (no app download required) is a powerful growth mechanic — but it raises a security question that needs to be understood before building. This is a learning task, not an implementation decision yet. Estimated time: 20 minutes.

Research task: How do these platforms handle temporary/timed access to sensitive content?
Dropbox — how do shared links expire? How is content protected between upload and access?
WeTransfer — content is available for 7 days then gone. How is it secured in the window?
Signal — disappearing messages. What's the encryption model?
Proton Mail — end-to-end encrypted email. How does a non-Proton user receive a message?

Questions to answer after research:
— How would you technically ensure a seed is inaccessible until a future date?
— Is server-side decryption safe, or should decryption happen client-side?
— If a guest contributes a photo via web, how do we prevent it from being extractable before bloom day?

Why this matters: The web-contribution flow (Idea 3 from the April 18 session) is high-value for growth but needs a sound security model before Ashley commits to building it. Understanding how established platforms solve this will inform whether DandyLine can do it cleanly or whether it's too risky for v1.

Note: this research is the prerequisite for any decision on Idea 3 (Web-Based Contributions). Do not design or build the feature until this is done.
⚡ Quick Win · ~20 minutes
🔍 Research Task
● Not started — prerequisite for Web Contribution feature decision

#112 — Main Nav Consistency Sweep Across All Pages

Thinking Ashley High · Quick Quest #17 · Infra & Ops

Every page in the DandyLine folder has its own nav, and they're inconsistent — different logos, different icons, different menus, some still reference pages meant to stay hidden. Sweep the ~40 pages into one canonical nav so the experience is consistent regardless of which page you land on first.

What's Next
  • Define the canonical nav spec (menu items, logo mark, favicon, sticky vs scroll, mobile hamburger behavior)
  • Audit current nav state on all pages — capture variations
  • Apply the canonical nav to every page in one sweep
Highlights
  • Done: Founder Tools dropdown pruned from site-landing.html (2026-04-22)
  • In progress: Nothing yet — card just raised
  • Must honor: Pages hidden from one nav must not be linked in any other page's nav either
  • Must honor: Real logo + real app icon in the header (not placeholders)
  • Depends on: Quest #12 Brand Sweep & Vocabulary (if logo/icon variants aren't final), Quest #17 Infrastructure & Ops
  • See also: Decision #11 (homework-card-is-the-project-hub) — nav discipline follows from that decision
Working Pages
Notes — Ashley's ask (verbatim, trimmed)

"The main NAV — it's so different depending on what page you land on. We need the actual logo and the actual app icon in the header. Then the nav menu needs to be consistent regardless of the page you're on, and NOT include things that are hidden from that nav. Every single page still has some kind of header on it. If this is a really big ask, reserve it and do it later — just make it a quick thing we can figure out later. Add it to the homework list as a priority — a quick priority we can get cleaned up so it'll be accurate moving forward and locked in."

Scope

~40 HTML files in the working folder. Each has its own nav. Inconsistency is cross-page: logo variants, menu items, icon presence, mobile behavior all differ.

Approach when executing

(1) Lock the canonical nav spec as a single source of truth (document in this card's History or in CLAUDE.md). (2) Audit current state and capture variations. (3) Build a reference nav component (HTML snippet + CSS) that every page uses identically. (4) Sweep-edit each page to replace its nav block with the canonical one. (5) Verify every nav menu item is launch-ready — remove any links to hidden/draft pages.

Guardrails

Nav discipline per Decision #11: scratch pages are NOT in any nav. Working Pages + Command Center + Finder cover their access.

History
  • Raised by Ashley during Phase A.2 hub pivot session. Tagged high-priority / quick. Execution deferred to a later session.

#137 — Founder Decision Tree · 30-Day / 6-Month / 12-Month / 24-Month Actions

Parked Ashley Medium Quest #17 · Infra & Ops

The near-term founder action roadmap — what to do in the next 30 days, 3–6 months, 6–12 months, and 12–24 months. This was written in March 2026 as a reference checklist; many items are now in progress or complete (e.g., waitlist launched). Preserved here for horizon-checking during Phase B.

What's Next
  • Cross-check current status against the 30-day list next session — most items are in-flight or superseded. Keeps as a sanity-checklist card.
Highlights
  • Done since March: Waitlist launched · Landing draft live · MVP build in motion · Investor narrative maturing
  • In progress: Emotional validation interviews (ongoing) · Cost modeling · Technical architect engagement (Josh Peña)
  • Still open: Pricing sensitivity tests · Investor relationship warming
  • References: Source was biz-dev-notes-strategy.html (retiring Apr 22, 2026)
Working Pages
Notes — Full 4-horizon checklist

Next 30 Days

  • Conduct emotional validation interviews (30–50 users)
  • Refine core narrative and category messaging
  • Explore naming / trademark consultation
  • Draft landing page concept privately
  • Build simple UX wireframes
  • Cost modeling with financial partner

Next 3–6 Months

  • Launch waitlist quietly
  • Create prototype demo video
  • Test pricing sensitivity
  • Identify fractional technical architect
  • Begin investor relationship warming

Next 6–12 Months

  • Raise pre-seed funding
  • Build MVP with lean engineering support
  • Run private beta
  • Measure retention signals
  • Begin category storytelling content

Next 12–24 Months

  • Public launch
  • Introduce premium storage tiers & seed packet marketplace
  • Expand emotional growth loops
  • Strengthen brand authority in emotional storage category

Founder Emotional Sustainability

Create a personal operating rhythm for long-cycle emotional product building, including validation milestones and mental resilience planning. Memory and legacy products require sustained emotional presence from founders.

History
  • Migrated from biz-dev-notes-strategy.html (lines ~866-909, plus Founder Sustainability section).

#167 — Cards Rendering as Stretched Columns (Phase C-3 Side Effect)

Thinking Ashley High UX · Homework Page

After the 4/25 Phase C-3 regroup-by-Quest, cards in low-population Quests (Sound Design = 1 card, Bloom Day Ritual = 1 card, Military Families = 1 card, Post-Launch Support = 2 cards) stretch to full row width because the .hw-grid uses grid-template-columns: repeat(auto-fill, minmax(300px, 1fr)). The 1fr tells leftover space to stretch single cards across the whole container. Result: cards look like columns, not cards. Likely fixes: (a) cap individual card max-width (e.g. max-width:380px), (b) change 1fr to auto on Quest sections, (c) use justify-content:start. Pick whichever preserves the multi-card layout for big Quests (Family MVP 18, App Design System 16) without stretching small ones.

What's Next
  • Inspect grid behavior on quest-sound-design (1 card), quest-app-design-system (16 cards), quest-family-mvp-build (18 cards) to see the stretch range
  • Try max-width:380px on .hw-card OR change grid-template-columns when section has < 3 cards
  • Verify the fix doesn't break the Build Roadmap tab cards (different grid)
Highlights
  • Origin: Raised by Ashley 4/25 during EOD spot-check after Phase C-3 regroup deployed.
  • Caused by Phase C-3 regroup. Pre-regroup, cards lived in big chronological sections that always had enough cards to fill rows.

#168 — Audit "What to Start Next Session" Summary — Does It Stay Updated, Is It Useful?

Thinking Ashley Medium UX · Homework Page

Ashley flagged 4/25: she's not sure whether the "What to start next session" persistent re-entry note actually updates session-over-session, and whether it provides real value vs noise. Need to: (1) find the widget on the homework page, (2) trace its data source — is it manual content, or auto-generated from BUILD-RESUMPTION-NOTES.md, or wired to data-status changes?, (3) decide: keep + ensure updates flow, or delete in favor of just relying on BUILD-RESUMPTION-NOTES.md.

What's Next
  • Locate the "What to start next session" markup in biz-dev-homework.html (referenced near line 579)
  • Read its current content vs what BUILD-RESUMPTION-NOTES.md says
  • Decide: keep widget + automate sync, OR retire the widget
Highlights
  • Origin: Raised by Ashley 4/25 during EOD spot-check after Phase C-3 regroup deployed.
  • Ashley's instinct: if it's not actually updated, it's misleading. Better to delete than maintain a stale signal.

#169 — Audit "Next 5 Priority Cue" + Paused Widget — Are They Wired and Updating?

Thinking Ashley Medium UX · Homework Page

Ashley flagged 4/25: same concern as HW#168 — does the "Next 5 Priority Cue" widget at the top of the homework page actually pull live data, or is it static placeholder content? CSS for .hw-next5 exists (collapsed-by-default, well-styled) and a sage-themed twin .hw-paused for "Paused · Ready to Resume." Need to: confirm JavaScript is wired to actually filter cards by data-priority="high" + data-status="thinking"/"spec-ready" for Next 5, and data-status="parked" for Paused. If wired but not rendering — fix. If not wired — wire it. If actively unused — retire.

What's Next
  • Open homework page in browser, expand both widgets, see what they show
  • Cross-reference what they show vs what should be there based on data-* attributes
  • Find the JS that should populate them (look for hw-next5-list, hw-paused-list manipulation)
  • Either fix the wiring or document them as unused and retire
Highlights
  • Origin: Raised by Ashley 4/25 during EOD spot-check after Phase C-3 regroup deployed.
  • Both widgets get prime real estate at top of page — they need to be either functional or gone.

#170 — Fix Broken View Toggles on Homework Page

Thinking Ashley High UX · Homework Page

Ashley flagged 4/25: the "VIEW" toggles on the homework page don't work yet. Need to identify which toggles she means (likely the lens-and-priority chips at top, or the tab-switcher between Homework/Build Roadmap), find the JS that should drive them, and fix or build the missing wiring. Could be that they were scaffolded in Phase A but never finished.

What's Next
  • Open page, click each toggle/chip, observe what works and what doesn't
  • Compare expected behavior (filter cards, change view) vs actual
  • Likely fix is in the JS at the bottom of the file — find the click handlers and verify they hit the right selectors after Phase C-3 restructure
  • The Quest restructure may have invalidated assumptions about card location selectors
Highlights
  • Origin: Raised by Ashley 4/25 during EOD spot-check after Phase C-3 regroup deployed.
  • Phase C-3 moved cards into quest-{slug} sections. Old JS that selected by #planted-* sections will be stale.

#171 — Build Top-of-Page Tracker: HW Completed/Week + Quest Progress Bars

Thinking Ashley Medium UX · Homework Page

Ashley's ask 4/25: build a tracker at the top of the homework page that shows (1) number of HW items completed per week (momentum signal), and (2) progress bar(s) per Quest showing how many cards are bloomed/done vs in-progress vs thinking. Ashley thought we may have done this already — check the coaching dashboard (biz-dev-coaching-dashboard.html) for any existing per-Quest progress visualization that could be ported. If it exists there, port it to homework page top. If not, build fresh: 23 small horizontal bars, each segmented by data-status (thinking / spec-ready / designed-built / bloomed / parked) with bloomed counted as "done."

What's Next
  • Check biz-dev-coaching-dashboard.html for any existing per-Quest visualization (Ashley suspects we did this somewhere)
  • If exists: port to homework page top, replacing or augmenting current widgets
  • If not: build a horizontal bar per Quest, segmented by status, with completed-this-week badge above
  • Wire to data-* attributes so it auto-updates as cards change status
Highlights
  • Origin: Raised by Ashley 4/25 during EOD spot-check after Phase C-3 regroup deployed.
  • This is the "feels less impossible" signal Ashley wants — visual progress proof, not just a 161-card list.

#172 — Better Quest Navigation — TOC / Jump-To / Sidebar to Reduce Scrolling

Thinking Ashley High UX · Homework Page

Ashley's ask 4/25: with 22 Quest sections now stacked vertically, navigating to a specific Quest requires lots of scrolling. Need a navigation aid — options: (a) sticky sidebar TOC listing all 23 Quests with anchor links to each #quest-{slug}, (b) a horizontal Quest-jumper bar at the top with chip per Quest (like Apple Music genre chips), (c) command-K search to jump to any Quest. Recommend (a) sticky sidebar TOC for now — fast to build, persistent, doesn't hide behind another interaction. Each TOC item shows Quest name + card count + dot indicator for "has a high-priority item."

What's Next
  • Build sticky sidebar TOC (left side, ~200px wide, collapses on mobile)
  • Generate from data-quest values automatically; show card count per Quest
  • Smooth-scroll to anchor on click; highlight current Quest as user scrolls
  • Add subtle dot indicator for Quests with at least one data-priority="high" + data-status="thinking" card (the "needs attention" signal)
Highlights
  • Origin: Raised by Ashley 4/25 during EOD spot-check after Phase C-3 regroup deployed.
  • Direct consequence of the Phase C-3 regroup. Made the page Quest-organized but didn't add the navigation infrastructure to match.
200
Working folder hygiene — pending archives & stale doc audit
Housekeeping File Hygiene
Two small housekeeping items captured 2026-05-02 from the cleanup session. **(1) Moleskin folder pending archive:** The "Moleskin Journal App - Screenshots for Ideas/" folder is gitignored and currently in active use by Ashley in a parallel session. When that session wraps, move the folder to ARCHIVE/ via the normal flow (copy first, then delete original after explicit go-ahead). **(2) Stale RESUME doc audit:** RESUME-2026-04-25-CONTINUE-GLOBE.md is conceptually stale — it claims V2-FAITHFUL is "the current active globe build" but the project is now on V4. Sweep all RESUME-* docs for similar staleness; update each to point at current state OR move outdated ones to ARCHIVE with a SUPERSEDED- prefix. Inventory first via `find . -maxdepth 1 -name "RESUME-*"`. Re-entry point: open this card, run the find command, decide per-doc whether to update or archive. Added 2026-05-02.
⚡ Quick Win
⚙️ Infrastructure & Ops
● Idea — Not blocking, address when convenient

Quest · ux-app-integration

Cross-app UX consistency, mobile sweeps, nav systems, sealed vault states. · 6 cards

07
Visual Concept Mockup — Rebuild v5 Into Final Interactive Prototype
Product UX Design Interactive
ux-mockup-reference.html (Visual Concept v5) is a strong reference starting point — 7 screens showing the full planting flow arc. Key elements worth keeping: button patterns, seed depth layers (Near / Mid / Far), vault-opening sphere, and the flow from Home Timeline → Vault → Content Type → Vault Selection → Bloom Timing → Sealed Confirmation. Needs a rebuild using current design decisions, updated vault types, and in-vault dandelion rendering (in-vault style from product-vaults.html). Reference the existing file, don't start from scratch.
🔨 Build Session
🎨 Visual / UX Design
● Reference file exists (ux-mockup-reference.html) — Needs design refresh & rebuild
43
Sealed Vault State — What Does a Gardener See While a Vault Is Waiting to Bloom?
UXSealed StateVisual Design
The bloom reveal has been designed (ux-bloom-reveal.html). The planting flow is being designed. But the in-between state — a vault sealed and waiting — has no UX. When a Gardener visits a sealed vault before it blooms, what do they see? A countdown? A visual of the sealed jar? Can they still add seeds? Can they peek at what they planted? Can they un-seal it? This middle state is where users will spend the most time (months or years), and it's currently blank. The visual language for "sealed but not yet bloomed" needs to be designed before the vault UI is built. Added 04.12.26.
⏳ Medium
🎨 Ashley + Claude · Visual + UX design
● Not started — needed before vault UI build
66
Seed Key Management UX — Preventing 'Too Many Keys' Overwhelm
UXGardenerSeed Keys
Power users (grandparents with many grandchildren) could end up managing a LOT of Seed Keys. If the Gardener tab becomes a wall of codes and statuses, it loses the emotional magic. Design principle: group keys by vault, not by individual key. Show the people, not the codes. 'Emma — Invited, waiting to join' is better than 'SK-7X9K2M — status: invited.' The key is a backend mechanic; the human is what the Gardener sees. Needs: Gardener tab information architecture, grouping logic, search/filter for heavy users, mobile-friendly card layout. Added 04.12.26.
🔨 Build Session
✍️ Ashley + Claude · UX Design
● Not started — needed before Gardener tab ships
78
Gardener Profile System — Setup, Stats, Discoverability
ProductUX
Full gardener profile system. Includes: photo, "gardening since" date, stats (# vaults, # planted seeds, # received seeds). Editable display names (Snapchat-style — "Granny" instead of "Judy Dobbs"). Shared vaults view. Quick-action prompts: plant a seed to this person, add them to a vault, build a vault with them. First-time setup: determine required vs. optional fields (keep it minimal for invited users). Discoverability: default to discoverable? Private option? If private, how are they found — by code only? Consider badges/levels based on contribution (future). Ashley wants guidance on what profile stats should be public vs. private vs. user-choice.
🧠 Deep Project
📋 Product Decision
● Idea — Needs Development
87
Nav/Menu System — Redesign, Shared Component, Status Rules, Hidden Founder Zone
Design SystemInfrastructureUX
Every time a new HTML page gets built, the nav/menu formatting drifts — nav placement, logo position, founder FAB, footer links all render slightly differently across pages. This is a sprawl problem that compounds silently. A proper design session is needed to: (1) Design mobile + desktop nav side-by-side — lock logo placement, primary nav structure, secondary/dropdown items, bottom-right widget behavior, footer. (2) Build a shared nav component — likely a `brand-nav.js` include (pattern modeled on `brand-icon.js` / `brand-shared.css`) so each page renders nav from one source of truth; changes propagate everywhere. (3) Two nav modes from one component: PUBLIC nav (visitors see — product-*, brand-*, site-landing, biz-investors, biz-mktg-founder-story) and FOUNDER nav (Ashley/Josh/Adam internal — biz-dev-*, biz-legal-counsel, biz-competitive-landscape, homework, dashboard, command center). (4) Status system for in-progress pages — data-status attribute on links (`live` / `in-progress` / `vision-board` / `coming-soon`) rendered with a DandyLine-branded badge like "Vision Board — growing" instead of generic "Coming Soon". Pages stay viewable in their natural habitat on mobile + desktop even when rough. (5) Hidden founder zone — LOCKED April 18, 2026: the hidden zone is called **Greenhouse** (on-brand — where things grow before they're ready to bloom). Unlinked URL `dandyline.app/greenhouse` that only Ashley/Josh/Adam bookmark; houses all `biz-dev-*` internal pages; tagged `noindex` so search engines skip; public nav never references it. Optional future: keyboard shortcut "secret handshake" (Cmd+Shift+D) on public pages reveals hidden founder links. (6) Consistency rules for CLAUDE.md — add to session-start protocol: "If this session touches any HTML page, check it uses shared nav include before closing." Add a rule: "Never hand-copy nav HTML into new pages — always use the shared component." (7) Sweep existing HTML files to standardize once the component is built. Critical blocker to resolve before the nav diverges further. Coordinates with HW#69 (Button Design System) — both are design-system consistency work that should share a session arc.
🧠 Deep Project
🎨 Design System
● Idea — Proper Design Session Required Before Building
88
Mobile Viewport Sweep — Remaining UX Prototype Files
UXMobileCSS
April 18 session: patched `ux-field-homepage-v3-motionmark-depth.html` and `ux-roots-arrival.html` with an `@media (max-width: 419px)` rule that collapses the decorative phone-frame mockup into a fullscreen layout on real phones — fixes the stat-counter cutoff and general overflow on narrow viewports. `ux-planting-flow.html` was checked: it's a documentation page (max-width:1200px), no cutoff bug. Remaining `ux-` and `product-` files that use a phone/frame mockup pattern should get the same treatment so Ashley can view everything in its natural habitat on mobile. Files to audit: `ux-bloom-reveal.html`, `ux-vault-flow.html`, `ux-button-system.html`, `ux-button-decisions.html`, `ux-component-decisions.html`, `ux-filter-decisions.html`, `ux-mockup-reference.html`, `ux-style-guide-draft.html`, `ux-reference-key-moments.html`, `product-dandelion.html`, `product-seeds.html`, `product-vaults.html`, `product-roots.html`, `product-seed-keys.html`. Also: SESSION-BRIEF.md referenced `ux-field-homepage.html` but actual filename is `ux-field-homepage-v3-motionmark-depth.html` — update the brief. Goal: one consistent media query pattern that any `ux-` or `product-` file can import from `brand-shared.css` once HW#87 (nav redesign) lands a shared include approach.
🌿 Medium Project
🎨 UX/CSS
● Partial — 2 of ~14 files patched

Quest · marketing-foundation

Revenue model, pricing, attribution, proof points, growth KPIs, premium features, gift vaults. · 10 cards

29
Live Gardener Count — "X Gardeners Are Tending Their Vaults"
Growth Marketing Social Proof
A live counter showing how many gardeners exist in the world. Low technical effort (a single database count query), high emotional and marketing value. Like Kickstarter's backer count — it signals momentum, builds social proof, and makes early testers feel like they're part of something. Could live on: the landing page ("Join X gardeners already tending their vaults"), the founder dashboard (private growth view), or even inside the app as a subtle community signal. Framing ideas: "X Gardeners worldwide" / "X Groves in bloom" / "X seeds planted and waiting." Also consider: a founder-only dashboard view showing gardener count over time (a growth curve), vault count, seeds planted, blooms delivered. This data tells the founder story when pitching. Extremely cheap to build — just a counter query on the users table. Add to the founder dashboard and landing page simultaneously. Added 04.09.26.
⚡ Quick Win
🏗️ Build with Claude
● Quick Win — Low Effort, High Value
48
Waitlist Nurture Sequence — What Do People Receive After They Sign Up?
MarketingResendWaitlist
The waitlist is live and people are signing up. But after they submit, nothing happens — no welcome email, no follow-up, no "here's what's coming." Every person who signs up already felt something, and that moment fades fast if it goes unacknowledged. What should they receive? A welcome email immediately? A second email a week later with the founder story? A "we're getting closer" update when the MVP launches? Resend is already in the stack — the infrastructure is there. This is a writing task more than an engineering one. Write the sequence first, then build it. Added 04.12.26.
⏳ Medium
✍️ Ashley writes · Claude builds in Resend
● Not started — waitlist is live now, every day without this is a missed connection
80
Revenue Model — How DandyLine Actually Makes Money
BusinessRevenuePriority
Define DandyLine's monetization strategy. This decision gates product design (what's free vs. paid), vault size limits, sharing restrictions, and the entire pitch deck financial slide. Explore: (1) Freemium subscription — free tier (3 vaults, text-only) vs. paid ($4.99–9.99/mo for unlimited vaults, photos, video, Grove sharing, custom bloom ceremonies). (2) Storage tiers — free 500MB, paid 5GB/50GB. (3) One-time vault packages — Wedding Vault ($19.99), Baby Time Capsule ($14.99), etc. KEY INSIGHT: one-time packages have massive virality potential — a wedding vault onboards 50-200 guests into DandyLine instantly. Gifting packages ($15 to give someone a vault) might be the best customer acquisition cost you'll ever spend. (4) Enterprise/institutional — schools, hospices, military families, funeral homes, therapists (annual contracts). (5) Marketplace potential — professional "Gardeners" (photographers, videographers) who plant seeds for hire. Consider: which model matches the emotional nature of the product? Subscriptions feel transactional; one-time purchases feel like gifts. Maybe hybrid. Draft a rough model with estimates even if incomplete — Ashley needs something tangible to think through.
🧠 Deep Project
📋 Business Strategy
🔴 High Priority — Key Decision
📎 Merged In · From HW#136 (was: "Monetization Blueprint · Six Revenue Pillars")

Merge reason · Monetization Blueprint Six Revenue Pillars fold into Revenue Model hub. Original card consolidated 2026-04-25.

Description: The six-pillar revenue architecture: Emotional Archive Premium Subscription · Theme & Skin Marketplace · Legacy Protection Plan · Emotional Credit Economy · Physical Product Ecosystem · Storage as Hidden Revenue Engine. Core philosophy: DandyLine doesn't monetize storage space — it monetizes emotional value, legacy security, and memory experience.

Original What's Next:
  • Revenue pillars slide for investor deck. Legacy Protection Plan is the highest-margin future tier worth flagging early.
Original Highlights:
  • Philosophy: "DandyLine does not monetize storage space. DandyLine monetizes emotional value, legacy security, and memory experience."
  • Premium positioning parallel: Life insurance, heirloom services, archival preservation — not typical cloud storage
  • Price points: $8–12/month premium archive · $80–120/year legacy plan · Lifetime heirloom vault options
  • References: Source was biz-dev-notes-business.html (retiring Apr 22, 2026)
📎 Merged In · From HW#092 (was: "Export as a Business Model — Revenue Expansion Deep Dive")

Merge reason · Export as a Business Model is one revenue stream within the Revenue Model hub. Original card consolidated 2026-04-25.

Description: The "save to device" export is just the baseline. The moment someone wants to take their memories out of DandyLine is one of the highest-intent moments in the product — and it's currently walking past a massive revenue opportunity. This item is about mapping every possible export format as a premium product line. Investors want to see this: a simple core mechanic that fans out into multiple high-margin, easy-to-execute revenue streams. THE KEY INSIGHT: Competitors (Artifact Uprising, Chatbooks, Mixbook, Motif, Shutterfly) all work with random photo dumps from camera rolls. DandyLine's content is fundamentally different — already curated, emotionally weighted, time-stamped with meaning, planted with intention. A memory book from DandyLine isn't a photo dump. It's a vault's worth of moments that mattered. That's a premium product at a premium price point. EXPORT OPTIONS TO EXPLORE AND SPEC: 1. SAVE TO DEVICE (baseline, free) — one at a time, DandyLine-branded filename, intentionally vague. Two reasons: (a) brand impression — the name travels into camera rolls and hard drives for years; (b) retention strategy — vague filenames (DandyLine_2026-04-21_photo.jpg, no vault name, no seed title, no metadata) make offline organization inconvenient. The beautiful, organized, navigable version lives in DandyLine — not on their hard drive. This is intentional product design. Do not make exports easy to sort offline. 2. MEMORY VIDEO (premium) — AI-generated montage video from a vault's seeds. Music, pacing, the moments in order. Delivered as a link or download. Think: automated film of your experience. High perceived value, low marginal cost with AI generation. 3. MEMORY BOOK (premium, physical) — Printed photo book with elegant design. QR codes embedded for audio and video seeds that can't be printed. Partners: Artifact Uprising tier quality, not Shutterfly. This is the clearest market signal — people already pay $60-150 for photo books. DandyLine's version is more meaningful because the content is already curated. 4. PREMIUM DIGITAL EXPORT (premium) — A beautifully formatted, shareable digital package. Not a slideshow, but an experience — think an interactive digital booklet or a web-based presentation that plays through a vault like a curated journey. Shareable via link, not a download. Could be the "gift" version — you export your vault as an experience and share the link with the people in it. 5. FRAMED PRINT (premium, physical) — Single seeds printed as art. A voice note gets a waveform print. A photo gets gallery framing. A letter gets typeset beautifully. Niche but high margin. THE EXPORT SCREEN VISION: When someone chooses to export, they see: "How would you like to take this with you?" — Save to device / Create a Memory Video / Print a Memory Book / Share as an Experience. Each option is a separate product with its own price point. The free option is always available; the premium options are the business. COMPETITORS TO STUDY: Artifact Uprising (premium physical), Chatbooks (subscription physical), Mixbook (customizable physical), Motif (Apple-integrated), Canva (digital design), Animoto (AI video). None of them have curated, emotionally-weighted content as their starting point. That's the moat. Done when: Full map of export product categories with pricing model thinking, UX spec for the export screen, investor talking points drafted, and Josh has been briefed on building the export endpoint with extensibility for future product types.

Original Status: ● High Priority — Before next investor conversation

83
Develop Premium Features — Beyond Storage Tiers
ProductRevenueSpawned from Planting Flow
Born out of the April 18 planting-flow session. The Premium tier needs to be more than "more storage" — it should unlock FLEXIBILITY, not AUTHORITY. Seed ideas captured so far: (1) Modify bloom dates on seeds I personally planted (free tier: locked after seal; premium: can shift within same vault up to 3× before bloom); (2) Extra Guardian slots (free: 1 Guardian; premium: up to 5); (3) Cascade rules on Guardian death (premium only); (4) Custom bloom ceremonies / visual treatments; (5) Larger media per seed (video length, photo resolution); (6) Priority support; (7) Early access to new vault types; (8) ADDED 2026-04-27 — Super Lock as a premium feature. Super Lock makes a bloom date permanently immovable (no override, not even by Guardian, not even by the planter themselves once engaged). Powerful for sacred dates ("bloom on her 18th birthday," "bloom the day he marries"). Should be subtle in the UI — not the default — but a meaningful premium upsell that maps directly to emotional commitment. Decision: Super Lock = premium-only feature. Spawned from HW#53 sub-decision (c) on bloom date editability. CRITICAL GUARDRAIL captured in the planting-flow doc: Premium never overrides consent layers — a premium subscriber CANNOT modify a co-planter's seed or a recipient's pre-locked date. Premium = "more flexibility inside your own authority," never "more authority over other people's seeds." This principle is the emotional backbone of the product and must hold across every pricing decision. This card pairs with HW#80 (Revenue Model).
🧠 Deep Project
📋 Business Strategy
● Idea — Needs Development
197
Jar Preservation as a Paid Feature — Pressing the Whole Vault
Business Pricing Storage Model Spawned from HW#56
Spawned April 27, 2026 from HW#56 (Generational Forwarding). Pressing one seed at a time is well-defined. But pressing or "buying" an entire jar — preserving the full vault as a single object with extendable storage — is a real product question that hasn't been priced yet.

The core question: Should DandyLine offer "jar preservation" as a distinct paid action — separate from per-seed Press? The use case showed up in the HW#56 conversation: when a planter is gone, the family/recipients should be able to preserve the entire vault as one preserved object, not just individually press their favorite seeds. Anyone willing to pay for it storage-wise should be allowed to.

Pricing model possibilities to evaluate:
1. One-time jar preservation purchase — pay once, vault is preserved with a max storage cap. Members can extend the cap by paying for more storage.
2. Subscription extension — preserved jars stay alive as long as a subscription continues. Lapses = jar enters Composting.
3. Hybrid — base preservation is one-time fee; storage cap extension is per-GB or subscription.

Why this matters: The "one-press-for-all" rule (any member can press a seed, protected for everyone) is a named USP. Jar preservation is the natural extension — one member can pay to preserve the whole vault for everyone. Same emotional + business mechanic at vault scale: the family member who cares most becomes the natural subscriber. Tie this directly into HW#91 (One-Press-For-All USP Documentation) — jar preservation should be the second name-callout after one-press.

Where this lives: Add to HW#80 (Revenue Model) as a candidate revenue stream. Add to HW#051 (Pricing Model Spec) as a tier line item. Add to HW#83 (Premium Features) as item (9) once the format is locked.

What this card needs: pricing model decision (one-time vs subscription vs hybrid) · storage cap defaults per tier · UX for the "preserve this jar" prompt (should appear in the right emotional moments — vault bloom, member memorial, archival) · membership signal (who paid? does that show in the vault somehow?).

Added 2026-04-27.
💜 Decision
🤔 Pricing decision · ties to revenue model + USP framing
● Idea — needs pricing model decision before adding to HW#80/#051/#83
91
One-Press-For-All + Storage Model — Investor USP Documentation Sprint
InvestorMarketingProductCopy
Two of DandyLine's strongest differentiators are currently buried in internal notes and need to be surfaced as named, articulated USPs — in the investor page, brand guide, and eventually consumer-facing copy. 1. ONE-PRESS-FOR-ALL: In a shared vault, one member pressing a seed preserves it for everyone with access. No one else needs to pay. "When someone in your vault preserves a memory, it's safe for everyone who shared it. One press. Protected for all." Investor angle: creates organic, emotionally-motivated upgrade behavior — the family member who cares most becomes the natural subscriber. No dark patterns. Needs: named feature callout in product-seeds.html, investor talking point in biz-investors.html, and eventual consumer-facing explainer copy. 2. THE GIANT VAULT MOMENT: When a large vault blooms all at once and tips a user over their storage cap, the upgrade prompt appears at an emotional high — they just experienced something meaningful and have a genuine reason to want to keep it. This is upgrade pressure through emotional stakes, not algorithmic manipulation. Needs: investor talking point, UX spec for the storage-cap prompt experience, copy for the "you're running low" notification. 3. STORAGE MODEL (locked April 21): Everything bloomed stays alive until storage cap is hit — not on a time clock. Free tier = smaller cap. Paid = more room. Upgrade prompt: "Your garden is getting full. Want more room?" This model needs to be reflected in product-seeds.html, the brand guide pricing section, and the investor page. Done when: all three are documented in biz-investors.html as investor talking points + product-seeds.html as feature specs + copy candidates in biz-mktg-copy-vault.html.
🌿 Medium Project
📣 Marketing / Investor
● High Priority — Do before next investor conversation
97
Gift Vault — Buy a Pre-Configured Vault as a Gift
Strategy PMF Business Model Growth
Short Years sells their app as a gift ("get this for the new parents"). Kept Collection sells a $59 physical baby book as a gift. DandyLine's version: buy a pre-configured vault as a gift — "Here's a 'First Year Baby Vault' — ready for you to start planting, blooms on their first birthday." The purchaser pays, configures the vault type and bloom date, and sends a gift link to the recipient who activates it. The recipient immediately has a beautiful, pre-named vault with a meaningful bloom date — zero setup friction. Gift Vault is the lowest-friction acquisition channel DandyLine has: (1) buyer joins to give, (2) recipient joins to receive, (3) family plants together = instant Grove behavior. Pricing anchor: a $19.99 "Baby's First Year Vault" or $14.99 "Anniversary Vault" gift is a genuinely thoughtful present — and it costs less than a photo book. Needs: gift flow UX, pricing tiers, vault template configurations per gift type, gift message (physical card or digital), fulfillment (email delivery). This pairs with HW#60 (Seed Key as Physical Product) — a physical gift card variant. Added 04.22.26.
🔨 Build Session
💰 Business & Revenue
● Idea — Needs Development
100
Investor Comparison Story — "All These Products, One App"
Strategy PMF Investor Marketing
The competitive landscape research surfaced a powerful investor narrative that needs to be developed into a slide and pitch moment. The story: parents today are spending real money across multiple products to solve ONE problem — preserving their children's lives and memories. They might buy: Kept Collection ($59 baby book), The Short Years ($89 annual package), HappyMe Journal ($22 wellbeing journal), Little Life Stories (subscription), Artkive ($75 art book). That's $250+ in one-off purchases per year, none of which talk to each other, none of which are digital-first, and none of which have a time-capsule layer. DandyLine is all of these in one app — and it grows with the child from birth to 18 (and beyond). The investor ask is not "why DandyLine vs. Google Photos" — it's "why pay for 5 products when one app does everything those products do, plus the thing none of them do (bloom delivery, time-delay, cross-family contribution)." This should become: (1) an investor slide showing the fragmented product landscape and DandyLine's consolidating position, (2) a pitch moment where Ashley names the products and prices out loud — "parents today are spending over $200 a year across apps and books that don't connect. DandyLine is the one place that replaces all of them", (3) a "problem slide" companion to the current investor deck. Needs: competitor price mapping table, slide design, pitch language rehearsed. Added 04.22.26.
🔨 Build Session
📣 Marketing / Investor
● Idea — Needs Development
105
Growth KPI Definition — Pick ONE Metric for Multi-Seed Vaults (Priority 4)
Business Growth Strategy Workbook Priority
When multi-seed vaults launch, one metric should tell you whether the feature is working. Pick ONE from these five candidates and define a specific target:

1. % of vaults created with 2+ seeds — measures immediate adoption of the multi-seed feature
2. Avg time spent organizing/curating a vault — measures engagement depth (higher = more invested)
3. Repeat organizers (created 2+ vaults) — measures retention and habit formation
4. Guest conversion to app download — measures viral loop effectiveness (does multi-seed bring in new users?)
5. Guest conversion to own vault creation — measures full funnel (from recipient to creator)

The exercise: Pick one. Then define a target with a timeframe. Example format: "30% of vaults have 2+ seeds within the first 90 days of launch." Without a specific target, you can't know if the feature is working or just being politely ignored.

This is a ~20 minute decision session. Bring it to Adam — his financial analysis background is exactly right for this kind of metric definition.
⚡ Quick Win
📋 Business Decision · Good for Adam
● Reframed April 26 — Track all 5 signals from day one. Revisit when revenue model is clearer to promote the strongest to the investor narrative.
173
Build biz-why-dandyline.html — The Hidden Genius List
Investor Marketing New File
Create a dedicated living page for every moment where DandyLine's design serves a brilliant, non-obvious business or investor purpose. Each entry: the feature or decision · why it's brilliant · one tag (Moat · Virality · Cost Discipline · Retention · Investor Signal · Product Truth). Triggered any time Ashley says "add this to the investor list" or "add this to the why DandyLine list" — Claude appends immediately, same session. File goes in MASTER folder, added to Dashboard Sweep, linked from biz-investors.html and Command Center TOC. Decided April 26, 2026.
🔨 Build Session
🏗️ Build with Claude
● Not started — build the file before next investor conversation
174
First Population Pass — Pull All Scattered Investor Wins Into biz-why-dandyline.html
Investor Marketing Consolidation
Once the file is built (HW#173), do a one-time sweep to pull all existing "investor value prop" moments scattered across QUESTIONS-FROM-ASHLEY.md, biz-dev-homework.html, and session notes. Known entries already waiting: export filename as brand touchpoint · storage upgrade at emotional bloom moment · one-press shared vault preservation · Cloudflare startup program timing · 5 growth metrics tracked from day one · parents spending $250+/year on fragmented products (HW#100). Blocked by HW#173.
🔨 Build Session
🔍 Consolidation Pass
● Blocked — waiting on HW#173 (build the file first)
194
Adam Onboarding · Build the DandyLine Financial Roadmap
Adam Business Revenue Pricing Onboarding
Adam takes lead on building DandyLine's financial roadmap — the path from pre-revenue indie startup to a real, profitable, sustainable business. The Apr 24 audit confirmed DandyLine is going indie/bootstrapped (not VC-track), so the work here is bootstrap business modeling, not pitch-deck math. This card is also Adam's entry point into using Claude for the first time. Claude can walk him through every step below; he just needs to ask out loud.

Goal: a defensible financial roadmap that answers (a) what DandyLine needs to gross to be a sustainable business that supports a full-time founder, (b) the realistic path to that number across Year 1 / Year 2 / Year 3, and (c) which milestones change the cost stack (Josh's eventual compensation, legal, infra scaling, marketing spend, contractors, taxes). Final output: a 3-scenario financial model (conservative / base / aggressive) plus a recommendation on entity structure.

Why this is priority: right now every revenue conversation is operating on industry-shape extrapolations, not validated numbers. Until the foundation pieces below are real, any operating plan is a vibe with numbers attached. Adam is the right owner because the judgment calls — entity structure, compensation philosophy, the cost-stack reality, household-level financial planning — are his domain. Ashley + Claude work alongside; Adam leads.

Do these in order — top-down math is fiction until ①–③ are done:
① Real Competitor Pricing Audit
Pull actual pricing pages and tier structures for the named competitors. Replace every "industry-shape extrapolation" with real data. Targets: Orca, Heritance Digital, Capsuler, Tripple, TimeLock, Storyworth (now under Ancestry), Chatbooks, Journey-the-app, Short Years, Kept Collection, Artkive, HappyMe Journal, Little Life Stories. For each, document: monthly price, annual price, free-tier scope, paid-tier features, any one-time / lifetime pricing, storage limits, household-account pricing if any. Output: a pricing comparison table that lives in the financial model. Claude can do the research and pull screenshots; Adam reviews and identifies the patterns. Unblocks every downstream math conversation.
② Freemium Boundary Decision
What does free DandyLine do, what does paid unlock? Right now the boundary isn't locked — and every subscription number is fiction without it. Principle to start from: free has to be enough that someone tells a friend about it; paid has to unlock something a Gardener craves after they've felt the magic of a bloom. Pairs tightly with HW#80 (Revenue Model — existing draft) and HW#83 (Premium Features — already sketched: bloom date flexibility, extra Guardian slots, custom ceremonies). Adam's judgment matters here on what "valuable enough to pay for" looks like in adjacent subscription categories. Output: a one-page free-vs-paid feature split with reasoning, locked.
③ Willingness-to-Pay Validation
One real conversation beats any spreadsheet. Pick 3–5 plausible target Gardeners from Ashley's network or Adam's. Walk them through what DandyLine will be at MVP launch (live waitlist, Phase 1 build at ~55–60%, plant-a-seed and bloom flow imminent). Ask: "Would you pay for this? At what price would it feel right? What would feel like a rip-off?" One real "yes, $X" rewrites the pricing model. Pairs with HW#37 (Concierge testing — same human research surface, different question). Claude can draft the interview script + a clean response template; Adam and Ashley do the actual conversations. Output: at least 3 documented WTP conversations with quotes.
④ Build the Financial Model
Once ①–③ are real, build a 3-year financial model with three scenarios (conservative / base / aggressive). Inputs: pricing (from ② + ③), conversion rates (free→paid funnel), retention curves, full cost stack (legal, Cloudflare infra, Resend, marketing, Josh's future compensation, eventual contractors, payment processing, taxes). Outputs: business gross revenue trajectory, cost structure, net trajectory, milestone gates ("at $X MRR, hire support; at $Y MRR, Josh moves to part-time paid; at $Z MRR, founder commitment changes"). Include an entity structure recommendation — re-evaluate HW#41 (Delaware C-Corp assumption) against the bootstrap path. LLC pass-through is likely more tax-efficient now that fundraising isn't on the near-term track; Adam confirms or counters with reasoning.
📚 Adam · Claude Onboarding Reading Order
First time using Claude — load context in this order before starting any work:
1. ASHLEY_SAFETY_RULES.md (DandyLine root folder) — the guardrails Claude follows every session. Plain-English house rules.
2. SESSION-BRIEF.md (DandyLine root folder) — current product state, build stage, scoring snapshot, blockers.
3. CLAUDE.md (MASTER folder) — how Ashley works with Claude: file naming, brand vocabulary (Plant/Seed/Bloom/Vault/Gardener — never upload/folder/user/open), session rituals, the Translator Rule.
4. This card (HW#194) plus the related cards already in this Quest: HW#80 (Revenue Model — existing draft), HW#83 (Premium Features), HW#91 (One-Press-For-All + Storage Model), HW#97 (Gift Vault — already Adam-owned), HW#100 (Investor Comparison Story), HW#105 (Growth KPI — flagged "good for Adam").
5. biz-dev-coaching-dashboard.html — skim the full page, then read the v8 Bootstrap Viability and Financial Reality & Optionality dimensions in detail. The Apr 24 indie pivot context lives there. Full audit notes in DEEP-AUDIT-FINAL-2026-04-24.md.

How to work with Claude: ask questions out loud, walk through numbers together, ask to see the math. Claude does the research, structure, drafting, and spreadsheet skeletons. Adam brings the judgment — what's the right cost structure, what compensation philosophy makes sense, what entity makes sense, what's realistic vs. wishful. Claude will flag any assumption that's a guess vs. a validated number; Adam decides which to push on.
🧠 Deep Project
📋 Business Strategy · Adam intake + Claude onboarding
● High Priority — Foundation for every revenue conversation downstream. Spawned April 27, 2026 strategy session.

#138 — Fundraising Deck Outline & Psychological Adoption Strategy

Parked Ashley Medium Quest #19 · Marketing Foundation

Twelve-slide pre-seed deck outline from opening vision through the ask — plus the underlying psychological adoption strategy (why people adopt memory tools, who the early adopters are, which retention psychology mechanics keep them). Includes the behavior loop (Capture → Plant → Anticipate → Unlock → Reflect → Share → Repeat) and the goal habit: "I need to save this in DandyLine."

What's Next
  • Use as the skeleton when next drafting or updating the investor pitch deck. Pair with HW#107 (Grandparent Legacy) for the emotional opener.
Highlights
  • Core insight: "People do not adopt memory tools for logic. They adopt them for emotional future value."
  • Early adopters: New parents · Couples/weddings · IVF/fertility journeys · Grief & remembrance communities · Journaling/reflection audiences
  • Behavior loop: Capture → Plant → Anticipate → Unlock → Reflect → Share → Repeat
  • Habit goal: Users think "I need to save this in DandyLine"
  • References: Source was biz-dev-notes-business.html (retiring Apr 22, 2026)
Working Pages
Notes — Full deck outline + adoption psychology

Part 1 — Fundraising Strategy Deck Outline (12 Slides)

1. Opening Vision: "Social media archives memories for attention. DandyLine preserves them for the future."

2. The Problem: Memory capture today is performative, disorganized, low-trust, degrading in quality, not designed for future emotional experiences.

3. Cultural Timing: Massive growth in digital photo/video storage. Social media fatigue. Privacy awareness rising. Desire for intentional living and reflection.

4. The Solution: DandyLine = Emotional Storage Platform. Users plant media capsules that unlock in the future for themselves or others.

5. Product Experience: Vaults · Seeds · Bloom moments · Contribution capsules · Memory map roots system.

6. Market Opportunity: Global digital storage market · Creator memory economy · Journaling & wellness tech · Legacy planning / digital inheritance.

7. Business Model: Storage subscription tiers · Premium capsule features · Skin marketplace · Future physical memory exports.

8. Growth Engine: Emotional viral loops · Family onboarding · Milestone lifecycle prompts · Long-term retention design.

9. Competitive Landscape: Cloud storage (utility) · Social media (performative) · Journaling apps (individual only) · Legacy tech (end-of-life focused).

10. Why Now: Technology exists. User psychology is ready. No category leader yet.

11. Founder Advantage: Strategic operations background · Financial modeling support · AI leverage · Early product narrative maturity.

12. Fundraising Ask: Pre-seed $750K–$1.2M · 18-month runway · MVP build + validation + category launch.

Part 2 — Psychological Adoption Strategy

Core Insight: People do not adopt memory tools for logic. They adopt them for emotional future value.

Adoption Drivers: Anticipation psychology (future reward) · Legacy instinct · Family bonding · Life milestone anxiety · Desire for meaning.

Early Adoption Targets: New parents · Couples / weddings · IVF / fertility journeys · Grief & remembrance communities · Journaling / reflection audiences.

Retention Psychology: Countdown mechanics · Emotional notifications · Surprise unlocks · Contribution visibility · Personal archive utility.

Behavior Loop: Capture → Plant → Anticipate → Unlock → Reflect → Share → Repeat.

Network Effect Mechanism: Receiving capsules motivates sending capsules. Family clusters create organic growth.

Category Habit Formation Goal: Users think "I need to save this in DandyLine."

History
  • Migrated from biz-dev-notes-business.html (lines ~557-680) before notes-page retirement.
166
Attribution & Referral Tracking — How Did You Find DandyLine?
Growth Data Onboarding
From day one, capture how every user arrived. This data is invaluable for pitching, fundraising, and understanding growth loops. Three layers to build: (1) Automatic attribution — if someone signs up through a vault invite link, that's tracked automatically (who invited them, which vault). This covers most early users and requires no extra input. (2) Referral links — every gardener gets a unique shareable link (dandyline.app/invite/ashley). When someone signs up through it, the referrer is logged. No relying on user memory. (3) Self-reported at signup — a single optional question: "How did you find DandyLine?" Options: Invited to a vault / Shared by a friend / Founder invite / Saw it somewhere. Keep it one tap, never required. The goal is to know: organic vs. invited, and who the super-sharers are (people like Ashley's sister who could bring in many users at once). Build the invite link system in Phase 1 — it also solves the Grove invite UX problem at the same time. Data to store per user: source (vault_invite / referral_link / direct / self_reported), referrer_id, referral_vault_id, signup_date. Added 04.09.26.
🔨 Build Session
🏗️ Build with Claude
● Build in Phase 1 — Invite Link Doubles as Attribution

Quest · future-products-merchandise

DandyLine Shop, physical products, gift items, print partnerships, Seed Key forwarding. · 5 cards

17
Physical Export & Print Partnerships — Photo Books, Keepsakes
Business Model Partnerships Product
Some users will want to turn a vault — especially a legacy jar or milestone collection — into something physical: a printed photo book, a bound archive, a keepsake. Competitors like Chatbooks and Artifact Uprising do this as a primary business model. For DandyLine this would be an add-on product: "Turn this vault into a photo book." Options are a direct partnership with a print vendor (they handle fulfillment, we handle the content handoff) or a native DandyLine export format optimized for print. Needs: partner research, export format design, revenue model (we take a cut? or flat fee?), and UX for triggering a print order from within a vault. Added 04.09.26.
🤝 Needs Outside Help
🤝 External Action
● Idea — Needs Business Model Definition
19
DandyLine Shop — Additional Purchasable Products Beyond Storage
Business Model Product Revenue
Monetization isn't just storage upgrades. There's a whole category of things someone might want to purchase from DandyLine beyond "more GB": Buy-a-Jar (already defined), bulk export packages, physical photo books, digital estate / legacy planning, gifted vaults, and probably things we haven't thought of yet. The question is whether these live inside the main app experience, in a separate "Shop" or product hub, or as one-off purchase flows triggered by specific moments (e.g., a bloom prompts "Want to turn this vault into a photo book?"). Needs: full map of purchasable product categories, pricing model thinking, UX for how purchases are surfaced (contextual vs. shop model), and how this interacts with App Store billing rules (Apple/Google take 15–30% of in-app purchases). Added 04.09.26.
🧠 Deep Project
💰 Business & Monetization
● Idea — Needs Business Model Mapping
56
Seed Key Chains — Generational Forwarding ✅ DIRECTION LOCKED
ProductSeed KeysLegacyGrowth
✅ Direction locked April 27, 2026. Yes — vaults keep living after the planter is gone. The vault does NOT auto-lock when DandyLine learns the planter has died; that would create a weird emotional moment ("you don't want DandyLine to know they died because then it'd lock").

The principle: A Hatch family Legacy vault that Grandma built shouldn't shut down because Grandpa is gone. If anyone in the vault wants to keep adding to it, they should be able to.

Locked decisions:
1. Vault keeps living after planter death. No auto-close, no auto-lock. Family/recipients/Guardians can continue interacting with the vault.
2. Default Guardian inheritance pattern still applies. If a Guardian is named, the Guardian receives oversight when the planter is gone (already locked in Section C of QUESTIONS-FROM-ASHLEY.md). If no Guardian is set, the question of "who steps in" needs design — see open question below.
3. Everyone with vault access retains the right to preserve / seal. Including pressing the entire jar, not just individual seeds. This is a meaningful right, not a paid-only feature gate.
4. Mixed-author content is fine — it's a feature, not a bug. Layered, multi-generational memory objects are exactly the differentiator. No competitor offers this.

Open questions spawned (need their own design pass):
Co-admin / co-owner model — when you invite someone into a vault, are they a contributor (can plant seeds) or a co-owner (can add other admins, take on responsibility/weight)? Like the Google Drive distinction. This is foundational and ties directly to HW#53 (Vault Settings Editability). Without it, "what happens when the planter dies" is underspecified.
"Request to claim" flow — when DandyLine notifies that a planter is gone (or their account expires), should there be an explicit handoff/claim prompt for the remaining vault members? Or does the vault just keep functioning under whoever has access?
Pricing model implication — preserving the entire jar. Pressing one seed is one thing; pressing the whole jar (or "buying" the jar with a max storage cap that members can extend) is a real product question. Tie into HW#80 (Revenue Model) and HW#051 (Pricing Model Spec) — flag "jar preservation" as a paid feature candidate. If anyone is willing to pay for it storage-wise, the system should let them.

Where this goes next: The co-admin / co-owner question (and its connection to HW#53) is the actual design blocker. Once that's locked, the rest of "vault keeps living" falls out naturally. Not MVP-blocking — Personal Vault MVP doesn't have multi-author at all — but needs to be locked before Grove + Legacy build.

Original card added 04.12.26. Direction locked 2026-04-27 with Claude.
💜 Decision
🤔 Direction locked · spawned 3 design questions for HW#53 / HW#80 / HW#051
● Direction locked — co-admin model + jar preservation pricing are the next design blockers
58
Memory Capsule Partnerships — Institutional Seed Key Distribution ✅ PURSUE
BusinessPartnershipsGrowthSeed Keys
✅ Pursue · April 27, 2026. Add this to the building plan as its own separate endeavor — same shape as the Printed Books / Physical Seed Key Cards stream. These are all parallel product streams alongside the core DandyLine app, not features inside it.

Decision framing: Don't try to launch all of these at once. Once core DandyLine is stable, prioritize which separate streams to pursue first — pick one, work out the details, then move to the next. This card is a placeholder commitment that the stream is real, not a "build now."

Original concept: Organizations that deal in time + memory embed DandyLine vaults into their services. Hospitals giving new parents a Seed Key at birth. Retirement communities offering Legacy Vault setup as end-of-life planning. Schools giving graduating seniors a Grove Vault their classmates plant into. Each partnership = distribution channel + emotional proof point for investors.

Will need (when prioritized): Partnership pitch deck · institutional pricing tier · API for bulk vault creation · partnership-specific onboarding flow.

Added 04.12.26. Direction locked 2026-04-27.
💜 Decision
🤔 Pursue · separate product stream · prioritize among parallel streams later
● PURSUE — separate product stream · prioritize after core DandyLine stable · 2026-04-27
60
Seed Key as Physical Product — Printed Cards / Gift Items ✅ PURSUE
BusinessRevenueMarketingSeed Keys
✅ Pursue · April 27, 2026. There's definitely a place for actual physical products. The gift-card use case in particular is real — physical Seed Keys would help with gifts.

Format flexibility: Could ship as email format (digital gift card, instant) OR physical card format (printed, beautiful, holdable). Both have a place — different occasions, different price points, different shopper psychologies.

Strategic frame: Same shape as HW#58 (Institutional Partnerships) and the printed-books stream — these are parallel product streams alongside the core DandyLine app, not features inside it. Each is its own separate endeavor with its own business development plan. Prioritize among them later once core DandyLine is stable.

Why this matters: Solves the "how do I explain this app to my mom" problem. Physical = real = trustworthy. Could be a revenue stream AND a marketing channel simultaneously.

Will need (when prioritized): Business development plan · card design + packaging · retail/e-commerce strategy · QR code generation flow · email gift card flow · pricing tiers.

Added 04.12.26. Direction locked 2026-04-27.
💜 Decision
🤔 Pursue · separate product stream · email + physical formats both viable
● PURSUE — physical + email gift card formats · separate product stream · prioritize after core stable · 2026-04-27

Quest · competitive-moat

Competitive positioning, moat thinking, dandelion symbolism, time-as-medium thesis. · 6 cards

68
Seed Key as Core Growth Engine — Organic Acquisition Strategy
BusinessGrowthStrategyInvestor
The Seed Key system isn't just a feature — it's DandyLine's core growth engine. Every vault for someone not on the platform = organic invitation. Every Open Claim Key at a wedding = 150 potential signups. Every 'Held in Trust' vault for an unborn child = a user who joins years later and arrives to something already waiting. That's not onboarding — that's an emotional moment. 'Sign up and immediately receive a message from someone who loved you before you existed.' No other app can offer this. Needs: growth model documentation, viral coefficient estimates, investor slide narrative, security/legal brief updates to cover growth mechanics. Added 04.12.26.
🔨 Build Session
✍️ Ashley + Claude · Strategy + Investor Narrative
● Not started — foundational strategy to formalize
101
Full Competitive Landscape Re-Run — Honest Assessment & Blind Spots Refresh
Strategy PMF Competitive Intel Priority
The competitive landscape document (biz-competitive-landscape.html) has grown to v3 with 45+ products, but the "Honest Assessment" and "Blind Spots" tabs haven't been fully updated to reflect new features, new competitors, or recent product decisions. Both sections likely contain outdated risk assessments, missing competitive angles, and opportunities that weren't visible when they were first written. This is a scheduled refresh task — ideally done in 1–2 weeks once the brain has some distance from today's session. What to re-run: (1) Tab 5 "Honest Assessment" — re-read every risk card and opportunity card; update any that are now better or worse given new product decisions (pricing, vault types, Guardian model, Journey Vault, Artwork Seeds, etc.); add new risks and opportunities surfaced by the Keepsake category research. (2) Tab 6 "Blind Spots" — re-read every blind spot; assess which have been partially resolved by product decisions; add any new blind spots surfaced by Artkive, HappyMe, Little Life Stories analysis. (3) Full scorecard audit — re-run weighted scores for existing competitors where market position may have shifted; check if any tier 3 items should be moved up. (4) Feature matrix — confirm the matrix still reflects DandyLine's current planned feature set (Journey Vault, Artwork Seeds, Gift Vault should now appear as DandyLine plans). Goal: biz-competitive-landscape.html goes from a historical document to a living document reviewed quarterly. Set a reminder: re-run this session in the week of May 5, 2026. Added 04.22.26.
🧠 Deep Project
📋 Strategic Review
● Scheduled — Re-run week of May 5, 2026

#108 — The Six-Layer Moat: Why DandyLine Becomes Irreplaceable

Spec-Ready Ashley High Quest #21 · Competitive Moat

A defense of DandyLine's competitive position through six structural layers: emotional brand ownership, time-based data gravity, family memory networks, ritual habit formation, trust infrastructure, and cultural narrative ownership. Summary: "The longer users stay, the stronger the product becomes."

What's Next
  • Map each of the 6 layers to a specific defensive action (what we do to earn each layer)
  • Use in the investor deck's "Why Us" / moat section
Highlights
  • Status: Framework articulated; needs translation into concrete defensive actions per layer
  • Depends on: Quest #14 investor deck; Quest #21 roadmap
  • See also: HW#110 (Dandelion Symbolism as Moat), HW#111 (Time as the Medium) — both reinforce the moat case
  • References: Originally drafted in biz-dev-notes-business.html (pre-retirement)
Working Pages
Notes — Full cleaned prose

Moat Layer 1 — Emotional Brand Ownership

DandyLine owns: Future memory language; Bloom metaphor; Time unlock ritual; Reflection-first positioning; Calm emotional UX. Competitors can copy features. They cannot quickly copy emotional trust.

Moat Layer 2 — Time-Based Data Gravity

Every capsule increases switching cost. Over time: Memories become irreplaceable; Emotional attachment grows; Archive depth compounds; Platform value increases. After several years, leaving DandyLine feels like abandoning a life archive.

Moat Layer 3 — Family Memory Graph

When families connect through capsules (parents, children, partners, grandparents), switching platforms means breaking shared timelines. This creates structural emotional network effects.

Moat Layer 4 — Ritual Habit Formation

Unlike shallow scroll habits, DandyLine builds deep rituals: birthday capsule unlocks, anniversary reflections, yearly life recaps, legacy message traditions. Life rituals are extremely difficult to displace.

Moat Layer 5 — Trust Infrastructure

If DandyLine becomes "the safest place for meaningful memories," trust itself becomes the moat. Privacy leadership and long-term preservation promises strengthen retention.

Moat Layer 6 — Cultural Narrative Ownership

First movers define: category language, emotional expectations, design patterns, user rituals. Competitors become iterations rather than originators.

Moat Summary

"The longer users stay, the stronger the product becomes."

Cleanup applied: No celestial. No military brand. No Supabase.

History
  • Migrated as gem #2 from biz-dev-notes-business.html.
📎 Merged In · From HW#139 (was: "Competitive Positioning · What DandyLine IS & IS NOT (Apr 18, 2026)")

Merge reason · Competitive Positioning IS/IS NOT folds into Six-Layer Moat card. Original card consolidated 2026-04-25.

Description: The April 18 workbook competitive positioning: four things DandyLine explicitly is NOT (photo backup, social network, journal app, messaging app), five things it IS, six reasons people choose it, and a competitor landscape. Closes with the key advantage: "None of them combine time-delay + anti-performative + event-based + founder authenticity."

Original What's Next:
  • Use as the "differentiation" slide in investor and waitlist nurture content. Pair with HW#108 (Six-Layer Moat) — this is the consumer-facing phrasing of that technical moat.
Original Highlights:
  • Is NOT: Photo backup (Google/iCloud) · Social network (Instagram/TikTok/BeReal) · Journal app (Day One/Notion/Reflectly) · Messaging app (WhatsApp/iMessage/Slack)
  • IS: Anti-performative memory platform · Time-delayed experience design · Intentional rediscovery · Private by default · Event-based and curator-driven
  • Key advantage: "None of them combine time-delay + anti-performative + event-based + founder authenticity"
  • References: Source was biz-dev-notes-strategy.html — Master Workbook v1.0 import (Apr 18, 2026)

#110 — The Dandelion as Landing Page Metaphor

Spec-Ready Ashley Medium Quest #21 · Competitive Moat

Strategic guide to leveraging the dandelion symbol as the landing page hook — not explaining mechanics, but making visitors *feel* what the dandelion means before they understand the product. Includes three hero headline options, messaging concepts, visual direction, and waitlist conversion psychology.

What's Next
  • Draft A/B tests for the 3 hero headline options on site-landing.html
  • Brief design on the "make a wish" visual language (sealed-vault + countdown imagery)
Highlights
  • Core hook: "Make a wish" — 3 words, universal, everyone knows the gesture
  • Depends on: Quest #13 Site & Landing for implementation
  • See also: HW#108 (Six-Layer Moat — Layer 1 Emotional Brand Ownership), HW#111 (Time as the Medium)
  • References: Drafted in biz-dev-notes-strategy.html (pre-retirement)
Working Pages
Notes — Full cleaned prose

Using the Dandelion Symbolism as the Landing Page Hook

The most powerful hook on the DandyLine landing page isn't the product — it's the name. Before explaining what DandyLine does, the landing page should make the visitor feel what the dandelion means. Consider: "Make a wish." (3 words. Universal. Everyone knows the gesture.) — or — "What if a breath you took today became a memory someone treasures in 10 years?"

The dandelion's wish-making tradition is the product's best onboarding metaphor: you hold an intention, you release it with purpose, and you trust that it will bloom somewhere meaningful. That's DandyLine. That's the whole pitch. The landing page should make someone feel it before they understand it.

Hero Headline Options (Symbolism-Grounded)

Option 1: "Make a wish." / Sub: "Plant it. Preserve it. Watch it bloom."

Option 2: "Some moments are too important to just remember." / Sub: "DandyLine — the memory platform that blooms on its own schedule."

Option 3: "What you plant today, someone will treasure tomorrow." / Sub: "Preserve memories now. Let them bloom exactly when they should."

Additional Headline Concepts

Preserve memories today. Let them bloom later. / Some moments deserve more than a camera roll. / The first platform built for future emotional experiences.

Subtext Options

Private by default. Designed for meaning. / Send moments forward in time for yourself or someone you love. / A calmer place to keep the moments that matter most.

Visual Direction

Minimal calming design; subtle anticipation cues (countdown imagery, sealed vault metaphors); no full UI reveal; emotional photography (parents, milestones, quiet reflective moments).

Waitlist Conversion Psychology — Key Triggers

Future regret avoidance; legacy instinct; early access exclusivity; emotional belonging; private beta framing.

Cleanup applied: Removed sun/moon/stars metaphor from the original draft. No military. No Supabase.

History
  • Migrated as gem #4 from biz-dev-notes-strategy.html. Cleaned of celestial framing.
📎 Merged In · From HW#133 (was: "Landing Page · Hero Headline Options & Waitlist Psychology")

Merge reason · Landing Page Hero Headlines fold into Landing Page Metaphor card (both about landing page positioning). Original card consolidated 2026-04-25.

Description: A candidate library of hero headline options for the landing page, built on dandelion symbolism and preservation-promise psychology. Includes trust builders, viral-loop structure, stealth-launch distribution channels, and validation metrics to track. Pair with HW#110 (Dandelion as Landing Page Metaphor) for the full landing-page direction.

Original What's Next:
  • Pick a primary headline direction when next revisiting site-landing.html. Hero Option 4 ("What you plant today…") is currently leading.
Original Highlights:
  • Leading candidate (working): "What you plant today, someone will treasure tomorrow." / "Preserve memories now. Let them bloom exactly when they should."
  • Goal: Not awareness — emotional signal validation (is the vision resonating?)
  • Viral loop: After signup, invite someone you'd send a future memory to — seeds relational growth without public exposure
  • References: Source was biz-dev-notes-strategy.html (retiring Apr 22, 2026)

#198 — Site Landing · May 1 tightening pass · Round 2 (deeper)

Spec-Ready Ashley High · PRIORITY Quest #21 · Competitive Moat

Round 2 of the May 1 site-landing tightening pass. Round 1 (4 quick mechanical fixes) shipped May 1 — see "Already Locked" below. Round 2 is the deeper creative + UX work that needs proper time. Re-entry: open site-landing.html in MASTER folder, work through ①–⑥ in order. Pre-edit backup at ARCHIVE - no longer using_store for historical reference/BACKUP-pre-tweaks-2026-05-01-site-landing.html.

What's Next · ① Motion dandelion in hero background

Place a motion-dandelion canvas in the top-right of the hero, behind the headline text, low-opacity, to add depth + motion. Source: port the canvas pattern from product-dandelion.html (canonical motion mark) or product-vaults.html (in-vault dandelion rendering — clean orbs, bezier stems, jellyfish float per CLAUDE.md). Container: position absolute behind .hero-copy, opacity ~0.25, pointer-events none, hide on mobile.

What's Next · ② Feeling section — fresh setup intro

"Nothing was ever built for later." currently lands cold without setup. Draft three different intro framings (1–2 sentences each, distinct angles — emotional / functional / quiet-minimal) that lead INTO that line. KEEP intact: the scrolling scenario chips and the closing line "somewhere to send it forward." Don't touch them. Pair with HW#110 (Dandelion as Landing Page Metaphor) — the headline candidates there may inform the new setup voice.

What's Next · ③ Replace the entire 1-2-3 "How it works" section

The three panels (01 Moment / 02 Wish / 03 Arrival) feel silly + incomplete to Ashley. Drop them entirely. Replace with a fresh pass that answers: if a stranger only sees the homepage, will they (a) understand what DandyLine is, (b) want it, (c) get how the UX feels? Use "draft three" — three distinctly different angles (e.g., one show-don't-tell visual scroll borrowing from V4 globe, one elevator-pitch trio with refreshed copy, one ceremony-narrative single-block). Ashley picks before any HTML is written.

What's Next · ④ Persona "different reason" — fix UX + refresh vault details

The concept and persona list are strong; the UX is broken. Currently selecting a persona collapses the grid and reveals one vault below — user has to know to scroll to find it. Fix: in-place reveal (push-aside or pull-up disclosure pattern). Inspiration candidates from the library: Entry 028 Push-Aside Reveal, Entry 030 Bloom-from-card, Entry 031 Pull-up structured detail. Pick one in proposal step. Refresh vault detail content from product-vaults.html (current locked vault types: Grove, Personal, Milestone, Legacy, Journey, Roots — verify against current product-vaults locks).

What's Next · ⑤ Buttons sweep against canonical decisions

Audit every .orb-btn, .orb-btn-ghost, and .nav-cta in site-landing.html against ux-button-decisions.html (canonical source of truth) cross-checked with BUTTON-CONSOLIDATION-FEEDBACK-2026-04-26.md (working notes + A10 rework plan). Replace deprecated variants. Show table of changes before editing.

What's Next · ⑥ Menu redesign + Greenhouse link

Mock the canonical public landing nav per HW#087 spec (Nav/Menu System Redesign). Two-mode component (Public + Founder) is a deeper build — for THIS pass, just craft a clean PUBLIC nav for site-landing only. Must include a Greenhouse link → lab.html (the founder-zone discovery page). Greenhouse is the locked name for the hidden-zone concept (per HW#087 step 5). Likely public nav structure: How It Works · Stories · Vaults · Founder Story · Greenhouse · Request Access (CTA). Keep mobile hamburger behavior. Don't build the shared brand-nav.js component yet — that's HW#087's full scope. Just freshen the inline nav.

✅ Already Locked · Round 1 (May 1, 2026)
  • Pre-edit backup archived at ARCHIVE/BACKUP-pre-tweaks-2026-05-01-site-landing.html
  • Nav-mark canvas dropped — wordmark-only header (was rendering as blank box)
  • Hero-mark canvas dropped — wordmark-only hero (was rendering as blank box)
  • Phone-mockup iframe → ux-field-homepage-v3-motionmark-depth.html?night=1&embed=1 (latest field/home, dark mode, WIP banner suppressed)
  • Phone-mockup needed support for URL-param overrides — added ?night=1 / ?day=1 / ?embed=1 handling to ux-field-homepage-v3-motionmark-depth.html (additive, won't disturb on-hold work)
  • "Experience the UX →" link → TEMP-dandelion-globe-V4.html (latest open-jar/globe experience)
  • Hero-sub color: var(--sage)var(--tm) (muted cream — keeps gold "DandyLine remembers" as the only accent)
Highlights
  • Goal: If a stranger only sees the homepage, do they understand what DandyLine is, want it, and feel how the UX works?
  • Untouched on purpose: Bottom "first platform built for emotional memories over time" section — Ashley confirmed it's working
  • Untouched on purpose: Scrolling scenario chips + "somewhere to send it forward" closing line in feeling section — Ashley wants them preserved
  • Post-deploy alarm: Phone-mockup iframe alignment has drifted on previous pushes. After deploying this pass, eyeball check on production.
  • See also: HW#110 (Dandelion as Landing Page Metaphor — hero copy direction), HW#087 (Nav/Menu System full redesign — long-term spec for ⑥)
  • Order suggestion: ⑥ menu first (visual top-of-page win) → ② feeling intro (copy) → ③ replace 1-2-3 (biggest pass) → ④ persona UX → ⑤ buttons → ① motion dandelion (delight layer last). But Ashley's call.
Working Pages
History
  • Card created. Round 1 quick fixes shipped (4 mechanical edits). Round 2 captured here as PRIORITY for next dedicated session — scope is 60–90 min for the creative passes (② ③ ④) plus 30 min for ⑤ ⑥ ① mechanical follow-ups.

#199 — TEMP-dandelion-globe-V4 · presentation cleanup

Thinking Ashley Medium Quest #21 · Competitive Moat

Two presentation issues on TEMP-dandelion-globe-V4.html surfaced May 1 when Ashley opened it as the "Experience the UX" target from site-landing. Site-landing now links to this file, so its presentation matters.

What's Next · ① Reorder UX screens above the notes dump

Currently the long .changelog block (17 entries, "Bug fix / Locked / Added / Scaffold" tags) lives inside <header class="hero"> BEFORE the phone-shell + density toggle + filter panel UX screens. A second "What changed in V4" .takeaway block lives below as well. Reorder so the UX screens come first (they're the demo), and demote both notes blocks to below the UX. Prefer collapsing one of the two notes blocks since they overlap in content. Re-entry: open TEMP-dandelion-globe-V4.html, locate .changelog at line ~741 and .takeaway at line ~1114, work the order from there.

What's Next · ② Fix bottom UX screen overlapping notes text

The filter panel (or a second phone-shell rendering) is hovering on top of the "What changed in V4" notes block — see screenshot Ashley sent May 1. Likely a position:absolute / z-index issue on .filter-panel or an unclosed flex/grid container. Investigate before any reorder so the fix doesn't regress.

Highlights
  • Why now: site-landing "Experience the UX" CTA points here as of May 1 — visitors will land on this page expecting a clean demo, not founder notes
  • Don't break: the V4 globe demo itself is the latest locked work — touch only the surrounding presentation
  • See also: HW#198 (Site Landing tightening Round 2)
Working Pages
History
  • Logged after Ashley landed on V4 globe via the new site-landing CTA and flagged layout issues. Punted from the May 1 site-landing pass to keep that scope tight.

#111 — Time as Core Mechanic: From "Share Now" to "Experience Later"

Spec-Ready Ashley High Quest #21 · Competitive Moat

Foundational strategy positioning time itself as DandyLine's primary product primitive — not a constraint, an emotional experience layer. Covers use cases, category creation ("Future Memory Platforms"), market timing, emotional network effects, retention philosophy, and defensibility rooted in time-based accumulation.

What's Next
  • Use the "experience later era" framing as the category-creation slide in the investor deck
  • Test "Experience Later" as positioning tagline on site-landing.html hero
Highlights
  • Category name proposed: Future Memory Platforms (new category DandyLine defines)
  • Core shift: "What should I share right now?" → "What will matter later?"
  • Depends on: Quest #14 investor deck; Quest #13 site & landing copy
  • See also: HW#108 (Six-Layer Moat — echoes Layer 2), HW#110 (Dandelion Symbolism)
  • References: Drafted in biz-dev-notes-business.html (pre-retirement)
Working Pages
Notes — Full cleaned prose

The Core Shift

DandyLine introduces time as a core emotional product mechanic. Instead of asking "What should I share right now?" DandyLine asks: "What will matter later?"

How Time Unlocks

Users create private digital capsules that unlock in the future. These capsules may contain videos, voice notes, photos, written reflections, or predictions. They can unlock: on specific dates; gradually over time; on life milestones; on anniversaries; through surprise resurfacing. Time transforms memory from a static archive into a living emotional experience.

Use Cases Across Life

Future-self messages; parent-to-child memory preservation; relationship chapter reflection; healing documentation; ambition tracking; legacy storytelling; everyday life texture. DandyLine is not about milestones alone. It is about emotional continuity.

Category Creation: Future Memory Platforms

Social media defined the "share now" era. DandyLine defines the "experience later" era. We believe this represents the emergence of a new category: Future Memory Platforms. These platforms prioritize emotional authenticity, intentional preservation, time-delayed engagement, private storytelling, and reflection over performance. Instead of optimizing for attention, they optimize for meaning.

Market Timing Signals

Several macro shifts make this moment uniquely powerful: social media fatigue and desire for healthier digital habits; massive growth in personal content creation; rising mental health awareness; increased demand for privacy-first platforms; generational storytelling interest; longevity and legacy conversations entering mainstream culture; AI-driven memory tools increasing awareness of digital preservation. Consumers are ready for technology that helps them relate differently to their own lives.

Emotional Network Effects

DandyLine spreads differently than traditional social apps. It spreads through family storytelling, life transitions, personal milestones, emotional recommendation, shared future curiosity. When one person opens a powerful capsule, others want to create their own. This creates a slower but deeper form of network effect.

Retention Through Anticipation

Traditional platforms retain users through dopamine loops. DandyLine retains users through anticipation. Waiting becomes a feature. Unlocking becomes an event. Reflection becomes habit-forming. This creates long-term engagement cycles measured in months and years, not minutes.

Monetization Philosophy

Because DandyLine holds emotionally valuable content, users are more willing to pay for: storage and preservation tiers; premium recap artifacts; legacy management tools; family capsule plans; physical exports; long-term archive guarantees. Revenue aligns with emotional usefulness rather than advertising attention.

Defensibility and Moat

DandyLine's defensibility comes from category creation leadership, emotional brand positioning, long-term user trust, time-based data accumulation, networked family content structures, habit formation around reflection, and cultural narrative ownership. This is not just another social app. It is a new emotional infrastructure layer.

The Vision

We believe the next era of consumer technology will not be about capturing more of life. It will be about helping people experience their lives more meaningfully. DandyLine transforms memory from something passive into something alive.

Cleanup applied: No celestial. No military. No Supabase.

History
  • Migrated as gem #5 from biz-dev-notes-business.html.

#140 — "On This Day" Passive Surfacing + Weather-at-Bloom (Apr 23, 2026)

Thinking Ashley Medium Quest #21 · Competitive Moat

Two related ideas born from the Apr 23 competitive re-audit. (1) An "On This Day" passive surface that re-surfaces previously-bloomed seeds on their anniversary date so Gardeners get the dopamine hit of rediscovery without planning it. (2) Ambient weather capture at plant-time and bloom-time — "it was raining the day your dad wrote this" — as emotional texture. Both address a specific competitive gap (see Highlights) without compromising DandyLine's intentional-bloom identity.

What's Next
  • Decide whether "On This Day" is a cross-vault feature or scoped to a specific vault type (Journey Vault is the obvious fit — fits chronological life capture).
  • Spec the weather-capture idea — where does it live (Seed metadata? Bloom reveal UI?), what service provides the historical weather lookup, opt-in vs. on-by-default.
  • Decide priority: MVP-worth or post-MVP delight layer?
  • Cross-check with HW108 (Six-Layer Moat) and HW139 (positioning IS/IS NOT) — does "On This Day" reinforce "intentional rediscovery" or blur it?
Highlights
  • Competitive context: Orca (formerly Happyfeed), Lumhaa, and other "memory jar" apps do passive throwback at 1w / 2w / 3w / 1m / 3m / 6m / 9m intervals. They capture the dopamine hit of rediscovery without requiring user intent. DandyLine's Bloom is fully intentional — brand strength, but a possible cold-start weakness if users want passive surfacing too. Fresh-eyes critique (Apr 23): "they do the throwback job automatically with zero setup — if users prefer 'let it happen passively,' you're fighting gravity."
  • The "On This Day" idea: Once a seed has bloomed, resurface it on the anniversary date going forward — a gentle passive layer on top of DandyLine's intentional Bloom. Does NOT compromise the intentional-bloom identity because it only surfaces things the Gardener has already chosen to experience.
  • The weather idea: Weather at plant-time (and optionally bloom-time) as embedded ambient detail. Small emotional texture that competitors don't do — makes a seed feel like a moment, not a file. Pairs especially well with Journey Vault milestone entries.
  • References: Apr 23 competitive re-audit session. External: happyfeed.co, Lumhaa (App Store).
History
  • Captured during competitive re-audit session. Ashley proposed in response to the Orca / Lumhaa "passive throwback" competitive gap the fresh-eyes subagent flagged.

Quest · frictionless-first-start-ux

First-run experience, onboarding, vocabulary teaching, starter vault, gardener profile. · 4 cards

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, popup cards). Like renaming a phone contact. Gardeners can't see the nickname. Needs: settings UX, where the name appears, privacy rules, personal avatars.
🔨 Build Session
🏗️ Build with Claude
● Idea — Needs Development
12
Storage Visualization UI — The Memory Health Bar
Product UX Design Monetization
Design a beautiful, branded storage bar (like iPhone storage) that shows users their full memory health at a glance. Three preservation states: Purple (pressed/hard storage — permanent, protected), Brown/Amber (composting tier — compressed, accessible but degrading), and a third color for shared vault content someone else is paying to preserve. Should also break down by content type (photo, video, voice, text) within each state. Needs: color system decision, layout, entry point in the app, emotional tone (feels like care, not a dashboard).
🔨 Build Session
🎨 Visual / UX Design
● Idea — Needs Design Sprint
23
Vocabulary Teaching & Progressive Disclosure — UX Pattern for Learning the App
UX Design Onboarding All Vaults
DandyLine has its own vocabulary (Sprouted Here, Rooted Here, Pressed, Compost, Bloom, Gardener, etc.) that users need to learn without feeling overwhelmed. The design principle: teach vocabulary through light, optional discovery — never through mandatory tutorials. Key pattern: a small info icon (ⓘ or a more DandyLine-fitting symbol — not the eye/visibility icon, which means something else) appears next to any term that needs explanation. Tap it for a one-sentence definition that appears inline and disappears. Used sparingly — only on terms that are genuinely unique to DandyLine, not obvious UI labels. Broader question to resolve during UX build: what is the right icon? And how do we balance this across the whole app so it never feels like there are "little eyes everywhere"? Consider: icons only appear on first encounter with a term, then fade out once the user has seen the definition. Needs: icon decision, list of all DandyLine-specific terms that need a tooltip, and a rule for when to show vs. hide the icon. Added 04.09.26.
📋 Decision Needed
🏗️ Build with Claude
● UX Principle — Needs Design System Entry During Build Phase
71
Instructional "Starter" Vault — First-Time Onboarding via Seeds
UXOnboarding
New user auto-joins an instructional vault with temporary "tutorial seeds" that coach them through how DandyLine works. Seeds auto-compost after reading, teaching composting/pressing organically. Different vault types get different instruction sets. Could also serve as the app's update/announcement channel (new features bloom as scheduled seeds). Ties to D1 empty-state concept. May also prompt for notification permissions during flow. Consider: can instruction seeds be "preserved but not counted against storage" to teach pressing? Ashley's detailed notes: see Plane Workbook section D1. PRIORITY: HIGH — determines build/flow for onboarding.
🧠 Deep Project
📋 Product Decision + UX Build
● Idea — Needs Development

Quest · app-design-system

General app UI primitives — forms, modals, tab bar, toasts, loading/error states, iconography. Tier A/B/C MVP triage. Quest #23, added 2026-04-25. · 18 cards

#183 — Tab nav: restrained swipe / micro-interaction layer on canonical TAB1-family · Field icon TBD

Thinking Ashley Medium · Polish Layer Tab Nav Micro-interaction

Surfaced 2026-04-28 EOD after Q2 reversal. The morning's Q2 lock attempted to supersede TAB2 with Entry 034 (Melting Ball Tabbar). After viewing the SVG goo-filter prototype with the actual viscous morph in motion, Ashley felt it was "offputting" and "too far off" for DandyLine's nav. Reverted to canonical TAB1-family direction (Field · Pressed · + Plant raised gold · Gardener) per ux-field-homepage-v3-motionmark-depth.html. Ashley's note: "anything you want to creatively come up with to make it feel like it has a little more swipe interaction would feel valuable... I just feel like it needs to be a little better than a boring menu." The challenge: add restrained micro-interactions that feel native to DandyLine WITHOUT another big-mechanic experiment.

What's Next
  • Field icon resolution — current sprout/seedling SVG in ux-field-homepage-v3-motionmark-depth.html line 320–326 hasn't been finalized. Explore alternates that read at small size + match the dandelion-mark family. Options: a tiny dandelion silhouette · a softer puff cluster · a horizon-line with a single seed orb above. Solve in the brand-icons.html work (HW#175).
  • Active-tab indicator — instead of a liquid blob, explore subtler treatments: (a) a thin vault-color underline that slides between tabs (linear, fast, ~250ms ease-out), (b) the active icon scales to 1.08x with a soft glow at its base, (c) the inactive tabs have a subtle low-opacity drift ambient animation (per A8 ambient drift) so the bar feels alive without movement-on-tap. Pick ONE direction; restraint is the whole point.
  • Tap acknowledgement — fire D-Ring ripple (per A2) at tap point. Active icon does a gentle press-spring (per A1). That's the whole motion budget for the tap event — no traveling indicators, no liquid bridges.
  • Plant FAB treatment — keep the canonical raised gold FAB (slightly bigger than other tabs, gold color, breathing pulse per existing TAB1). The "Plant is sacred" treatment was the one thing the Q2 reversal validated — it should stay.
  • Optional micro-flair — when user moves between tabs, the previously-active icon could briefly shed a tiny pappus particle (single seed-dot drifts down + fades) as a "soft handoff." Restrained, organic, optional. NOT a replacement for the active indicator — just a one-shot delight.
  • Build a focused prototype with just one micro-interaction at a time so it's easy to feel each one separately and pick what stays.
What was learned from Q2
  • Big-mechanic experiments at the nav layer are risky — nav is high-frequency UI that needs to feel calm, not novel.
  • The Plant FAB raised-gold-distinct treatment IS right (option B from Q2 prototype) — keep it.
  • Goo-filter / liquid morphs don't fit DandyLine's calm aesthetic even when implemented well — file under "tried, doesn't work" so we don't revisit.
  • Reference: SCRATCH-tab-melting-ball-prototype.html preserved as explored-not-locked example.
Connects to
  • ux-field-homepage-v3-motionmark-depth.html — current canonical TAB1-family nav source
  • ux-button-system.html lines 2885-2972 — TAB1/TAB2/TAB3 reference variants
  • HW#175 (brand-icons.html) — Field icon canonical resolution
  • MOTION-SPEC-V1 A1 (press-spring) · A2 (D-Ring ripple) · A8 (ambient drift) — the motion budget for tab interactions
  • biz-dev-decisions-log.md 2026-04-28 EOD entry "Q2 REVERSED" for the full reversal context

#178 — Future Popup States · 4 visual treatments to design (Pressed · Composting · Held in Trust · Location-not-yet-arrived)

Thinking Ashley High · State Visualization Popup States Sibling Pass

Consolidated 2026-04-27 from HW#178/179/180/181 (formerly 4 separate cards · all surfaced 2026-04-28 during POPUP-SPEC-V1 future-state inventory). Per app-design-system.html Section 7, these 4 popup states are already grouped as one inventory — they need to be designed in the same pass for visual coherence. Each state needs an orb-level treatment AND a popup treatment (Tier 1 + Tier 2). Master spec ships INCOMPLETE without these designed.

① Pressed (preserved forever) · silver/cream reflective sheen
  • Per Ashley's verbal: "silver glow instead of gold... reflective feel... a bright line around it that makes it feel sealed forever / protected." Pressed = "this matters · I have chosen to keep it · it cannot be undone."
  • Orb: silver/cream-toned gradient (NOT gold); reflective sheen (pressed-flower-under-glass); thin bright outline; very slow ambient pulse (slower than A13 to read serene-permanent rather than active-CTA).
  • Tier 1 popup: state label "PRESSED" cream/silver tracked uppercase; thin reflective border; no countdown; tiny "preserved" glyph.
  • Tier 2 popup: full anatomy with reflective border treatment, "Pressed · Preserved [date]" status footer, no CTAs (or limited "Re-press" / "View original" only).
  • Cross-ref: Entry 024 (Canopi pressed shelf) destination chassis · Entry 009 (TheFork seal-confirmation) emotional commitment · brand vocab "Pressed Flowers = master media library" — same kept-under-glass aesthetic.
  • Update TEMP-dandelion-globe-V4.html with 1 pressed orb + popup so full state variety is documented.
② Composting (decision window · soft-delete) · terracotta-tinted, degrading-progress signal
  • Composted = soft-delete in degradation window; user can pull back OR let it complete the cycle. Released = permanently gone (separate state).
  • Orb: terracotta-tinted? Faded opacity? Drifting downward animation? Slight blur/desaturation that progresses as compost window advances?
  • Tier 1 popup: state label "COMPOSTING" + days-remaining countdown ("3d left to recover")? Terracotta tint + faded border?
  • Tier 2 popup: full anatomy with two CTAs visible — "Bring back" (recover) + "Let it go" (commit · slide-to-commit per Entry 032 since irreversible).
  • Cross-ref: Entry 010 (Pillar compost-dump) for the orb-leaving-the-dandelion animation when initially composted.
  • Update TEMP-dandelion-globe-V4.html with 1 composting orb + popup.
  • Note 2026-04-27: V4 already includes a composting popup example using "Compost Terra" (#8C5A3D) — refine from there. Drifting (the warning state before composting · LOCKED Apr 27) also already in V4.
③ Held in Trust (Seed Keys recipient unclaimed) · distinct from "Sealed" lifecycle
  • Per CLAUDE.md vocab: Held in Trust = Pending / Unclaimed / Locked. Recipient-relationship state, NOT a time state.
  • Tier 1 popup: small "key" or "in trust" glyph + state label ("HELD IN TRUST" or "Awaiting [recipient]"). Cream/oat tones to read "trust quality" — distinct from time-gated states.
  • Tier 2 popup: full anatomy with Guardian information visible · "[recipient] hasn't claimed yet" · gardener CTAs ("Send reminder" / "Re-share Seed Key") · Guardian CTAs ("View Seed Key info" / "Mark as delivered").
  • Guardian-perspective variant: when Guardian opens app, seeds held in trust appear differently from their own seeds. Possibly separate vault category ("In My Trust") or special filter.
  • Edge cases: recipient claims AFTER bloom date passes? Guardian needs to deliver to deceased recipient?
  • Cross-ref: product-seed-keys.html · HW#177 (Journey Vault peer-gating) sibling "waiting for action" state · HW#175 (brand-icons "in trust"/key glyph at small sizes).
④ Location-not-yet-arrived (Roots geofence) · 3 distance-aware states
  • Distinct from LOCATION-LOCKED display (which shows the popup of a location-gated seed). This is the orb's state in the dandelion / Roots Map BEFORE arrival.
  • 3 distance-aware states: Far from place (default · quiet purple orb · "must travel to bloom"), Approaching place (within proximity threshold · orb glows brighter · "almost there"), At place (geofence triggered · Bloom Now state with pulse).
  • Far-from-place orb visual: small pin glyph overlay so user instantly knows "this needs travel"?
  • Popup language: communicate location requirement without spoiling contents. "Open when you visit Paris" works as title; state row needs companion language.
  • Distance-display ethics: show "3.2 miles away" (helpful but anxiety-inducing) OR keep abstract ("travel to unlock" — more poetic)?
  • Edge case: if recipient never visits the location, does the seed eventually compost? Or stay sealed forever? (links to ② Composting decision)
  • Cross-ref: Entry 022 (zenly map) · product-roots.html arrival flow + Phase 5 Bloom (line 1018+).
Connects to
  • POPUP-SPEC-V1.html Section C Future Popup States · app-design-system.html Section 7 inventory
  • HW#175 (brand-icons.html) — needs all 4 small-size glyphs
  • HW#177 (Journey Vault peer-gating) — sibling "waiting for action" state inventory
  • HW#186 (V4 Round 2 follow-ups) — V4 already includes Composting + Drifting examples; this work refines + adds Pressed + Held in Trust + Location-not-yet-arrived
  • biz-dev-decisions-log.md Composting vs Released vocabulary
  • CLAUDE.md vocabulary table — Held in Trust definition

Why one card, not four: these 4 states are explicitly grouped in app-design-system Section 7 as one "Future popup states inventory" — they need to be designed together for visual coherence (each is a sibling lifecycle-state visualization). Consolidated 2026-04-27 per the new homework consolidation rule (one card per coherent pass, not one per sub-step).

#177 — Journey Vault peer-contribution gating · "locked-but-visible" popup state · cold-start dignity

Thinking Ashley High · UX Risk Journey Vault Cold Start Popup States

Surfaced 2026-04-28 during POPUP-SPEC-V1 lockdown. Journey Vaults work via prompt-sequenced contributions: multiple gardeners contribute to the same prompt-set over time, and contributing can unlock or auto-bloom others' contributions at the same point in the journey. The cold-start risk: if no one else has contributed yet (early days · low user base · niche prompt-set), a gardener contributes and gets NOTHING back → emotional flatline → user concludes the product is broken or empty. The product math (random unlock timing to drive return engagement) makes this MORE likely to happen at scale, not less.

What needs to be designed:

What's Next (5 distinct sub-questions to answer)
  • The "locked-but-visible" popup state — when you can SEE that contributions exist at this prompt-point but they're locked behind your own contribution. Visual treatment: a popup that renders but with locked styling (lock icon? low opacity? a "contribute to unlock" CTA?). This is a NEW popup state distinct from Sealed (waiting for time) and Held in Trust (waiting for recipient claim) — it's "waiting for YOUR action."
  • Cold-start dignity rules — when there ARE no peer contributions yet, what does the gardener get? Options: (a) inspiring follow-up questions ("what would you wish for them at this age?"), (b) AI-generated companion prompts that feel personal, (c) acknowledgement copy that reframes the silence ("you're early — your contribution will be the first one others hear when they arrive at this point"), (d) historical/founder content (a Journey Vault might come pre-seeded with Ashley's own contributions to mirror), (e) a "yours alone for now" celebratory framing.
  • Random unlock timing — the math we discussed for re-engagement (variable rewards). How do we tune it so it never feels arbitrary or punitive? Specifically: what's the timing distribution that keeps people coming back without making them feel manipulated? Reference behavior-design literature on variable-ratio reinforcement, but apply it through a memory-keeping (not gambling) lens.
  • Contribution-as-key UX — if contributing IS the unlock action, how is that communicated without feeling transactional? "Plant your memory, theirs unlocks" sounds gamey. Better: "Now that you've shared yours, here's what others wished for too." Action → reciprocity, not action → reward.
  • Notification ethics — when an unlock happens (random time, peer contribution), what's the notification copy + timing? Risk: notification arrives at a bad emotional moment and the bloom moment is wasted. Possible: defer notifications · let user pull-to-discover instead · time-of-day awareness.
Connects to
  • POPUP-SPEC-V1.html Future State Considerations section (forward reference added 2026-04-28)
  • product-vaults.html Journey Vault section (canonical Journey Vault product spec)
  • HW#176 (The Bloom Moment animation) — if the unlock IS a bloom, the bloom animation has to support this trigger pattern, not just timer-expiry
  • Future brand-icons.html (HW#175) — locked-state icon needs to be canonical
  • Likely a parallel concern in Grove vaults (collective sealing, shared discovery) and Roots vaults (location-gated unlock) — flag as "gated states inventory" sub-task
⚠️ Why this is being flagged now (not deferred)
  • POPUP-SPEC-V1 just defined 5 lifecycle states (Sealed / Distant / Patient / Approaching / Imminent / Bloom Now) but those all assume "waiting for time." Peer-gating is a fundamentally different "waiting for action" axis that the spec didn't anticipate.
  • Cold-start UX is the #1 risk for any social/contribution-based product — getting it wrong tanks early adoption regardless of how good the rest of the product is.
  • If the bloom moment (HW#176) is the emotional centerpiece, the cold-start path is the silent killer that prevents users from EVER reaching that moment.

#176 — The Bloom Moment animation (click-to-bloom from Tier 2 popup) — needs dedicated design pass

Thinking Ashley High · Emotional Centerpiece Motion Bloom

Surfaced 2026-04-28 during POPUP-SPEC-V1 lockdown. When a recipient taps a Bloom Now Tier 2 popup, the transition into the bloom view (Tier 3) is the emotional centerpiece of the entire DandyLine experience — the moment the wish unfolds, the seed reveals what's been held for them. Right now this is partially specified: POPUP-SPEC-V1.html B2=C locks the transition motion (Tier 2 docks as a thumbnail in the corner as Tier 3 takes over) and the A4 routing matrix names the Tier 3 destination (Bloom view per Entry 014). But the actual blooming animation itself — what the user SEES + FEELS in those 2–4 seconds of opening — has never had a dedicated design pass. ux-bloom-reveal.html exists as an early prototype but predates the V2 motion system, B1=D anchored depth, and A13 ambient pulse. Needs: a fresh design pass that treats the bloom as the FLAGSHIP motion moment of the app, mining the strongest bloom-related inspiration entries and synthesizing them into a buildable spec for Josh.

What's Next
  • Audit existing bloom-moment work: ux-bloom-reveal.html (current prototype) · product-seeds.html bloom view section · POPUP-SPEC-V1.html B2=C transition lock · A4 routing matrix.
  • Mine inspiration library for relevant entries:
    • Entry 014 — Apple TV bloom view (full-bleed media + thumbnail strip) — already canonical Tier 3 destination
    • Entry 030 — Kole Jain bloom-from-card-to-page expansion (3:00–3:28 in the YouTube reference)
    • Entry 008 — "Anticipation, not opacity" philosophical throughline
    • Entry 009 — TheFork seal-confirmation moment ("Sealed, Ashley." beat)
    • Entry 011 — Believe arc dial (dandelion-orb arc for media flipping)
    • Entry 013 — 3D dandelion bloom-globe (Three.js feasibility — separate spike pending Josh)
  • Define the multi-phase motion: (1) tap acknowledgement, (2) anticipation pause, (3) reveal/unfold, (4) media-emerges, (5) settled-bloom-state. Each phase has its own timing + easing.
  • Coordinate with: A13 (Bloom Now ambient pulse should NOT just stop on tap — should transition into the reveal), A2 D-Ring (the tap ripple is the trigger), MOTION-SPEC B-section locks.
  • Build ux-bloom-moment-v2.html as the new prototype (preserve ux-bloom-reveal.html as v1).
  • Seek Ashley's emotional read at multiple checkpoints — this is THE feeling moment of the product, not a UI motion choice.
⚠️ Why this is being flagged now
  • POPUP-SPEC-V1 today locked the mechanical transition (B2=C) but the emotional payload of the actual bloom animation was never speced. Ashley flagged 2026-04-28 that this needs to be powerful and inspired — not just functional.
  • The master app-design-system.html spec deliverable for Josh would be incomplete without the bloom moment defined — it's the moment users will most remember.
  • Risks if not done: bloom defaults to whatever ux-bloom-reveal.html v1 did (predates 6 weeks of motion-system maturation) OR Josh implements something generic.

#175 — Build brand-icons.html (canonical small/medium/large icon reference) — BLOCKER for app-design-system

Thinking Ashley High · Blocker Design System Brand

Surfaced 2026-04-28 during POPUP-SPEC-V1 lockdown. The app uses many small icons everywhere — media types (mic / camera / video / note / location / file), lifecycle states (Sealed / Blooming Soon / Bloom Now glyph indicators), vault types (the 6 jar marks), navigation (tab bar glyphs), and actions (plant / press / compost / share / claim). Today's popup work flagged that at small sizes (10–14px in Tier 1 popups, B1=D depth-stacks), media icons can look ambiguous — a circle, a rectangle, a 3-line waveform all read as "some kind of glyph" without enough disambiguation. The current icon use is ad-hoc per file; nothing canonical exists. Build brand-icons.html as a brand-level reference page sitting alongside brand-color-system.html and brand-typography.html: every icon DandyLine uses, categorized (media · lifecycle · vault · navigation · action · location), rendered at every meaningful size (12px / 16px / 24px / 32px / 48px) so the visual progression is documented and the small-size disambiguation is solved. Master app-design-system.html spec will REFERENCE this page, not contain it (better separation: the icon library is brand-level, used by app + marketing + site).

What's Next
  • Audit existing icon use across POPUP-SPEC-V1.html (3 TODO comments left in B1-A), MOTION-SPEC-V1.html, product-seeds.html, product-vaults.html, product-roots.html, brand-shared.css, brand-icon.js. Catalog every distinct icon currently in use.
  • Decide canonical SVG for each media type — including the mic-vs-waveform question for voice-note seeds (today's session established mic as the canonical answer; document it).
  • Design the 6 size variants per icon (12 / 16 / 24 / 32 / 48px) with stroke-width adjustments per size (small icons may need lighter strokes to avoid blob-ifying).
  • Build brand-icons.html with a category-grouped grid showing every icon at every size + paste-able SVG snippets.
  • Sweep existing files to use the canonical icons (TODOs in POPUP-SPEC-V1.html B1-A · waveform → mic in TEMP-dandelion-globe-V2-FAITHFUL.html when V3 fork is built).
  • Add to brand-guide.html table of contents and link from brand-system.html.
⚠️ Why this is a blocker
  • The master consolidated app-design-system.html spec (the deliverable Josh needs) cannot accurately document the icon system without this reference existing. Otherwise the master spec inherits the same ambiguity it's trying to eliminate.
  • Without canonical small-icon disambiguation, popup designs (B1=D anchored depth) will keep getting ad-hoc icons that don't read at small sizes — the exact problem flagged today.

#147 — Form & Input Field System (Tier A)

Thinking Ashley High · MVP Blocker Design System

Text inputs, textareas, dropdowns, date pickers, radio pills, toggles, checkboxes. States per field: default / focused / filled / error / disabled / placeholder. Without this spec, every form in the app gets a slightly different treatment. Slots into DESIGN-SPEC.md Section 8 (Component Specs).

What's Next
  • Design a reference form with all input types on one page (like shadcn/ui showcase)
  • Build ux-form-system.html as the reference
  • Canonicalize into DESIGN-SPEC.md after approved

#148 — Bottom Tab Bar Exact Specs (Tier A)

Thinking Ashley High · MVP Blocker Design System

Field / Pressed / Plant / Gardener — 4-tab bottom nav. DESIGN-SPEC.md Section 9H mentions it but doesn't spec dimensions, active/inactive states, badge styling, FAB-protrusion math, or safe-area handling on iPhone notches. Reference pattern in ux-field-homepage-v3-motionmark-depth.html (Ashley called it "close to perfect"). Field icon decision locked 2026-04-24: mini dandelion silhouette (per brand-logo-marks.html lockup mark at 20px stroke outline) — replaces the current seed-packet glyph which reads more tulip than dandelion.

What's Next
  • Pick tab bar height (60px? 72px? 80px with safe-area?)
  • Design FAB that protrudes above (14px raise per current notes)
  • Lock active-state indicator (pill? dot? gold underline?)
  • Badge styling for notification counts
  • Build mini-dandelion Field icon at 20px stroke (port from brand-icon.js)
Highlights
  • Reference pattern: ux-field-homepage-v3-motionmark-depth.html lines 168-194 (bottom-nav CSS)
  • Locked colors: inactive `rgba(245,240,232,.28)`, active `#D4A853`, FAB gradient `linear-gradient(135deg, #F0C96A, #D4A853)`
  • Locked icon style: 20px SVG, 1.5 stroke-width, currentColor, round line-caps
  • Field icon: Mini dandelion (option 1 from Claude's 5-option suggestion 2026-04-24) — unambiguously DandyLine, ties tab back to brand mark everywhere

#149 — Modal / Dialog / Bottom-Sheet System (Tier A)

Thinking Ashley High · MVP Blocker Design System

Confirmation dialogs ("Are you sure you want to compost?"), action sheets (compost/press/download/delete — from DESIGN-SPEC Section 9O), bottom sheets (My Garden in the globe), full-screen modals, toasts. Currently zero spec. Slots into Section 8.

What's Next
  • Decide: sheet animation (slide up 300ms? spring? ceremonial 600ms?)
  • Decide: backdrop blur level and overlay opacity
  • Decide: dismissal (tap-outside vs. swipe-down vs. X button — all three?)

#150 — Loading & Skeleton States (Tier A)

Thinking Ashley High · MVP Blocker Design System

What does "loading a vault" look like? Upload progress? Encryption-in-progress visual? Voice recording status? A "growing dandelion" loader would be on-brand and is currently undefined. Slots into Section 7 (Animation) or new Section 13 (States).

What's Next
  • Design the "growing dandelion" loader as a signature loading animation
  • Design skeleton states for vault cards, seed cards, gardener list
  • Design upload-in-progress indicator for media

#151 — Error & Connection Feedback States (Tier A)

Thinking Ashley High · MVP Blocker Design System

Offline banner, "couldn't load this vault" empty state, failed upload with retry UI, content-moderation rejection screen, generic "something went wrong" fallback. The Section 9L error handling spec covers the WHAT — this captures the VISUAL. Slots into new Section 13 (States).

What's Next
  • Decide tone (warm and reassuring, not alarming)
  • Pick icon style for error states (broken seed? wilted dandelion?)
  • Lock the amber warning color from DESIGN-SPEC Section 2 as the error accent

#152 — Voice Recording & Playback UI (Tier A)

Thinking Ashley High · MVP Blocker Design System

Referenced everywhere (10-min voice notes, waveform) but no actual UI spec. Need recording controls (start/stop/pause/re-do), playback (waveform scrubber, play/pause, duration, transcript toggle), and trim. Critical for Legacy/Grove/NoVavo-style use cases and the biggest competitive feature parity item.

What's Next
  • Study NoVavo's voice prompt UI (they're the main competitor doing this well)
  • Design waveform visual (animated during record, static during playback)
  • Build prototype as ux-voice-recording.html

#153 — Account / Auth Screens (Tier A)

Thinking Ashley High · MVP Blocker Design System · Onboarding

Sign up, sign in, forgot password, email verification, OAuth buttons (Google/Apple), email-already-exists handling. Section 9D covers Seed Key claiming but skips the auth UI itself. First thing every new user sees.

What's Next
  • Decide: how brand-forward is sign-up? (Full dandelion animation? Subtle?)
  • Decide: OAuth vs. email/password priority
  • Pair with the Welcome Vault onboarding (DESIGN-SPEC Section 9Q)

#154 — Iconography System (Tier A)

Thinking Ashley High · MVP Blocker Design System

Which icon library? Stroke weight? Sizing scale (sm 16px / md 20px / lg 24px)? Custom seed-type icons (photo, video, voice, text, mixed)? Action icons (plant, bloom, press, compost, share, edit, delete). Without a system, every page defaults to whatever's nearby.

What's Next
  • Decide: Lucide (open-source) vs. Phosphor vs. custom hand-drawn
  • Lock stroke weight — 1.5px? 2px?
  • Custom seed-type glyphs (1 per media type) are worth designing from scratch for brand ownership

#155 — Spacing / Grid System (Tier B)

Thinking Ashley Medium Design System

Is DandyLine on an 8pt scale? 4/8/12/16/24/32/48? No spacing tokens documented. Affects every screen layout. Need to pick a scale and define named tokens (--space-xs, --space-sm, etc.).

What's Next
  • Pick a scale (recommend 4pt for fine control, 8pt for cleaner math)
  • Define tokens in a CSS variables file

#156 — Avatar System (Tier B)

Thinking Ashley Medium Design System

Sizes (sm/md/lg), fallback rules (initials? color derived from name?), avatar-stack rules for multi-Gardener vaults (Section 9H mentions a 28px circle avatar stack but no stacking rules). Used in Gardeners row, profiles, contributor chips.

What's Next
  • Lock size scale (24/32/48/72?)
  • Design initial-letter fallback with color-from-name algorithm
  • Lock avatar-stack overlap distance and max visible

#157 — Seed Key Share UI (Tier B)

Thinking Ashley Medium · Revenue Design System · Seed Keys

The actual card/screen a Gardener sees when sharing a Seed Key. QR code? Copy-link button? Email share? SMS share? Physical Seed Key card preview (revenue stream from deep audit §8.7). Section 6 covers Seed Keys architecturally but not the share UX.

What's Next
  • Design the digital share screen
  • Design the physical card layout (revenue stream)
  • Decide: QR code on by default, or opt-in?

#158 — Settings & Preferences Screens (Tier B)

Thinking Ashley Medium Design System

Notification preferences (per-vault-type categories named in Section 9I but no UI), storage management ("8GB of 50GB used" with upgrade CTA), account deletion flow (open item in §11), GDPR data export. Lives under the Gardener tab.

What's Next
  • Map all settings categories
  • Resolve account deletion policy (§11 open item)
  • Design storage management with upgrade path

#159 — Toast / Snackbar System (Tier B)

Thinking Ashley Medium Design System

"Saved to drafts," "Seed Key copied," "Couldn't connect — retrying..." — short non-blocking feedback. Currently undefined. Three variants needed (success / info / error). Slots into Section 8.

What's Next
  • Pick position (top? bottom-above-tabbar?)
  • Lock duration (3s? 5s?)
  • Pick swipe-to-dismiss gesture

#160 — Posthumous Experience Design (Tier C)

Thinking Ashley Low · Post-MVP Design System · Guardian

Softer animation timing noted as TBD in Section 7. Also need: Guardian dashboard visual treatment (more somber? same theme?), death certificate upload UI, condolence moments, gentler language throughout the Guardian flow.

What's Next
  • Dedicated design session — this is emotionally weighty, needs care
  • Lock posthumous bloom animation timing (slower than live-planter reveal)

#161 — Print Product UX (Tier C)

Thinking Ashley Low · Post-MVP · Revenue Design System · Revenue

Photo book preview (Journey Vault → printed output), physical Seed Key card design (size, layout, redeem instructions), order/payment flow, shipping status tracking. Direct revenue stream per deep audit §8.7 (Chatbooks $30-80M validates the category).

What's Next
  • Study Chatbooks and Mixbook flows for patterns to borrow
  • Decide print partner (Blurb API? Shutterfly white-label? Custom?)
  • Design physical Seed Key card in print-ready format

#162 — Discovery / Community Gardens (Tier C)

Thinking Ashley Low · Post-MVP Design System · Community

Public vault browsing UI, "request to join" flow, public vault preview cards. Mentioned as open in Section 11. Only relevant once Roots + Grove vaults have scale.

What's Next
  • Defer until post-launch; revisit when you have users in shared vaults

#201 — Restyle locks · May 2 implementation buildout

Spec Ready Ashley High · Deep 🎯 Spec Tier

Build punch list for shipping today's Restyle locks (Q1 nav · Q2 footer · Q3 status badges · Q4 Field icon · Q10 port DoD). Canonical specs live in biz-dev-decisions-log.md May 2 entries — open that first as the source of truth. Visual preview at SCRATCH-restyle-preview-2026-05-02.html. ⑤ runs only after ①–④ ship; ⑥ can run anytime. When this card is fully done, all six tier-state moves: 🎯 Spec → 🔨 Component → ✅ Live.

Build punch list (in any order; ⑤ last)
  • ① brand-nav.js — shared nav component, two variants (PUBLIC + FOUNDER per Q1). Mobile hamburger right; desktop sticky-on-scroll.
  • ② brand-footer.js — Path B-Light per Q2. Universal tagline "Time isn't a feature. It's the medium." auto-year copyright.
  • ③ brand-status-system.html + .status-badge CSS — visual gallery for the 4 statuses per Q3 (Live · Growing · Wishing · Ripening). Pattern mirrors brand-color-system.html.
  • ④ Field icon swap — replace placeholder sprout SVG in ux-field-homepage-v3-motionmark-depth.html + ux-button-system.html tab nav with the locked dot cluster (Q4 entry has SVG verbatim).
  • ⑤ Port-DoD audit — run the 10-criterion checklist (6 universal + 4 conditional) per Q10 across all live pages on dandyline.app. Pages passing all applicable criteria get data-status="live" and tier moves to ✅ Live.
  • ⑥ Ripple updates — copy-vault tagline notes (3 registers per Q2), site-landing footer tagline sweep, command-center TOC status badges → canonical 4-status system.

#202 — Master Field view vs single-vault view — visual differentiation

Thinking Ashley Medium · UX 🌱 Concept Tier

Surfaced 2026-05-02 during Restyle Q4 walkthrough. The Field master view (all seeds across all vaults) and a single-vault view both render as a dandelion-globe — visually IDENTICAL except for filter state. Q4 solved this at the icon layer (dot cluster ≠ dandelion); this card solves it at the VIEW layer. Sits at 🌱 Concept tier — needs prototype before locking spec.

Directions to explore (prototype before locking)
  • Vault-context label at top: "All Vaults · 47 seeds" vs "Grove · 12 seeds" (lightest, most explicit)
  • Background variation: master view has subtly different ambient gradient or backdrop tint
  • Per-vault dot animation extension: single-vault uses that vault's animation; master uses a unified "all vaults gently rotating" pattern (extends V4 motion language)
  • Density indicator: master has visibly more orbs than any one vault — proceed carefully; could feel chaotic
  • Combination: top label + ambient backdrop variation is probably the cleanest minimal solution; needs prototype to feel right
Highlights
  • Origin: Ashley flagged 2026-05-02 — "the master view basically just undoes filters by vault, looks identical to individual dandelion."
  • Q4 icon decision (loose dot cluster, not mini-dandelion) was specifically chosen to avoid perpetuating this confusion at the navigation layer.
  • Doesn't block any May 2 lock; can be designed in parallel with HW#201 implementation.

The Build Roadmap

Ashley and Claude are building the family MVP together — the same way everything else in this folder was built. Split into Phase 0 (decisions to make before writing code) and Phase 1 (the actual build). Steps are in order. Josh Peña is the technical lead handling infrastructure setup (D1 + wrangler.toml). He is actively building the foundation — Claude and Ashley pick up from there once D1 is wired.

Stack locked April 12, 2026: Cloudflare-only — Pages + D1 (database) + R2 (storage) + Workers + Resend (email). Supabase dropped. Josh is wiring D1 + wrangler.toml now. Family MVP build cost: ~$0. Monthly running cost at family scale: $0–$20.

Ashley decides / acts
Ashley + Claude build
Worth a quick call with Josh
MVP Goal Timeline
Target: rough estimate — adjust as you go. Ashley + Claude build at whatever pace works.
WEEK 0 / 14
Updated automatically
0% complete
Phase 0 · Foundation
Wk 1–3
Legal + Scaffold
Not started
Phase 1 · Build
Wk 3–12
Core MVP (9 steps)
Waiting on Phase 0
Launch Prep
Wk 12–14
Polish + Go Live
Future
Kickoff Legal Auth Seeds Seal Homepage Launch
Kickoff date:
Phase 0 — Decisions First
Before writing code. These are decisions and light setup tasks — not engineering work. Ashley handles all of these, with Claude. Some are worth a quick conversation with Josh for his perspective, but none require him to build anything.
0A
Legal Blockers — Engage Counsel
Three legal questions must be answered before building begins. Children are core recipients of DandyLine content, which triggers specific legal obligations. Find a lawyer familiar with tech/startup law and get guidance on: (1) COPPA — are we "directed at children" if a teenager creates an account to view a bloomed vault? (2) NCMEC reporting — what are our exact procedures for reporting detected CSAM? (3) GDPR — what's our data retention policy when a user requests deletion of sealed content?
🌱 Family
$0 — For 10 invited family members you personally know, formal COPPA/NCMEC/GDPR compliance isn't legally required. You're not "directed at children" if Grandma opens a vault. Skip this for the family MVP and revisit before any public-facing launch.
🏢 Scale
$2K–$5K legal — Required before public launch. Any platform that stores user-generated content involving children needs COPPA guidance, NCMEC reporting procedures, and GDPR/CCPA data policies documented. Non-negotiable at scale.
✓ Done when: Legal counsel has provided written guidance on all three
Homework: HW#31, HW#33 · LAUNCH BLOCKER
Ashley ⏭ Deferred
Family MVP
Launch Blocker
0B
Product Decisions — Account Recovery & Recipient Verification ✓ Resolved April 21, 2026
Both decisions locked in a working session with Claude.
Account Recovery (HW#32): At signup, users choose at least one backup method or defer to later. Options: backup email · recovery codes · phone/SMS · Guardian vouching. "Set up later" always available to reduce friction. Users nudged post-signup, especially before first vault planting. Framing: "Your seeds could bloom for decades. We want to make sure you're always there to witness it."
Recipient Verification (HW#38): Planters choose verification level per vault — no one-size-fits-all. Options: no verification · Seed Key only · Seed Key + passphrase · Guardian vouching · email confirmation. Options can be combined. Nudging increases as gardener plants more seeds. Framing: "We seal it, encrypt it, and protect it on our end. Help us make sure only the right person ever opens it."
Full decisions documented in dandyline-app/QUESTIONS-FROM-ASHLEY.md · HW#32, HW#38 closed
✓ Done
0C
Messaging Decisions — Zero-Knowledge & Time-Locks ✓ Resolved April 21, 2026
Both messaging decisions locked in working session with Claude.
Privacy messaging (HW#34): "Scanned" retired — too clinical. Approved language: "one quiet check." Two layers: short trust signal for signup → "Once it's sealed, no one can touch it. Not even us. We just do one quiet check to make sure everything inside is safe — to protect the people you're planting for." Brand/explainer version for Privacy page → "We tend the garden carefully before the seeds are sealed. One quiet check to make sure everything inside is safe — then it's locked away, beyond our reach, waiting only for the moment you chose."
Time-locks: Ashley comfortable with application logic enforcement. Marketing line confirmed: "Sealed until the moment you chose." Application logic is actually an advantage over cryptographic locks for Date TBD vaults (milestone blooms like a wedding day). Side effect: HW#89 added — Super Lock must be disabled/blocked for vaults without a set bloom date.
Full decisions documented in dandyline-app/QUESTIONS-FROM-ASHLEY.md · HW#34 closed · HW#89 opened
✓ Done
0D
Account Setup — Cloudflare D1 + Tools ✓ Josh Completed — April 2026
Stack is Cloudflare-only (locked April 12, 2026). Josh is handling the D1 setup: (1) Create a Cloudflare D1 database — this is the database (SQLite-compatible, lives on Cloudflare edge). (2) Wire wrangler.toml to bind D1 + R2 to the Pages project. (3) Create the 4 core tables in D1: profiles, vaults, seeds, bloom_schedule (SQLite syntax). (4) Confirm R2 bucket exists for file storage. Re-entry point: Josh completes D1 setup → Ashley + Claude pick up here and start writing Workers functions for auth and the planting flow.
🌱 Family
$0 — Cloudflare D1 free tier: 5GB storage, 25M row reads/day, 100K row writes/day. More than enough for family scale. Josh sets up D1 and wrangler.toml bindings. Ashley + Claude write the Workers functions on top. Everything stays in Cloudflare's ecosystem — no third-party database needed.
🏢 Scale
$5/mo Workers Paid — Same D1 stack, but Workers Paid plan ($5/mo) unlocks higher limits: 10M+ requests/day, Durable Objects, Queues, and Cron Triggers at production scale. Also: Drizzle ORM for type-safe queries, Turborepo monorepo, GitHub Actions CI/CD. This is the architecture Josh recommended — it's already the plan from day one, no migration needed.
✓ Done when: D1 is live, wrangler.toml shows D1 + R2 bindings, and 4 core tables exist in D1
Stack: Cloudflare D1 (database) + R2 (storage) + Pages (frontend) + Workers (backend) + Resend (email)
What Josh completed: D1 database live · wrangler.toml with D1 dev + prod + KV + R2 bindings · Turborepo monorepo · password reset flow · seed encryption pipeline · auth live end-to-end. Phase 1 app build is ~55–60% complete. Auth is live. Core infra is done.
✓ Done
0E
Email Strategy — What We Send, When, and Why ⚡ Decision needed
DandyLine sends emails via Resend (our locked stack). Before building Step 06 (Bloom Delivery), we need to map out every email moment — what triggers it, what the email should feel like, and whether it should be email or text. This also covers scheduling logic: is the Cron Trigger daily? Hourly? What happens if someone's bloom date lands on a Sunday at 3am?
Email Moments to Map Out
Trigger
What the email says
Email or Text?
Account created
Welcome + verify your email
Email only
First seed planted
Confirmation + countdown to bloom date
Email only
Vault sealed
Sealed confirmation — "Your seeds are sleeping"
Email only
Bloom day arrives
🌸 "Something is blooming for you"
⚡ Decide: email or text?
Bloom date reminder (–7 days)
Remind planter: something blooms soon
⚡ Do we send this at all?
Account recovery nudge
Set a backup method — don't lose your vault
Email only
Password reset
Reset link — standard transactional
Email only
Decisions to Make
1. Bloom notification: email or text?
This is the most emotional moment in the app. An email is quiet and intentional — it sits in your inbox and waits. A text is immediate and loud — it buzzes your phone. Which feeling does DandyLine want to own?
📧 Email: free via Resend, works today, feels curated and deliberate. Risk: lost in spam.
📱 Text (SMS): Twilio ~$0.0079/msg, feels urgent and personal. Risk: adds cost + another account to manage. Can be added later.
→ Recommendation: Start email-only. Build for SMS in Phase 2 once you see how the bloom moment lands.
2. When does the Cron Trigger fire?
The bloom delivery Cron runs on a schedule. Options:
0 8 * * * — once a day at 8am UTC (simple, but no one's in the same timezone)
*/5 * * * * — every 5 minutes (delivers within 5 min of bloom date, any timezone)
0 * * * * — every hour (compromise — within 1hr of bloom date)
→ Recommendation: Every hour for family MVP. Every 5 min for scale launch.
3. Do we send pre-bloom reminders?
Should the planter get a "heads up, something blooms in 7 days" email? Pros: they can prepare, adds anticipation. Cons: spoils the surprise, adds more emails, annoying if they planted 50 seeds.
→ Open question — decide before building Step 06.
Email tone: Every email should feel like DandyLine — quiet, intentional, not corporate. The bloom notification especially. "Something is blooming for you" is the working line. Don't write emails that sound like a notification from Dropbox. Write emails that feel like a letter arriving.
Blocks: Step 06 (Bloom Delivery) · Tech: Resend (templates) · Cron Triggers (scheduling) · Twilio optional later
Ashley Decision
Phase 1 — MVP Build
Ashley and Claude build this together, step by step — exactly the way everything else in this folder was made. One workflow: Sign up → Plant a photo or text → Name it → Set a bloom date → Seal → Wait → Bloom. Josh handles infrastructure setup (D1, wrangler.toml, bindings) and advises on any step with security or architecture implications. Re-entry point: once Josh completes D1 setup, Ashley + Claude write Workers functions starting at Step 01.
01
Authentication — The Front Door
Three ways to sign in: Google ("Sign in with Google" button), Apple ("Sign in with Apple"), and email/password. Self-hosted on Cloudflare Workers — no third-party auth service, so user data never leaves DandyLine. Sessions are 15-minute access tokens with 30-day refresh tokens. Passwords hashed with Argon2id (military-grade). Email verification required before sealing. This replaces the old magic link approach — more robust and works with future native apps.
🌱 Family
$0 — Magic link auth via a Cloudflare Worker + Resend. Grandma-proof: enter email, tap a link, you're in. Session token stored in KV. No passwords, no OAuth, no Google/Apple developer accounts needed. Does NOT include: Google/Apple sign-in, Argon2id password hashing. Simple, fast to build, and zero third-party auth service required.
🏢 Scale
Build time + ~$99/yr Apple Dev — Self-hosted OAuth on Cloudflare Workers with Google + Apple sign-in, email/password with Argon2id, 15-min access tokens, 30-day refresh tokens stored in KV. Required when you need App Store presence (Apple requires Sign in with Apple), or when you want full control over auth flow and user data. Adds real engineering complexity.
✓ Done when: You can sign in with Google, Apple, or email/password and land on the Field (home screen)
Depends on: Phase 0 scaffold · Tech: Arctic (OAuth), Argon2id (passwords), KV (sessions), Resend (verification email)
Ashley + Claude
02
Vault Creation — Plant Your First Jar
A simple screen to create a personal vault: give it a name, say who it's for (Sterling, Stella, Family). Vault is created in D1 with status "open." MVP supports personal vaults only — one owner, one vault type. Grove, Milestone, Legacy, and other vault types come in later phases. This is the moment DandyLine becomes personal.
🌱 Family
$0 — Same at both levels. A form that creates a row in the vaults table. Name, recipient, created_by. Simple. No difference between family and enterprise here.
🏢 Scale
Same — Only difference at scale: vault types (Grove, Milestone, Legacy, Journey) add type-specific fields and rules. For family MVP, one vault type ("Personal") is enough. Vault types expand in later phases.
✓ Done when: You can create a vault and see it listed on the Field homepage
Depends on: Step 01
Ashley + Claude
03
Seed Planting — Text & Photos
The core planting flow. Type a note or upload a photo into a vault. Text seeds and photo seeds are the two MVP media types (video is deferred to Phase 2). Photos upload to a temporary R2 location — they sit there, access-controlled, until the vault is sealed. A date picker lets you choose a bloom date. This is the step where the product clicks: "Sterling just said the most hilarious thing in his sleep" gets planted and dated.
🌱 Family
$0 — Upload photos to R2 (Cloudflare object storage, free tier). Text seeds stored in D1. Date picker for bloom date. That's the whole feature. Does NOT include: video upload (deferred), encryption at rest, or content scanning.
🏢 Scale
R2 costs scale with storage — At scale: uploads go to a temp R2 bucket, content is scanned before permanent storage, video encoding via Cloudflare Stream (~$5/1K min of video), and files are encrypted before permanent storage. R2 is $0.015/GB/month — cheap at family scale, meaningful at 10K+ users with video.
✓ Done when: You can plant a text or photo seed with a future bloom date
Depends on: Steps 01–02 · Tech: R2 (file storage), D1 (seed metadata)
Ashley + Claude
04
Content Moderation — Scan Before Encrypt
Josh suggested this as a future legal requirement — not needed for the family MVP. For a closed family beta with known, invited users, content moderation APIs are overkill. This step belongs on the roadmap before any public or community-facing launch, not before the family MVP. Keeping it here as a placeholder so it doesn't get forgotten — but it is not a Phase 0 or Phase 1 blocker for the family build. When it's time: CSAM hash scanning (Cloudflare's free tool), visual classification for nudity/violence/self-harm (Hive AI), text NLP for crisis indicators (Workers AI). Worth asking Josh for his recommendation on sequencing when the time comes.
🌱 Family
$0 — SKIP FOR NOW — For a closed family beta where you personally invited every person, automated content scanning adds zero value. You trust these people. What skipping means: uploaded photos and text go straight to storage with no automated safety check. If someone uploads something inappropriate, you'd only know by seeing it yourself when it blooms. Risk level: near zero — your family isn't uploading harmful content. When to add it: Before the first person you don't personally know gets access. The moment the user base includes anyone outside your trusted circle — friends of friends, beta testers, community vault members — content moderation becomes a legal and ethical requirement. Budget 1–2 build sessions with Claude to add it. Easy to bolt on later because it sits between upload and storage — you're just inserting a check in the middle of an existing flow.
🏢 Scale
~$1.50/mo (Hive AI) — Required before any public or community launch. CSAM hash scanning (Cloudflare, free), visual classification for nudity/violence (Hive AI, ~$1.50/mo at MVP scale), text NLP for crisis indicators (Workers AI, free). Plus NCMEC auto-reporting pipeline. Real engineering — but doesn't exist until you have strangers uploading content.
✓ Done when: Uploads are scanned synchronously, blocked content is rejected, flagged content enters review queue
Depends on: Step 03 · Legal: Phase 0A must be complete · Ashley: will handle manual review at launch
Ashley + Claude New step
05
The Seal Ritual — Encrypt & Lock
When you tap "Seal This Vault," the app marks it as sealed in the database, locks it from further edits, and moves the content to a protected storage state. For the family MVP, this is a database status change + storage permission lock — simple and effective. Josh proposed a more complex encryption architecture (AES-256-GCM, DEK/MEK key wrapping, Durable Object state machines, AWS S3 backup replication) that is genuinely strong for a public product at scale. That architecture is worth discussing with him before public launch — but it is not required for a 10-person family beta. Build the simple version first. Upgrade the security model when real users and real stakes are involved.
🌱 Family
$0 — Seal = flip a database flag in D1 from "open" to "sealed." Content stays in R2, vault becomes read-only. No encryption, no key management, no backup replication. Cloudflare's infrastructure (D1 + R2) handles durability. Does NOT include: AES-256 encryption, DEK/MEK key wrapping, Durable Object state machines, AWS S3 cross-cloud backup.
🏢 Scale
$5/mo Workers + AWS costs — Full encryption pipeline: unique encryption key (DEK) per seed, wrapped by master key (MEK), AES-256-GCM encryption, Durable Object state machine for irreversible seal transition, cross-cloud backup to AWS S3 + DynamoDB. This is where "sealed" becomes cryptographically real — not just a database flag. Serious engineering. Worth it at public scale. Overkill for family.
✓ Done when: Sealing a vault locks it from editing and protects the content
Family: database flag + storage lock · Scale: Secrets Store (MEK), KV (DEKs), R2 (encrypted content), Durable Objects, Queues (backup)
Ashley + Claude New step
06
Bloom Delivery — The Daily Alarm Clock
A Cron Trigger runs every 1–5 minutes (not just once a morning) and queries D1 for seeds whose bloom date has arrived. For each match: the Durable Object verifies single-execution (no double bloom), the DEK is unwrapped using the MEK, content is decrypted, and the recipient gets an in-app notification + email via Resend. SMS is deferred — email only for MVP. The notification says something like: "Something is blooming for you." This is where the app becomes a time capsule.
🌱 Family
$0 — A Cloudflare Cron Trigger (Workers) checks the bloom_schedule table in D1 once a day (or every hour). If a seed's date has arrived, send an email via Resend (free tier: 3K emails/mo). No decryption needed (content isn't encrypted at this tier). Simple, reliable, and Grandma gets an email that says "Something is blooming for you."
🏢 Scale
$5/mo Workers — Cron runs every 1–5 minutes, Durable Object enforces single-execution (no double blooms), DEK is unwrapped and content decrypted before delivery. Push notifications via service worker. SMS via Twilio (~$0.0079/msg). The complexity here is all about the encryption/decryption pipeline and delivery guarantees at volume.
✓ Done when: You plant a seed for today, seal the vault, and get an email that something is blooming
Depends on: Step 05 · Tech: Cron Triggers, Resend (email)
Ashley + Claude
07
The Bloom Reveal — The Emotional Payoff
The most important screen in the entire app. When someone taps the link in their notification, content is decrypted and revealed — a photo, a note — with the date it was planted, who planted it, and what it's from. This screen needs to feel like opening something, not loading a file. Use the existing bloom reveal animation from ux-bloom-reveal.html as the foundation. This is the screen that makes people cry. It's the reason the whole app exists.
🌱 Family
$0 — Same at both levels. This is pure UX — the animation, the reveal, the emotional moment. Use ux-bloom-reveal.html as the starting point. No encryption/decryption difference here because the content is already available at the family tier. The magic is the design, not the plumbing.
🏢 Scale
Same + decryption — At scale, content must be decrypted on the fly before display. Adds a loading step and key management. The UX is identical — the viewer shouldn't know or care about what's happening behind the curtain.
✓ Done when: Tapping the notification link opens a screen that reveals the seed beautifully
Depends on: Step 06 · Reference: ux-bloom-reveal.html (existing animation)
Ashley + Claude
08
The Field Homepage — Your Garden at a Glance
The home screen after login. Shows: total seed count, next bloom countdown, and a vault list (open + sealed + bloomed). This is where you feel the weight of what you've planted and the anticipation of what's coming. Keep it simple for MVP — the dandelion visual system and advanced animations come later.
🌱 Family
$0 — Same at both levels. This is a dashboard page: vault list, seed count, next bloom countdown. Pure frontend + database queries. No difference between family and enterprise. Use the existing UX mockups as a guide and keep it simple.
🏢 Scale
Same — At scale you might add: activity feed, gardener avatars, dandelion visual system, day/night mode. But the core Field homepage is the same build at any scale.
✓ Done when: Field homepage shows vault list, seed count, and next bloom countdown
Depends on: Steps 01–07
Ashley + Claude
09
Polish — Turnstile, Health Check & Monitoring
Final MVP hardening: Cloudflare Turnstile on signup and planting flow (privacy-friendly bot protection, free), a health check endpoint for monitoring, and Grafana Cloud observability (free tier) to watch for issues. This is the "production-ready" pass before inviting real users.
🌱 Family
$0 — MOSTLY SKIP FOR NOW — For 10 family members, you don't need bot protection, monitoring dashboards, or health check endpoints. Cloudflare's built-in DDoS protection (free with Pages) already covers you. What skipping means: if the app goes down or has a bug, you'd find out because someone texts you "it's not working" — not because a dashboard alerted you. No automated bots will try to sign up because nobody knows the URL except your family. Risk level: very low — the worst case is a few hours of downtime you don't notice right away. One quick add worth doing now: Cloudflare Turnstile on the signup form — free, takes 5 minutes, prevents any future bot signups if the URL ever gets shared publicly. When to add the rest: Before any public launch or press. Grafana monitoring matters when strangers are using the app and you can't just text them. Budget one 30-minute session with Claude for Turnstile now, and one build session for Grafana + health checks before public launch.
🏢 Scale
Free tools — Cloudflare Turnstile on all forms (free, privacy-friendly), health check endpoint for uptime monitoring, Grafana Cloud free tier for observability. All free services — the cost here is build time, not money. Worth doing before public launch to catch issues early.
✓ Done when: Bot protection active, health endpoint live, Grafana dashboard showing basic metrics
Depends on: Steps 01–08 · All free services
Ashley + Claude
Deferred from MVP (moved to later phases)
Invite Links / Grove Access — Was Step 09 in the old roadmap. Grove (multi-contributor vaults) is now Phase 4. Invite links ship when Grove ships.
Video Upload — Was part of Step 05. Video seeds are Phase 2 (encoding complexity + Cloudflare Stream costs).
SMS / Twilio — Email-only for MVP via Resend. SMS can be added later if needed.
MFA — Not at launch. TOTP (authenticator app) within 60 days of launch.
Phase 0 + Phase 1 Summary
Phase 0: 5 setup steps — decisions and account setup before writing any code
Phase 1: 9 build steps — Ashley + Claude build together, one session at a time
🌱 Family path: $0/mo (D1 free + Workers free + Pages free + R2 pennies + Resend free) · 🏢 Scale path: ~$10–20/mo (Workers Paid $5 + R2 storage + Hive AI $1.50 + Resend)
Full 10-phase roadmap documented in dandyline-app/docs/platform/roadmap.md
$0/mo
family path

What People Are Saying

Ideas, questions, and reactions submitted through the landing page widget. Future in-app customer feedback will appear here automatically too.