Shared Lexicon for a Common Base

What are the guidelines we are reviewing by? What is the process lexicon should go through? These are the sort of things that should be written down first so new comers can easily see and reviewers have a reference to be consistent in evaluation.

One thing that I would like is the proposal to be a markdown doc committed to the repo, rather than a description field in issue/pr

this will make it easy for people proposing to find examples, and keep them from getting lost to time

Yeah we should decide on what a proposal looks like. Some combination of open questions, use cases, example, and other pieces that would be helpful to understand the purpose

... providing references prior art / how are other people representing this model on/off atproto