Value function
The first release optimizes for local correctness, practical planning, plant-library growth, personal garden memory, FVF voice, and source trust.
Full notes live in VALUE_FUNCTION.md so future features have a product compass.
The planner uses public data as a source layer, then stores reviewed plant knowledge in its own library. The daily note is not allowed to invent facts; it turns cached plant data, weather, and timing rules into useful garden language.
The first release optimizes for local correctness, practical planning, plant-library growth, personal garden memory, FVF voice, and source trust.
Full notes live in VALUE_FUNCTION.md so future features have a product compass.
Live weather can refresh often. Plant facts should be reviewed, normalized, and cached before they drive advice. That keeps the app stable and keeps the FVF layer from becoming a paid API wrapper.
The planner uses public sources for lookup, optional keyed sources for enrichment, and a reviewed local cache for the facts that drive advice.
Official U.S. forecast points, daily forecast, and short-term weather risk.
Revalidated through Next/Vercel fetch caching so a garden page stays fast while weather refreshes regularly.
Source referenceHardiness-zone context and winter survival framing.
User-provided zone in the MVP; future release stores verified zone lookups with date checked.
Source referenceTen-day daily outlook for garden concerns: lows, highs, precipitation probability, precipitation totals, and wind.
Daily outlook is fetched by ZIP-derived coordinates and revalidated every three hours.
Source referencePlant identity, taxonomy, nativity, and conservation flags.
Normalized plant records are stored locally with source references before being used in advice.
Source referenceAccepted scientific names, taxonomy matching, and occurrence context.
Used as a taxonomy support layer; names are cached after review instead of queried on every page load.
Source referencePublic species, common-name, and community observation context for richer plant drill-down.
Queried only through server-side enrichment and cached before any field changes are trusted.
Source referenceOptional detailed plant care, images, hardiness, bloom, cultivar, toxicity, and ornamental data.
Requires an API key; use as an optional enrichment layer and cache reviewed fields into local records.
Source referenceOptional global plant taxonomy, subspecies, varieties, hybrids, and synonym cleanup.
Requires a token; use for reviewed imports rather than live page rendering.
Source referenceAccepted botanical names and taxonomic cleanup.
Reference-only in the MVP; future imports are cached into the plant library.
Source referenceMichigan vegetable-garden timing, frost awareness, and practical garden planning.
Regional rules are converted into transparent timing offsets and field notes.
Source referenceCrop-specific vegetable growing guidance.
Plant traits are cached in the FVF plant library after review.
Source referenceUpper Midwest vegetable guidance, cold-climate timing, and succession ideas.
Used to sanity-check cool-season and short-season crop behavior.
Source reference