I don't think this will work...
This is my own personal opinion, not Word of Mod.
...but it's by no means a bad idea
The fundamental issue with this idea is, as identified by xnor:
This strikes me much like the classic "we're going to rewrite all our code from scratch and get it perfect this time" that tempts developers everywhere. It seems like a massive undertaking with high upkeep costs, on a site long past its prime with dwindling activity.
Source
Even ignoring the part about activity, this very much feels like literally a "mandate from heaven" i.e. something too ideal to be practical/true. As the resident CGCC historian and long-suffering content moderator (both before and since my diamond), I can confidently tell you that CGCC's rules are intricate, complicated, contradictory and nigh-impossible to understand in their entirety. The problem with this idea isn't that the rules will contantly be evolving, as yes, in theory, we can constantly update such a document with each new rule change. The problem is that this document would be so dense as to not even be writable in the first place, let alone readable to the veteran user. New users would be lost at the beginning.
After the canonical faq tag, the policy tag is as close to Word of God as we can get on the site rules. There are 250-odd questions, dating back to 2011. And, not only are a substantial number of these questions outdated, but only specific parts of them are outdated. For instance, for years, we pointed users to Command-line flags on front ends when discussing command-line flags. But also, at the same time, people counted command-line flags as additional bytes per a policy from 2011. And don't even get me started on the Great Debate About "What is a Language?".
In fact, don't even get me started on the fact that literally every language has, in some way or another, unique rules.
In short: such a document, while it would work, would be so impenetrable that it'd fail at its primary job of providing a single source of all rules. At that point, why not just consider Meta itself as said "document" or source? In fact, isn't that what the faq tag is supposed to be?
My suggestion
As I already remarked, we have a community-editable document/guide containing (ideally) all the information a new user should reasonably need to know before posting on the site. The Welcome page is, unlike our unhelpful Tour and help pages, editable by any member of the Community, and so can be updated with any rules changes. It's linked in our Welcome box, is used by multiple users by default when welcoming new users, and contains exactly the information a new user should need to know when posting.
Yes, I wrote the first version. No, it is not my post. It is the Community's post, and, if it's missing information or isn't immediately accessible for new users, then:
Please edit it!
I've suggested posting another answer, one that covers essentially "ok, I've read the answering/asking post, do I need to know anything else?", and such a beginner-rules pamphlet would, in my opinion, be perfect for this. A resource where anyone from the most experienced user to a recently-joined user can find the most useful information is precisely what this faq post is for, and if it's failing to do that, it should be improved to fix that.
Therefore, my suggestion:
- Have a follow-up discussion to this, wherein we formulate what "new user rules info" should be included in such a guide
- Post a new answer to the Welcome page containing this information
- Update the existing answers so they are up-to-date, contain all relevant information while still being accessible
- Update the faq tag so that we can point users to that for rules clarifications
- Potentially, create a new post along the lines of "I have a rules questions I couldn't find an answer to elsewhere. What do I do?" This would contain links to some of our most often-linked policy questions, with snippets clarifying what the settled-on policy was within the faq
- This prevents users having to search through policy to find a single answer, but also prevents it from becoming an impenetrable mess of descriptions/clarifications. A bullet-pointed list of "important policies", followed by a "if you still are unsure, ask on meta" would be ideal