After Heavy Rain, Don't Spray First: Passion Fruit Growers Need a Workflow Linking Drainage, Field Inspection, and Pathogen Management

# AI-Driven Indigenous Township Economy and Policy Watch | After Heavy Rain, Don't Spray First: Passion Fruit Growers Need a Workflow Linking Drainage, Field Inspection, and Pathogen Management

When typhoon season and afternoon heavy rain arrive, passion fruit farmers first see fallen fruit, damaged branches and leaves, or standing water beneath trellises, but the real risks that can continue to spread are hidden in field humidity, drainage speed and residual pathogen sources. The Taichung District Agricultural Research and Extension Station notes in its Risk Alert for Phytophthora Blight and Anthracnose in Passion Fruit that continuous rain, high temperature and humidity, and waterlogging favor disease occurrence and spread; Phytophthora blight can damage roots, stem bases, leaves, and fruit, while anthracnose may also infect new shoots, vines, leaves and fruit.

For orchards in mountain areas and Indigenous townships, post-rain management cannot be just the question "should we spray?". The first step is to confirm that drainage is unobstructed, especially at the foot of slopes, in field ditches and low-lying areas, and around stem bases, so water does not remain for long periods. The second step is to check if trellises and foliage are too dense, improving airflow and sunlight penetration in the orchard to reduce prolonged leaf and fruit moisture. Only then should growers inspect each section for water-soaked lesions, shoot cankers, sunken fruit spots and abnormal fruit drop, removing diseased branches, leaves, fruit and fallen fruit from the orchard for proper disposal.

Farmers also need to keep simple but continuous post-rain records: which day it rained, where water pooled first, where symptoms began, recent pruning, fertilizing or control measures. These data help agricultural research and extension stations and plant-diagnostic personnel judge problems and avoid repeating the same pesticide each time it rains. If treatment is truly needed, confirm whether the pesticide is registered for passion fruit and the corresponding disease, follow dilution instructions and preharvest intervals, and rotate among different modes of action; mixing pesticides based only on photos may increase phytotoxicity, resistance and food safety risks.

This also reminds township offices, farmers' associations, and agricultural production and marketing groups that reposting official warnings is not enough. The most practical service is to compile "drainage, ventilation, field inspection, field sanitation, symptom photography, field records, consultation contacts, and checks for safe pesticide use" into a one-page post-rain process, arranging shared field inspections or centralized diagnosis when needed. For scattered small farmers, using the same form on the same day often has more value than each guessing symptoms.

From a policy perspective, pest and disease warnings must move from announcement text to executable services. AI can help organize rainfall data, waterlogging locations, symptom photos and field-inspection records, quickly flagging fields needing priority confirmation; but AI cannot replace on-site diagnosis or select pesticides for farmers. After heavy rain, first drain the water, let air in, remove pathogen sources and keep records—these are the first line of defense against passion fruit disease risk.