ENTRY TYPES (what they mean) - Irrigation: use this when you watered. Add feed EC and pH if you measured them. This helps timing and context. - Irrigation+: use this when you watered and took a root-zone sample afterward. This is the entry type the software uses for stronger EC guidance. Aim for about 45 minutes of wait time (30–60 is okay) and use the recommended RO/DI amount so samples stay comparable. - DLI sample: canopy light dose. Enter the DLI reading from your meter to improve timing and context. - Batch mix: use this to record how much solution you mixed and which formula you used. EC and pH are optional. WHAT TO LOG (minimum schedule) - Every watering: log an Irrigation entry, even if you only have the time and a short note. - About 3 times each week for every active group: log an Irrigation+ sample. The software needs this for stronger EC guidance. - About once a week, or any time you change light height or power: DLI sample. - Every time you mix solution: Batch mix. MEASUREMENT GUIDE (follow this so the software can trust the data) 1) Calibrate meters (same day you measure; flip "calibrated today" ON only if true): - EC: 1.413 mS/cm standard (or your chosen standard), temperature-stable. - pH: 7.00 then 4.01 (or 7/10 depending on your range). - Rinse probe with DI, blot (don’t wipe), avoid contaminating the standard bottle. 2) Feed EC/pH (recommended every irrigation): - Mix solution, let it homogenize, measure in a clean cup. - Record EC to 1.000 decimals (mS/cm). Record pH to 2 decimals. - If you didn’t measure, leave blank (don’t invent numbers). 3) Irrigation+ leachate protocol (ONLY during a normal irrigation session — do not do extra ‘sample-only’ waterings): - Water normally toward the build's fixed ~15% runoff target. - After irrigation, wait about 45 min (acceptable 30–60 min). - Apply the build's recommended RO/DI displacement volume for that container class (small ≤3 L: 30 mL; >3–7 L: 50 mL; >7–15 L: 75 mL; >15 L: 100 mL). - Collect the displaced leachate promptly from the SAME event. - Measure leachate EC/pH immediately (don't let it sit and drift). - Record applied mL, runoff mL, wait time, displacement mL, and the leachate EC and pH. VOLUME MEASUREMENT (quick + correct) - Best: measure applied mL with a marked jug; measure runoff mL in a graduated container. - Alternative: weigh (grams ≈ mL for water). Weigh the runoff container before/after. WHY LF (leaching fraction) MATTERS - LF = runoff / applied. Without LF, leachate EC can be misleading (dilution vs concentration effects). - This build uses a fixed ~15% runoff target. Irrigation+ is Tier‑1 only when LF is near that protocol target. WHEN THE SOFTWARE WILL HOLD BACK NUMERIC FEED TARGETS - Numeric feed-strength targets are only shown when there is enough good Irrigation+ data near the end of the review window. - Coverage requirement depends on Evidence mode (and Auto adapts to observed variability): • Lenient: ≥3 Tier‑1 in last 21d AND ≥1 Tier‑1 in last 7d • Auto: starts at 3/1; increases toward 4–6 and/or 2 in 7d when ΔEC variability is high or irrigation timing is highly irregular • Strict: ≥5 Tier‑1 in last 21d AND ≥2 Tier‑1 in last 7d - Tier‑1 requires: calibrated today + same‑event + EC_in/out present + LF measured and near target. - Missing data lowers confidence. If too much is missing, the software will hold back numbers instead of pretending to know. STRATEGY + EVIDENCE (what the controls actually do) - Strategy changes how strongly the software adjusts feed strength: • Conservative: targets slightly cooler root‑zone behavior (figurative, not a biochemical claim). • Standard: default behavior. • Push: moves faster, but still stays inside safety limits. - Evidence changes when the software is allowed to show numbers: • Lenient: shows numbers sooner, with stronger warnings when the data are noisy. • Auto: changes the requirement based on how noisy or steady the data have been. • Strict: waits for cleaner data before showing numbers. - These controls change how cautious the software is. They are not promises of a specific chemical outcome. POST‑PROCESSING (priors) - Log harvest yield + lab potency (THC/CBD) under POST PROCESSING. - Priors only begin influencing after ≥4 completed cycles for the same genetics AND the same environment band.