How the weekly brief is made
The rules are small, versioned, and written down here so a farmer or adviser can disagree with them on the record.
Deterministic, not generated
AgriView applies visible rules to normalized source snapshots. It does not use a language model to invent or rank farm advice. Every priority on the brief points at the rule and the source that produced it.
The pin is the working location
Routing-key search only centres an approximate area. The point you save manually remains in this browser as your profile; its coordinate is sent to AgriView’s data routes when the app loads point or nearby evidence. There is no server-side user profile. The point is not an official property or Eircode lookup.
Evidence keeps its scope
A point forecast is an estimate at the saved coordinate. Nearby, county, regional, and national evidence is labelled as such and is never described as field-specific. A weather warning says whether it lists your county.
Compliance stays a verification task
Scheme dates and environmental layers are prompts to check current terms, records, correspondence, and professional guidance. They do not decide whether an action is permitted.
Missing is not zero
When a source is stale, unavailable, or structurally invalid, the interface reports that state instead of substituting sample values.
Last-known-good has a time limit
A previously validated response may be reused only within its source-specific cache window. If its freshness time has elapsed, AgriView labels it stale. If no valid cached response is available and the source fails, the result is unavailable, never silently replaced.
The briefing rules, version 2026-07-18.1
Three thresholds decide the weather priorities. A Red or Orange Met Éireann warning that lists your county is always the lead; a Yellow warning is a check; a regional warning that does not list your county is only a watch. A verified DAFM deadline within 45 days joins the brief as a watch, or a check when the week’s focus is compliance.
- ground-access-rain
25 mm over available forecast days, greater than or equal.
A conservative product heuristic that promotes a ground-access check during a materially wet forecast.
Inputs: daily precipitation_sum. If unavailable: Do not run when complete daily rain values are unavailable.
- peak-gust-check
45 km/h, greater than or equal.
A presentation heuristic that calls attention to the windiest modelled day; it is not a spray or safety limit.
Inputs: daily wind_gusts_10m_max. If unavailable: Do not run unless at least two complete forecast days are available.
- driest-adjacent-days
2 mm, with km/h tie-break, at least two adjacent complete days.
A conservative comparison heuristic for ordering already-permitted work, never permission to act.
Inputs: daily precipitation_sum, daily wind_gusts_10m_max. If unavailable: Show insufficient coverage instead of inventing a window.