Proposal type: Constitution

On Telegram, we discussed the notion of having a constitution and possibly a proposal type in order for this to be created. How this exactly would be structured is still to be discussed.

I had a question about the council and proposals. Lets say the council operates for several years, and the number of proposals would predictably be in the hundreds. How would we best organize the results of proposals into rules? An example would be that we've established a signal proposal is needed for creating a forum category, if there are several proposals like that, would we need a document to organize/collate them all in one document? Especially if a later proposal overrides an earlier one in some way
I think you just made the case for a new kind of proposal & feature: a constitution + constitutional amendment.
A constitution would be a coherent body text which would be augmented over time using a special amendment proposal. It would both serve to become a canonical document that sumarized the current net intention behind all such amendment proposals, and most importantly, it would practically force the council to have all of those amendments be internally coherent. With text proposals, you could have two contradictory, or at least ambiguous texts pass close in time, and there is no pressure to make sure they are compatible.

Questions:

• Would this proposal type directly add/edit a central document located on the chain? Or would it be up to the community and council to collate the proposals into a document?
• How would it best be formatted, for wide readability/accessibility?
• Would each addition be a separate numbered item that forms the constitution? Or would it be more like a body of text?

No files, tests, or entry points are identified. First clarify whether a constitution is an on-chain document or a community-maintained compilation, then define how amendments, conflicts, numbering, and readable formatting should work before implementation can be scoped.