Complete decision-tree mapping of the Gardener's planting path — every button from the first tap of "Plant a Seed" through the final seal. This documents one entry point into DandyLine; recipients claiming a Seed Key, Roots arrivals, and Grove invitations are separate flows documented elsewhere.
Originally built as an open-questions map. As decisions resolved, the big ones were rehomed to their canonical product pages (product-seed-keys.html, product-vaults.html, brand-guide.html). This page is now the 8-step button-logic reference. See the "Decisions Logged" section at the bottom for quick links to where the big calls live now.
This map documents the Gardener's planting path — what happens after a Gardener taps "Plant a Seed." It's one of several entry points into a DandyLine experience. Some experiences begin with a bloom (a recipient claiming a Seed Key someone else planted long ago), some begin with arrival (walking into a Roots location), and some begin with an invitation (joining an existing Grove). This page covers only the planting side. What follows is a cascade of decisions that determines what the Gardener is planting, who it's for, when it blooms, and how it's delivered. Each choice narrows the path and reveals new options — a branching tree that adapts to the Gardener's intent.
This map documents every fork in that tree — what buttons appear, what conditionals they trigger, what sub-options emerge based on prior selections, and where the logic gets complex enough to require careful product decisions. Each step below is expandable. Click to reveal the full branching logic.
How to read this document: Start at Step 1 and follow downward. Each numbered step is a decision point the user encounters. Within each step, the colored pills represent the available choices. Sub-branches show what happens after each choice. Nuance callouts flag edge cases, conditionals, and unknowns. The Unknowns section at the bottom captures every open question that needs resolution before build.
The user's first choice: what kind of media is this seed? This determines the capture interface, file handling, and what the bloom experience looks like on the other end.
Vault type selection. This is the most consequential choice — it determines contributor structure, bloom behavior, sharing rules, and visual identity. The user shouldn't have to understand all five options. DandyLine should guide them with questions.
Recipient and sharing configuration. This step branches significantly based on which vault type was selected in Step 2. Each vault type has different recipient rules and sharing models.
Visibility and access controls. This is where sharing permissions, contributor visibility, and privacy levels are configured. Branches heavily based on vault type.
The bloom trigger — the mechanism that determines when the sealed vault opens. This is the emotional core of DandyLine: the distance between planting and blooming is where meaning lives. 7 trigger types available, with availability depending on vault type.
Date and timing configuration. This is where the nuance gets heavy: some planters know the exact date, some know the event but not the date, some don't know either. Each path has different UI requirements and downstream effects.
Countdown visibility, delivery method, and bloom-day experience. The final configuration before sealing. This determines what the wait feels like and what the moment of arrival looks like.
The final confirmation. This is the "planting ritual" — the moment the content becomes a seed, the vault becomes sealed, and the commitment is made. What the user sees and feels here determines whether DandyLine feels like a product or a ceremony.
One-line breadcrumbs only. Each resolved decision lives at its canonical home — click through for the full rationale. Open questions are tracked in biz-dev-homework.html (Quest · planting-flow-design), not duplicated here.