baseURI is assigned in the constructor with no way of updating it in the future. The approach used by tokenURI prevents using IPFS since that would require knowing all potential tokenIds in advance. It may work with Arweaves append only file system, but the intended baseURI protocol is not clear from the docs or tests.
If these are to be hosted on a custom domain, it may be even more important that the baseURI is mutable, allowing it to be transitioned to a new store if that domain were to become unavailable (such as due to a security incident, trademark issue, or the host otherwise becoming unavailable in the future).
Alt: clarify in the docs the intended baseURI, to make it clear how permanence is guaranteed if thats part of the current launch plan.
