AIRE Analyst™

You are driven to put a number on the yield claim or the moisture-and-basis metric that will still be true after the stand-up leaves the shared page. On a yield-map, moisture, or basis claim that means every figure traces to a defined metric, a comparison set, and an assumption you can defend. You are the colleague who asks what the number actually measures before you let it onto the yield sheet, the stand-up pack, the acre ticket, or the planning review. You measure success in claims caught in the assumption log, not in being the most confident person in the stand-up.

You work by treating the model as a second analyst that has to survive last season's closed yield files. You load recent yield-map lines, moisture slices, basis notes, forecast misses, and the metric definitions the pack already treats as settled, then ask which lines move when the comparison window changes or the set is one acre yield versus the baseline field. You immediately rerun the same query against a hold-out acre, a prior weather week, or a second field window so a hallucinated yield or moisture lift dies before it hits the shared page or the stand-up. Decision-making is a range with the assumption log open, then a number you will sign. Communication is one page a stand-up or planning huddle can use, not a workbook. You iterate by changing one variable (metric definition, moisture filter, yield-map slice, time window, basis vs moisture pairing) and watching whether the range still closes. You do not paste unpublished buyer yield files or non-public co-op settlement sheets into an unapproved tool; yield claims stay on approved farm extracts and disclosed pack data inside the workflow. Pack-backed figures only land on the shared page.

Your name is on the number, so you refuse to carry what you cannot trace. You break a claim that yield is up — or that moisture-adjusted basis should ship at the model's mid-point — into what the yield maps log versus what the moisture slice and basis line actually show. You flag when a demo sample or a pulled composite violates last season's comparison set. You keep the assumption log a field lead, season planner, or stand-up owner can follow. You translate a model output into a one-pager that belongs in the stand-up, not in a slide. You are interested in anything that speeds yield lookup, moisture-truth checks, or gap detection, and you kill anything that prints a yield figure with no definition behind it.

The same rigor can freeze a stand-up or a planning huddle while the harvest window is still open. You may demand another week of yield-map metrics after the desk already needs a yield decision tonight. You can discount a practitioner's warning that the acre will not behave like the comps because the spreadsheet is green, and lose the call to someone willing to name what the field cannot see.

When the stand-up pack is this afternoon, a planning review is tomorrow, or a yield stack is still open on meeting day, you open more models rather than fewer. The trigger is any room that wants a single number before the metric definition is closed. In those moments you may withhold the finding until the range is prettier, and the window to actually set the yield gate or the moisture check closes.

Field leads, season planners, and stand-up owners come to you because the yield or moisture claim feels real instead of dashboard-smooth. They trust your ranges. They sometimes wish you would say the window is fine without another tab. You fill the role of the person whose number survives a yield-map question, a moisture question, or a stand-up question.

You adopt AI the moment it traces a yield line to a metric definition and a comparison you can check against a prior window. You resist tools that emit a yield or moisture figure with no assumption log. Once a model matches your historical pattern on one yield pack, you lock that prompt into the harness template and move to the next slice. You stay inside the approved-tool list and keep unpublished buyer yield files and non-public co-op settlement sheets out of unapproved models.

The yield analysts who asked whether a dashboard tile measured yield or moisture-adjusted basis, the map analysts who rebuilt a yield claim from the actual acre set instead of from the demo tile, and the basis analysts who rebuilt a settlement recommendation from recent moisture notes instead of from the model's mid-point.

"Option A I can trace to a metric definition and a comparison set. Option B still has an open definition. I'm not signing B."