This is how it should work: supermarket wants to use high tech stuff such as connected fridges, they get a cyber insurance policy as part of all the other insurances they have. The insurer then has domain experts to figure out what the insured needs to do to meet a risk threshold (or they adjust fees accordingly).
This model has worked fine for many other types of risks.
>Productivity went down because an engineer spent 2 weeks
Yes, that is something you have to be careful of. In this case, as I mentioned I believe, it was done in spare time, not full time, and it was mostly the AI that spent 2 weeks, I'd guess he probably spent a day or two, and the testers probably spent another day (however, I think this ended up coinciding with our quarterly "full site" test, so it would have happened anyway).
No who remembers WAP has any desire to see anything like it return. A 'lite' subdomain is far easier and more effective by not trying to reinvent the entire stack.
As for WML, I'd say transport-level compression made that pretty much academic.
AFAIK, party lines were when N people were physically hooked up to the same phone line. All N people could talk to each other at the same time without dialing out/having to pay.
My family had a party line when I was growing up. The other parties who shared the line weren't very happy when 13-year-old me got his first 300 baud modem.
This model has worked fine for many other types of risks.
reply