Where do I start?
Starting a new plant from seed, cutting, runner, crown/division, tuber, or transplant?
Start in Propagation. Record what you actually did. The app then creates the Stage 1 Garden batch and, when you want succession, creates or updates Planning from the same information.
Recommended flow: Planning → Propagation → Garden State → Today reminders → Harvest. Planning drives timing, destination and quantity. If you make an intentional ad-hoc propagation start instead, the same entry can create or update Planning automatically when succession is enabled — never re-enter the crop information.
Known healthy units
—
from Google Sheets garden state
Production target / gap
—
no target is invented when a crop goal is not configured
Open garden actions
—
confirmed garden actions + pending tasks; data cleanup excluded
Quick actions
System readiness
Live production pipeline
Calculated from the connected Garden State and active succession targets. No Sheet dashboard formulas are required.
What should I do next?
Garden work first. Older-batch cleanup is separated below and does not inflate the action count.
Use Garden State to manage plants that already exist.
If you are starting something new from seed, cutting, runner, division/crown, tuber, or transplant, go to Propagation first. If a plant is already physically growing and you are only bringing it into the app, use Add existing plant.
Garden State
Live batches, stages, systems, containers, and locations. Use this tab to update what is already growing.
| Crop | Qty | Healthy | Stage | System | Container | Status | Action |
|---|
Independent Crop Library
Reference knowledge is separate from current garden state. Add several custom crop/variety records to the working cache, review them, then save them to Sheets together.
Planning can come before Propagation.
Use Planning first when you want to evaluate what should be started, how many, where it should go, and when. Nothing is recorded as physically propagated until you execute the plan in Propagation. If you already know what you are starting now, begin directly in Propagation and let Planning synchronize automatically.
Succession Plans
Planning can come first. Use Planning when you want the app to tell you what, how many, where, and when to start; then execute the recommendation in Propagation. If you already know what you are physically starting today, you can begin in Propagation and let it create/update the plan. 3X3X means at least three crop varieties moving through the production pipeline every three weeks — not three plants.
Succession & Forecast
Decision engine rules
Gap and starts required are separate values.
Propagation may use seed, cutting, runner, division, crown, tuber, or cold treatment.
Capacity checks use equipment status, container compatibility, crop compatibility, current occupancy, season/environment notes, and known dimensions. Unconfirmed measurements remain warnings—not invented facts.
Gardyn 2.0 — Study: indoor climate-controlled vertical hydroponic system with 30 planting positions. Planning treats it as year-round capacity and calculates occupied/open positions from active Garden batches assigned to the Gardyn.
Planned propagation dates become Today actions; destination conflicts are warned before the move is written.
Hydroponic transplant routing: capacity is stage-specific. A crop may begin in a Ziploc/propagation tray or small net cup, use a temporary staging container, then move through larger net cups or another table before its final grow-out position. The plan must reserve downstream space by due date rather than treating the starting hole count as mature capacity.
Outdoor routing: propagation can remain flexible until the crop reaches its required transplant window; final outdoor spacing is checked when planning the grow-out destination.
START HERE for a new plant.
Use Propagation when you start from seed, cutting, runner, crown/division, tuber/root stock, purchased cutting, or transplant. You enter the facts once. The app resolves the crop profile, uses the method you actually chose, creates Stage 1 in Garden State, and—when succession is enabled—calculates and updates Planning from the same event. Later rooting/germination results feed back into the linked Garden batch and plan history.
Propagation integrity
Active Propagation
Starts remain here while rooting/germination success is pending. If the original start quantity was entered incorrectly, use Correct quantity started; this corrects the Propagation record and linked Garden batch without creating a duplicate.
Harvest guidance is crop-specific.
The app uses the Master Resource harvest type, regrowth interval, yield notes, your production strategy, and recorded harvest history. The default objective favors the best practical usable yield; change it only when you want a different result such as seed production or whole-head harvest.
Harvest & Production
| Date | Crop | Amount | Unit | Disposition |
|---|
Tasks & Maintenance
Recurring maintenance resets from the day you complete it. One-time/event tasks keep their event date and do not drift.
Vermicompost quick log
Log what physically happened today. These are completed maintenance records, separate from future reminders.
Recent maintenance
Inventory & Purchases
Manage seeds, purchased plants, equipment, containers, reusable components, consumables, nutrients, biological inputs, and refunds from the app. Historical purchase cost remains auditable even when an item is used up or retired.
📷 Scan receipt, order, or product photo
Start here when you have purchase evidence.
Upload a JPG, PNG, WebP, or PDF — or copy a receipt/order screenshot and paste it here with Ctrl+V. The Command Center reads the evidence, opens the purchase review, preserves what you actually paid, and can research the identified model for equipment dimensions and capacity. Nothing is written until you review and save.
COPY → PASTE: Copy the receipt/order image, click “Paste copied receipt / screenshot,” then press Ctrl+V. The app will show “Reading purchase evidence…” immediately.
Seeds, plants, supplies & purchased inventory
| Date | Item | Category | Purchased | On hand | Status | Net cost | Action |
|---|
Equipment & capacity
Capacity changes affect current/future planning. Growing containers, hydro systems, VermiHut/composters and other capacity-critical assets are flagged when planning specifications are missing. Give the manufacturer/model when known; the Command Center researches missing specifications. User measurements remain editable and keep their provenance.
Unknown dimensions/capacity remain unknown until researched or measured — never guessed.
| System / equipment | Status | Capacity / specs | Occupied / open | Environment | Containers | Action |
|---|
Harvest value
$0
Operating costs
$0
Documented garden purchases
$0
Durable / reusable investment
$0
Inputs / seed / plants
$0
Net modeled value
$0
Equipment, inputs, refunds & resource payback
Purchase records keep item price, shipping, tax, refund, status, and net attributable cost separate. Fully refunded purchases remain auditable but contribute $0 to investment. Mixed orders never receive invented tax allocations.
Knowledge & Provenance
Reference defaults, garden state, goals, computed values, overrides, and learned values remain separate.
Gardyn 2.0 — Study: indoor climate-controlled vertical hydroponic tower, 30 planting positions, operational, year-round planning environment. Occupancy/open positions are derived from current Garden batches assigned to the Gardyn.
Known source conflicts remain visible: Flood Table 1 strawberry capacity is recorded as 21 net-cup positions in one source and 22 plants in another; Terraform 8 remains planned until explicitly marked operational.
Appearance
Preview a built-in style without changing garden data. Apply only when you like it.
Preview: Garden Green
Browser & garden settings
Data controls
Google Sheets is the source of truth for connected garden records.
Start-fresh operational reset
This empties the current operational garden so you can re-onboard everything cleanly.
It clears current Garden batches, propagation, succession plans, scheduled/legacy tasks, harvest entries, mortality entries, and the legacy Succession Planner data rows. Before clearing, every removed row is copied into an App Reset Archive sheet. The Crop Lookup Library, Garden Resource Master, equipment-capacity records, operating-cost/equipment economics, Update History, and App Change History are preserved.