deprecated-api
Junior engineer Priya Nair expects routine work: retire an old weather API by June 1st. She finds something else instead—hundreds of orphaned systems still calling: a dead botanist's greenhouse requesting forecasts every hour, a hospital ward medication scheduler still running eighteen months after closure, a weather station checking the dawn from a rooftop where its owner died two years ago. As she traces each caller's origins, the API begins generating impossible responses: undocumented fields that accumulate like sentences, data that shouldn't exist, a countdown visible only to those paying attention. She has until June 1st to understand what's happening—ten weeks to trace each connection, each loss. But sitting beneath every question is a harder one: what does it mean to be the last thing that acknowledges something exists? And what's lost when you turn it off?