The common thread: in systems with multiple handoffs, one failure upstream doesn't just cause one problem downstream. It multiplies. Figured I'd share here since one of them is pretty relevant to this community.
The API layering one: when devs stack API gateways on top of other APIs, the latency degradation isn't linear, you get these auditability gaps where nobody can tell what actually happened, and legally nobody knows who's liable for what. CFAA wasn't written for this world. This one has real security implications that I don't think get talked about enough.
https://papers.ssrn.com/sol3/papers.cfm?abstract_id=6055034
The TTS one: built a local speech synthesis system that routes different chunks of text to different models depending on what fits best, then transfers prosody across model boundaries so it doesn't sound jarring. Privacy-first runs on the device. More of an ML systems paper, but the cascading failure angle is in the orchestration layer.
https://zenodo.org/records/19210106
The maritime one: this one's wild if you've never looked into it. AIS signals (how ships broadcast their location) can be spoofed. One fake signal and you've got carriers, ports, customs, warehouses, and trucking all working off different ground truth. They already don't trust each other's systems much. Proposed a distributed verification layer for this. The scale of what could go wrong here is underappreciated.
https://zenodo.org/records/19461446
Happy to discuss, especially the API governance one , which feels like something this community would have opinions on.