Scorecard
This page answers the hardest evidence question on the site: did Verdify make useful greenhouse decisions, or did it merely create plans?
The scorecard is not a single number. It is the relationship between:
- what the forecast said would happen
- what the planner decided to do
- what the greenhouse actually experienced
- how much stress, water, and cost remained afterward
- what lessons were extracted for the next cycle
For the exact parameters the planner can change, see AI Tunables Traceability.
Use this for the continuously refreshed panels. The static snapshot below is the crawler-friendly proof layer.
Current scorecard
Static public API snapshot: 2026-08-17 08:25 MDT. Source: evidence snapshot JSON and scorecard API. These values are crawler-friendly receipts; use the live dashboard link above for continuously refreshed panels.
Today's planner score
Both-axis compliance (binary, house)
Temperature compliance
VPD compliance
Stress-axis hours
Last validated plan
Validated 2026-08-17 06:15 MDT with outcome score 4.
Written 2026-08-17 06:20 MDT; age 2.1h at snapshot time.
Total stress-axis hours can exceed wall-clock hours because temperature and VPD are independent stress axes.
On convective/variable-cloud days, an accurate outdoor-temperature forecast does not validate the solar forecast: solar can exceed the predicted peak by more than 3x and create multi-hour heat/VPD-high stress. Keep morning thermal lead and moisture authority live-edge-triggered and band-coupled rather than suppressing them from a low solar forecast alone.
Did the plan improve the outcome?
What to inspect: score trend, both-axis compliance, and stress-axis hours over the last 30 days.
The compliance panel is percent only: temperature compliance, VPD compliance, and total compliance when both axes are inside the firmware-enforced band.
The stress panel is time only: temperature stress hours, VPD stress hours, and total stress hours. Total stress can exceed 24 hours because temperature and VPD are independent stress axes.
Forecast, band, actual
What to inspect: forecast pressure, the actual-to-forecast firmware compliance band, and the actual greenhouse response across the current planning window.
These panels are the direct decision story. The forecast is the external pressure. The stitched green firmware band shows what the ESP32 considered compliant historically and what the dispatcher projects next. Crop target provenance, cfg readbacks, trigger thresholds, and padding math live in the traceability tables rather than as extra trend lines.
The planned posture maps back to bounded parameters in AI Tunables Traceability.
Compliance and accuracy
What to inspect: waypoint compliance and forecast/plan accuracy grouped by day.
Compliance is waypoint-level: planned setpoints compared against actual hourly extremes. Accuracy groups those checks by day so the pattern is easier to inspect.
Tradeoffs
What to inspect: whether water and cost increases correspond to meaningful stress reduction.
The goal is not to minimize cost or water in isolation. The goal is to spend them when they buy meaningful stress reduction.
Journal and lessons
What to inspect: plan outcomes, extracted lessons, and whether repeated lessons have become useful operating constraints.