I'm asking for simple language, accessible to a broad audience, which allows rules to be written so that most people applying them to a set of example situation

I'm asking for simple language, accessible to a broad audience, which allows rules to be written so that most people applying them to a set of example situations would arrive at the same results. Beyond that, what I'm suggesting is that it could be helpful to gradually make it easier for the public to view, comment on, and search proposed and historic legislative changes. Collaboration, tracking down bugs and coaching/mentoring in open source software is greatly aided by tools like GitHub; it's worth having concerns about whether such a service itself should be proprietary, but I do think the value it creates is worth looking at. If something similar could be created for legal texts, I think it's possible that there could be similar benefits. There may be risks, too. My suggestion isn't that we should devise a software system to implement the rules of the Frankenstein Veto; instead my theory is that the time-to-detect and time-to-recover from a process problem like the Frankenstein Veto would both be shorter in the presence of an open, collaborative, transparent legislative repository.