docs/architecture.md

Waterleaf Architecture

flowchart LR
    U[Gardener] --> G[Gradio Blocks]
    G --> A[FastAPI application]
    A --> O[Hugging Face OAuth]
    A --> S[(Local SQLite\nbucket snapshot + images)]
    A --> M[Modal proxy-auth endpoint]
    M --> L[llama.cpp\nGemma 4 26B-A4B GGUF]
    A --> B[GBIF taxonomy]
    A --> P[Local care baseline catalog]
    A --> W[Open-Meteo]
    A --> I[Whole-garden ICS]
    I --> C[Apple / Google / Outlook]

Identification

1. Gemma extracts visible traits, candidate names, container status, and size.
2. GBIF resolves names to valid Plantae species records.
3. Gemma reranks only those records. Unknown keys are discarded.
4. The user confirms a candidate or replaces it through taxonomy autocomplete.

Scheduling

The local catalog provides a baseline interval for supported species; users enter one explicitly for other plants. Waterleaf shortens the interval for containers, applies bounded rain and heat adjustments to the 16-day forecast, and labels later dates as seasonal estimates. The language model never chooses watering dates.

Privacy

HF username is the private ownership key. Coordinates are rounded before storage. Public plant profiles use opaque slugs and omit account and location data. Uploaded images are resized, converted to JPEG, and stripped of EXIF.