Regulatory liability - putting your ability to work in jeopardy should you drop the ball, not standard business liability.
Still, what you describe is good business practice for any complex project - you can’t catch everything all the time.
So why is it so important for you to call yourself an engineer?
Computer and Network Engineering are general offshoots of Electrical Engineering - they aren’t new as you state. You can get registered as a PE in Electrical Engineering, and contrary to what you may have heard, you CAN pass the test with a computer/networking background.
Unfortunately, you do not exhibit the temperament to be in responsible charge of anything if you insist that nobody can review your work. If your work is good enough, and your design is properly documented and is solid, it can be reviewed by someone with a reasonable skill level in networking.
I don’t know if this is you, nor am I accusing you of this, but what most folks doing “network engineering” do is rely on vendors to help put their designs together, and then rely on the performance claims of vendors, and interoperability claims of vendors.
You assert that it is somehow too complex for a technical person to review your work in a responsible charge capacity- and if you were an engineer, you would recognize that this highlights a failure in your design - that it is not documented sufficiently, and that your technical arrogance will be your downfall.
Your assumption that no regulatory liability applies to networks only proves my point that you do not understand the current situation in network engineering.
Why is it important for anyone to call themselves “engineer”. Why cant the structure be three parts
[licensed / certified ] Licensed by the state or certified by the vendor
[discipline] civil / electrical / network / etc
[level] technician / engineer / architect / consultant
Sorry, Computer and Networking are offshoots of mathematics not electrical engineering. I have fired EE’s because they could not perform the job required. One even had his masters in EE.
Unfortunately you do seem to possess the intelligence to understand complex systems. Do you want a civil engineer to review the desins of a 757? How about a home architect reviewing the designs of a nuclear power plant? I would venture to say that most complex systems can not be reasonably reviewed by a mid level skill set.
Not only have I worked for several of the network vendors and in one case, engineered their own internal voice video and data backbone, I have served on design teams, technology teams and even have been the highest level of support for customers. This includes PSTN carriers and their central offices and backbones.
However, I no longer perform in that role.