Update README.md

Author: shrutibist

README.md

@@ -60,6 +60,7 @@ Our mission
 * [Group Support](patterns/2-structured/group-support.md) - *What happens if a team or individual no longer supports an InnerSource project? Keep the project alive by forming a group of interested individuals.*
 * [Explicit Governance Levels](patterns/2-structured/governance-levels.md) - *Different teams within an organization use InnerSource practices in varying ways, leading to confusion and inefficiencies due to inconsistent expectations of collaboration and contribution rights. Establish centrally documented governance levels that define the extent of influence contributing teams can have on a project, improving clarity for contributors and host teams alike.*
 * [InnerSource Hackathon](patterns/2-structured/innersource-hackathon.md) - *Only InnerSource enthusiasts practice InnerSource during the early stages of adoption, while most engineering teams lack the time or motivation to try it. Hosting a company-wide hackathon focused on InnerSource contributions provides a safe space for engineers to experiment with InnerSource practices and produces tangible contributions to InnerSource projects.*
+* [Sponsor Communication and Engagement](patterns/2-structured/sponsor-communication-and-engagement.md) - *InnerSource programs typically depend on a small number of senior sponsors for funding, organizational air cover, and top-down advocacy, but sponsors who only hear about the program sporadically, only receive one-way status updates, or are recruited purely for seniority rather than genuine engagement, tend to disengage, and their support quietly erodes over time. Hold recurring, time-boxed readouts that are forward-looking rather than retrospective, and split into a presentation segment and a protected discussion segment, so sponsors stay genuinely informed, have a real voice in shaping the program's direction, and know exactly how they can help.*
 
 ### Maturity Level 1: Initial