> We need a guild of software engineering

The threat of professional exclusion is one of the big levers provided by such a guild. Given the way tech companies behave, why do you believe that this lever will be left in the hands of good people, and not taken over (like the rest of the internet)?

I think there are more developers opposed to the recent web attestation shenanigans than those for it (even those who might be coerced into being for it by their employer). A majority guild vote could stop everyone working on it and keep the web open.

Who accredits someone to join this guild? Who holds the keys?

Yes, and if you can hold and retain power over the guild then the power of professional exclusion exceeds the coercive power of any one employer. But when your threat model includes adversaries who are willing to subvert the entire open internet to get their way, how do you harden your guild against this attack?

> new software and hardware is being developed or rolled out right now that is incapable of working on an IPv6 network

I would be shocked if this were true for hardware. Even for software, every major OS in the last 10 years as supported IPv6, and prefers it over IPv4

I’m sure there’s horror stories, but I doubt it’s systemic.

> prefers it over IPv4

That's the problem. If the OS starts using IPv6 preferentially but the software on top can't handle it, then you get a crash.

E.g.: if you turn on IPv6 for DNS and it starts returning AAAA records instead of A records, then a lot of applications fall flat on their face.

Usually the type written in C and insisting on maintaining compatibility with whatever Berkley did in the 1970s.

Some enterprise software I guess? I have native IPv6 since 2010 and can't remember a single software that crashed because of it.