Bringing new work to the Gathering
New work in The Gathering usually starts with a clear problem that needs shared language, repeatable practice, or a stable technical standard. The first goal is not perfection. The first goal is to make the need visible and understandable in public.
Work begins as a draft, improves through review, and moves forward only when the document is clear enough for broader discussion and consensus.
Start with a draft
The usual way to bring new work is to prepare a draft that explains the problem, the intended scope, and the initial direction. A good first draft can be incomplete, but it should be concrete enough for other people to review.
If you are preparing a new proposal, read the Stream-Drafts guidance and use the shared draft template and authoring workflow.
Bring it into public review
New work should be visible in public as early as practical. The right place for that is Stream, where contributors can read the draft, leave comments, and follow the revision history.
Early review is useful because it helps test assumptions, narrow the scope, and identify objections before the work becomes harder to change.
Keep the scope clear
The strongest proposals usually have a narrow, specific purpose. New work should say what it is trying to solve, what it does not try to solve, and what kind of output is expected. That clarity makes review faster and reduces confusion later in the process.
Move forward through the process
Once a draft is active, it follows the normal process: public review, call for consensus, and ratification when the work is ready. Bringing new work to The Gathering does not bypass that path. It is simply how work enters it.
For the full lifecycle, see the process page. If you need help with authoring or access, use tools and services or contact support.