Nice! But in the case of Govt, we need to clearly (re)define what actually constitutes an "effective dose" at a societal level. Too much time has passed from the creation of the original documentation and many things exist now that did not exist then. I think it's time for an update on both the user manual and the developer's API documentation :)

Think of trying to operate a current piece of software using the (printed and never updated) instruction manual from 1992 (let alone 1776). That would not go very smoothly. Since Govt functions sort of like civilization's operating system, then most people would agree that means to keep a "relatively smoothly running civilization" it is very important to keep not just the documentation up - the OS software itself needs to be up to date on patches and documentation. And only occasionally add new features - but only after extensive functional, regression and user acceptance testing...

Congress currently patches the things incessantly (new legislation) but in a seemingly random manner. I have yet to see anything resembling a comprehensive project development plan for how "enhancements" and bug fixes are elicited consistently from the customer/citizen base (oh wait, we're not the "real" customers anymore are we, even though we're paying for it), evaluated for both feasibility and affordability, or prioritized. There also does not seem to be any opportunity for code review - they promote freaking alpha code to production overnight without 98% of the "dev team" even getting a chance to read it once! And there's certainly little to no functional, regression or user acceptance testing before changes are rolled out to production. Hell, they don't even smoke test half the time :)

Without clearly defined criteria between what is required functionality vs what is excessive (unsolicited scope creep features) or defective (bugs) functionality, they keep on taking another foot (or 5280) every time you close your eyes to catch a nap (who even gets a full night's sleep anymore). OK, enough half-wired programmer analogies - maybe it's time to pull the plug for just a few minutes, roll back to a much earlier and less bug-riddled OS version release and reboot the damn system - while we figure out whether it's a massive code review/purge of buggy functions, or a full re-write that is needed....