no StartEncrypt API now, later it will support IETF ACME, maybe open source.Apparently, "substantially negative".
Grabbing an open-source ACME implementation really is the canonical value proposition for open source. Work together to make it secure, every individual contributor (once it exists) does less work over all, and even had they successfully implemented StartEncrypt the first time, the value would be in hosting it and attaching their reputation to it, not the API design. So even the usual objections to using open source in a commercial setting hardly apply. There's not much in the way of "look and feel", and no matter how this was going to happen the actual "polish" was going to be done by creating a new website that they could make as polished as they like with no trouble.
In other words, they have comprehensively flubbed this. Even once the code is fixed, the reputation damage is done.
Don't. Implement. Crypto.
If you're curious if there are any rules for CAs that describe how domain validation must be performed, the current Baseline Requirements can be summarized with "do something that's safe" on that topic. A working group within the CA/B Forum[1] is currently working on revising the document and adding explicit rules declaring which methods are permitted. I believe [2] is the latest draft.
[1]: https://cabforum.org/mailman/listinfo/validation
[2]: https://github.com/cabforum/documents/pull/25/files?short_pa...