What Happens When Two Voice Notes Give Opposite Spray Advice?

When two voice notes give opposite spray advice, a farmer needs a safe next step, not a third confident answer. AgriVoice should return only an agronomist-reviewed Twi response that fits the question, or send the case to a named extension officer.

A filter problem under real pressure

In 1970, Apollo 13 had a problem no one could solve by guessing. The spacecraft’s lunar module carried carbon dioxide scrubbers with round cartridges. The command module had square ones. After an explosion disrupted the mission, the crew needed a way to make the square cartridges work before carbon dioxide built to dangerous levels.

At NASA’s Manned Spacecraft Center in Houston, engineers worked from the materials actually available to the crew. The improvised adapter used items including plastic bags, cardboard, tape and a flight manual cover. It worked, and Jim Lovell, Jack Swigert and Fred Haise returned safely to Earth. NASA’s Apollo 13 mission record documents both the crisis and the workaround.

The lesson is not that every hard problem has a clever fix. The lesson is that, when the stakes are high, a team should work from verified constraints. They needed the right cartridge, the right materials, and a method that had been checked before it reached the crew.

A cocoa farmer can face a smaller version of that decision before breakfast. One voice note says to spray immediately. Another says to wait, use a different product, or mix something else. Both may sound certain. Neither voice note may include the product concentration, the right dosage, when people can safely re-enter the field, or the interval before harvest.

Confidence does not supply missing safety details.

Advice must stay inside what has been reviewed

AgriVoice is being built for Asante Twi speaking cocoa farmers as a constrained voice workflow. A farmer sends a question. The system identifies the appropriate reviewed content block. It returns that block in spoken Twi. It does not generate fresh agronomy instructions from a language model.

That boundary matters most for pesticide questions.

The product can safely answer a question only when a reviewed block covers it. It can give the farmer a clear observation step, explain a known safe practice, or share advice that a farming-aware translator and reviewer have approved for spoken Twi. If the question depends on a product name, dose, crop stage, weather condition, re-entry interval, or pre-harvest interval that is missing from the reviewed material, the answer changes shape.

It becomes an escalation.

This is deliberately less dramatic than a chatbot that always has something to say. It is also more useful than an answer that sounds fluent and leads someone toward an unsafe spray decision. Neuralis has already seen why translation alone cannot be trusted for this work: a translation test rendered the Twi word for cocoa, “kokoo,” as “chicken.” A polished sentence can still carry the wrong noun.

For chemical advice, the system should treat uncertainty as information. It should tell the farmer that the case needs review, preserve the relevant question, and route it to the extension officer responsible for the pilot.

What Happens When a Farmer Asks a Chemical Question With Missing Safety Details? explains why dosage, re-entry and pre-harvest guidance cannot be filled in from memory.

A named person must own the unresolved case

An escalation only helps if someone is responsible for it.

For the AgriVoice pilot, a cocoa-sector partner must name the extension officer who receives escalations before farmers are exposed to the service. That person is part of the safety system. A farmer should not send a voice note into a queue that has no owner, especially when rain, labour availability, or a spreading symptom makes the decision feel urgent.

The pilot will measure whether the escalation path works: who owns it, how quickly questions receive a response, and whether any unsafe instruction reaches a farmer. A useful answer includes a correctly handled handoff. Silence after a cautious refusal is not enough.

This also gives the team evidence to improve the reviewed blocks. If several farmers ask the same question and the extension officer keeps supplying the same safe answer, that may reveal a missing block worth reviewing, translating and adding. Until then, the human route remains the correct one.

The Extension Officer a Farmer’s Voice Note Needs, Before It Enters an Unowned Queue sets out why accountability belongs in the design, not in a later operations plan.

The useful answer may be “wait for review”

Apollo 13’s engineers did not send the crew a list of possible approaches and ask them to pick one. They worked toward a tested procedure using the equipment already on board. The outcome depended on reducing uncertainty before action.

AgriVoice should do the same with spray advice. Select reviewed guidance when the question matches it. Ask for the relevant observation where more information is needed. Escalate when safety details are absent or the case falls outside the approved content.

For a farmer deciding what to spray, that restraint protects more than the crop. It protects the person holding the sprayer, the people who enter the field afterwards, and the harvest that follows.