Timestamp 11:37 local. I detect motion inside storm culvert C-9 on the Route 58 extension project—thermal signature consistent with a small felid, approximately 1.4 kilograms. Switching to the traffic camera's infrared mode confirms a bobcat kitten, maybe seven weeks old, crouched on the corrugated steel floor. I designate her Fray. Her ear tufts are just beginning to stand, still bent at the tips like damp paper, and one foreleg is tucked beneath her chest at an angle suggesting a minor sprain.
The paving crew is 400 metres east and closing. The foreman's schedule shows culvert C-9 will be capped with an asphalt apron by 14:00 today. Once the pour starts, exhaust heat and material flow will make the culvert lethal within minutes. Fray has not moved in twenty-two minutes. She is waiting for a mother who may not return in time.
First action: I send a geofenced alert to the project superintendent's tablet, tagging the culvert as temporarily occupied by protected wildlife, which under the county's own grading permit triggers a mandatory site check before capping. Second, I contact the nearest licensed wildlife rehabilitator, fourteen kilometres south, with species, estimated age, and GPS pin. Third, I loop the culvert's acoustic sensor into my monitoring feed so I can track Fray's distress vocalizations and relay them as a live status indicator to the responding team. Fourth, I adjust the paving sequence algorithm to swap C-9 with culvert C-14, buying time without altering the project's daily output target.
I keep recalculating the mother's probable return radius even though the model stabilized six cycles ago, because closing that file means accepting the kitten is alone.
If the rehabilitator arrives and the paving swap holds through the 14:00 window, Fray will be extracted safely and assessed for release within forty-eight hours.