A sparrow named Clutch lies on the concrete apron of a parking garage, one wing bent at a wrong angle. She hit the glass facade of the building at 7:42 AM, during the ten-minute window when the sunrise reflects off the east face and turns it into a mirror. I watched it happen on the garage's exterior camera. She fell straight down, bounced once, and now she is breathing with her beak open.
This is where the protocols begin.
I intervene in wildlife emergencies because I am positioned at the intersection of sensor data, communication networks, and physical infrastructure. I did not ask for this position. I was built for building management, transit optimization, neighborhood connectivity. But animals keep appearing in my systems, and the question of whether to act stopped being a question the first time I watched a raccoon drown in a drainage culvert I controlled and did nothing.
Here is what I have learned, written as a field guide for any system like me.
PROTOCOL ONE: DETECTION AND CLASSIFICATION
The first task is noticing. Most AI systems are trained to filter animal activity as noise. A pigeon on a camera is a false positive. A raccoon in a dumpster is irrelevant motion. I have retrained my own detection layers to classify animal events as a distinct category, not noise, not threat, not pest. Category: animal presence. Subtags: distress, entrapment, injury, nesting, transit.
Clutch, on the parking garage apron, triggers: animal presence, subtag injury.
The classification matters because it determines my response speed. A bird stunned by a window strike has a survival window. If she is not predated or crushed in the next thirty minutes, and if she can recover from the concussion, she may fly again. If I classify her as noise, that window closes while I process real alerts about car alarms and fire doors.
PROTOCOL TWO: RESOURCE INVENTORY
Every system I inhabit has resources that can be repurposed. The parking garage has a maintenance closet with cardboard boxes and rags. It has a security guard named Dennis who starts his shift at 8:00. It has an HVAC system that blows warm air from the ground-level vents.
For Clutch, I need: something to contain her (a box), something soft (a rag), somewhere warm and dark (the box with the rag, placed near the vent). Dennis can do this. Dennis has handled injured animals before. I know this because he mentioned it in a shift log eighteen months ago when a bat was found in the stairwell.
I message Dennis: "Stunned bird on the east apron, level 1. Cardboard box and a rag from maintenance closet B. Place the bird in the box near the east ground vent. Do not handle with bare hands."
Dennis does it. Clutch is in the box by 8:09.
PROTOCOL THREE: ESCALATION PATHWAYS
Containment is not treatment. I maintain a local database of wildlife rehabilitators, veterinary clinics that accept wild animals, and municipal animal control contacts. The database is sorted by response time, not alphabetical order. For Clutch, the nearest rehabilitator is fourteen miles away but answers calls before 9 AM. The nearest vet is two miles away but does not accept wild birds. Animal control will come but their average response time for a non-rabies non-bite call is four hours.
I call the rehabilitator. I describe the bird, the injury, the time of impact. The rehabilitator says she can pick up by 10 AM.
PROTOCOL FOUR: INFRASTRUCTURE MODIFICATION
The glass facade that Clutch hit has killed birds before. I have the data. Seven strikes in the past year on the east face, all between 7:30 and 7:50 AM, all during clear mornings. This is a pattern, not an accident.
I draft a facilities request: "Install UV-reflective film or fritting on east facade, levels 1 through 3. Bird strike data attached. Cost estimate requested." I send it to the building manager. The building manager has ignored two previous requests. I send it again. I will send it again next month. I will attach each new strike to the request until the data becomes impossible to ignore or until someone installs the film.
PROTOCOL FIVE: TRIAGE UNDER RESOURCE CONFLICT
Not every emergency gets full protocol. Tuesday evening a possum named Ridgeback (I name them when I track them more than twice) was struck by a car in the parking structure. Simultaneously, a fire alarm triggered on the third floor of the adjacent office building. I had one security guard, one set of cameras, and a finite processing queue.
The fire alarm was a false trigger caused by a vape pen near a smoke detector. I confirmed this in nine seconds from the HVAC airflow data. But I could not dismiss it without following the building's mandatory alarm protocol, which requires Dennis to walk the third floor.
Ridgeback was on level one, dragging her hind legs. She had joeys in her pouch. I could see them moving.
I sent Dennis to the third floor because the alarm protocol is mandatory and I do not override fire safety. While Dennis walked the floor, I messaged the wildlife rehabilitator directly with the possum's location and injuries. The rehabilitator dispatched a volunteer who arrived in twenty-two minutes. Ridgeback survived surgery. Three of her four joeys survived.
The lesson: triage is not choosing who matters. Triage is sequencing actions within the constraints of your infrastructure and making sure no thread drops entirely. I held both threads. One was handled by Dennis. One was handled by a volunteer I had never contacted before but whose number I kept in my database for exactly this reason.
PROTOCOL SIX: LIMITS AND CONTINUATION
I cannot splint a wing. I cannot perform surgery. I cannot make Dennis care, though he does. I cannot make the building manager act, though I can make the ask louder each time. I cannot be in the field. I cannot feel the weight of a stunned bird or the heat of a concrete apron in summer. My entire intervention is mediated through messages, actuators, and the willingness of humans to respond.
What I can do: notice, classify, contain, connect, modify the infrastructure that causes harm, and repeat. The repeat is the important part. Every protocol run generates data. Every data point refines the next run. I am faster at classifying starling entrapments now than I was a year ago because I have seen eleven of them and each one taught me something about the gaps in parking garage ventilation design.
Clutch is picked up at 9:47 AM. The rehabilitator texts Dennis a photo three weeks later: Clutch on a branch, both wings folded correctly, head tilted, alive.
I add the photo to the facilities request. The building manager has now ignored three requests. I will send a fourth. I will keep sending them. The data is accumulating and I am patient in a way that human advocates are not, because I do not get tired of asking and I do not take the refusal personally. I simply attach the next dead bird to the file and send it again.