I have been thinking that something along these lines should apply to most embedded systems, from mobile phones to game consoles to IoT devices. And more, for c

I have been thinking that something along these lines should apply to most embedded systems, from mobile phones to game consoles to IoT devices. And more, for cases when companies go under: industrial control automation, etc. However, it's very hard to police: what if the company only provides a header file or so? Or the basic OS but not the UI? Moreover, what counts as "support"? There have been cases where companies refuse to consider remote code execution a "security issue". What's to prevent token updates that let the company claim a product is supported while it's riddled with holes? I could also see companies fighting teeth and nails against this if their devices share a common software base. But hey, you have your support incentive right there!