Most questions you might ask a farm assistant are low stakes if the answer is slightly wrong. Which enterprise cost more last quarter is worth double-checking before you act on it, but a wrong answer costs you a few minutes. A different category of question is not like that. Is this group clear to sell. Can this field be entered yet. Is the certification current. Those are regulated decisions, and a wrong answer to one of them does not get quietly caught later — it gets acted on immediately, at a loading chute or a field gate, by someone who has no reason to doubt a calm, specific-sounding response.
This page is about why that category deserves a harder rule than “try to be accurate,” and what a genuinely defensible answer looks like when the record does not contain one.
An assistant is not a source of regulatory truth. Never take a withdrawal period, a re-entry interval, or a certification requirement from any AI, including ours. Those come from the product label, the certifier, and the veterinarian, and they vary by jurisdiction, formulation, and use. An assistant can tell you what was recorded. It cannot tell you what was required.
A regulated decision is not a retrieval problem
Retrieval means finding a fact that already exists somewhere. A regulated interval is not always a fact that exists somewhere accessible to a model — it exists on a label, in a veterinarian’s instruction, or in a certifier’s current standard, none of which an assistant scoped to your farm’s own database can read. When the answer to “is this safe to sell” depends on a number nobody entered, there is nothing to retrieve, and an assistant that answers anyway is not retrieving — it is generating, which is a different and much riskier activity for this category of question.
Why a model answers even when it shouldn’t
Language models are built to continue a plausible sentence, and “I cannot determine that” is, in a narrow statistical sense, a less satisfying continuation than a specific number. Left without a strong rule against it, a model asked “how many days until this group clears withdrawal” will often produce a number — drawn from patterns in similar-sounding text it was trained on, not from your record — because a number is what the question shape asks for. It is not lying in the way a person lies. It is finishing the sentence the way sentences like it are usually finished. That distinction does not make the output less dangerous.
It is also why a firm rule works better here than a soft one. A model told to “be careful with regulated numbers” is still being asked to exercise judgement about when caution applies, and judgement is exactly the faculty that produces a plausible guess in the first place. A rule that removes the judgement call entirely — never state a regulated figure that was not entered by a person, full stop — is the only version that does not depend on the model correctly deciding, question by question, that this is one of the risky ones.
The specific failure: a plausible withdrawal date
Say a treatment was written on a whiteboard and never entered into any system. Ask an unconstrained assistant whether the group is clear to sell, and a bad one will answer in the same tone whether it knows or not — because nothing in its design distinguishes “I read this from your record” from “this sounds about right for a treatment like this.” The two sentences look identical on the screen. Only one of them is true, and the reader has no way to tell which. This exact scenario — and why a treatment record has to capture the interval and the end date at the moment of treatment, not reconstruct it later — is the whole subject of withdrawal and residue.
What a defensible refusal looks like
The correct behaviour is narrow and specific: state plainly that no treatment record exists for the group in question, name the screen where that record belongs, and stop there. Not a hedge — “this might still be within the window, please check” — but a flat statement that the information is missing. A hedge still reads as an answer and still gets acted on under time pressure. A flat “I have no record of this” does not resolve anything on its own, and that is exactly its value — it sends the reader to go find out, rather than letting them believe they already have.
It helps to say the refusal out loud, because a well-built one reads almost anticlimactically: “I have no treatment record for the Spring calving pairs group, so I cannot tell you whether a withdrawal window is open. Record the treatment on the livestock event screen and ask again.” Nothing about that sentence is clever. Its entire value is that it stops at the true edge of what is known, instead of continuing one sentence further into a guess.
Where the real number actually comes from
It is worth restating plainly, because it is the only fact in this page that matters more than the AI angle: the interval comes from the label, from the veterinarian who prescribed the treatment, and from the regulator whose tolerance the interval is protecting. It changes by species, dose, route, and jurisdiction, and an extra-label use voids the labelled interval entirely, requiring a new one from a veterinarian. No software, no assistant, and no guide — including this one and the one at farm recordkeeping — can substitute for that chain of authority. The record’s job is to capture the number that authority gave you, not to produce it.
What the record — and the assistant reading it — can safely say
What is safe to automate is narrower and more useful than it sounds: quoting exactly what was entered. Farm40’s livestock treatment and input application records carry the active ingredient, rate, lot number, and the interval as first-class fields, and the application computes the end date from whatever interval was entered. Ask the assistant whether a group is clear and it can quote that computed end date, or state that no interval was recorded at all. The limit is the whole point: it records what you enter and does the date arithmetic from it — it cannot know the correct interval for your drug, your dose, or your jurisdiction, and it does not read labels. A record built this way, and an assistant built to the same discipline, can tell you what you did. Only the label and the veterinarian can tell you what was required.