We're quite far from implementing such a system for software "engineers".
We don't trust building ethics, independent inspector comes and checks if everything is as it should be before it can be used by the public.
Clients not being experts at the job they are getting somebody else to do is not a new pattern. So while some trust is required, it's best if you can get somebody else to verify.
I've seen a few smart clients over the years which when faced with some excuses from a software house hired another one to give them opinion about the codebase and capabilities. It seems pretty intuitive. It seems like a money well spent.
In fact, a whole lot of the time, the entire reason someone hires a professional is precisely because they themselves aren't experts.
Good narrative: but certification and guilds do not solve the problem.
For example: UK Grenfall towers. https://www.bbc.com/news/uk-61724373
It is a wrong to assume that only engineers can cause deadly mistakes. Also we have penal liabilities that don’t need licensing:
The [UK] Health and Safety at Work Act 1974 is designed to stop employers putting the public at risk, not just employees in the workplace. Individuals can be prosecuted and a serious breach could attract a two-year prison sentence.
And sometimes some pretty big exceptions: the [UK] government can't be prosecuted for corporate manslaughter
Locally to me in Christchurch, New Zealand, there have been no prosecution for the CTV tower collapse: https://www.nzherald.co.nz/nz/fatal-ctv-building-collapse-po... https://www.nzherald.co.nz/business/govt-considering-introdu... The second link is interesting because it looks at changing the law to add liability (not engineers licensing changes )In both cases, there are multiple layers of failure, and many causes could be asssigned. Especially the CTV building with inspections before collapse and warnings from people working there ignored.
You are talking Nirvana fallacy https://en.m.wikipedia.org/wiki/Nirvana_fallacy