A contributor does not arrive because a repository exists. They arrive because they can see where they fit. Our most useful shift was to stop treating contribution as a single action. Someone can improve a sentence, reproduce a bug, design an example, answer a question, or build a feature. Each of those actions is a way into the product, and each deserves a clear path. We started writing issues as invitations instead of tickets. We added context, a definition of done, and a sentence explaining why the work mattered. We documented the decisions that felt obvious to us because they were not obvious to anyone joining later. The result was more than a larger contributor graph. It was a better product: more resilient, more legible, and more honest about who it was for. Community is not an audience around the work. It is part of the work.