If you have 'known valid' legalese broken into segments and clauses (this already exists in platforms in use by legal professionals to speed up this process, bu

If you have 'known valid' legalese broken into segments and clauses (this already exists in platforms in use by legal professionals to speed up this process, but for legit purpose) and you can convert certain elements into variables (names, dates, addresses, and so forth), you can trivially make a 'valid' legal document that is nearly impossible to parse due to length, by referencing everything under the sun and stars, by introducing lots of situational logic that rests on references, or by simply relying on hyper-specific language and structure. For example, I've had to read quite a few 1,000+ page legal documents (Companies Act 2006 being one example) and that document gets referenced all the time. I can imagine tools like GPT-3 being used to crank things up to 11 to ensure that no user ever really reads or understands the TOS/EULA/whatever they're reading. Not that most people do anyway. > too complicated for normal humans, but acceptable for lawyers. I can totally imagine someone building a tool to parse generated garbage legalese into plain language bullet points and adding the proper visual references/links and document structure so that a human can read it. Perhaps it already exists and I'm just not aware of it.