Update index.md

Updated governance docs to reflect current Assembly model.

docs/initiative/index.md

@@ -36,7 +36,7 @@ The Open Referral Initiative is guided by a set of **values** (_the good things
 
 _The Open Referral community is open to all who wish to work towards a future of open, interoperable, reliable, and sustainable community resource directory data — and who abide by the following principles:_
 
-**Open source.** **_Open Referral works in the open._** We promote open data, we develop open source technology, and we share knowledge about all of the above. We specify open source licenses (such as [Creative Commons By-Attribution Share-Alike](https://creativecommons.org/licenses/by-sa/4.0/)) for code, content, and collateral produced through our projects. We also strive to be open in our processes — including contracting and fundraising — to whatever degree is possible. Business intelligence specific to our contracted partners may remain private or clearly attributed. That said, we publicly document our decision-making processes and outputs to whatever degree is appropriate. [[Here is a memo with more analysis of open source licensing issues.](https://docs.google.com/document/d/1W81WtFVgnIIz_ko8PVtvoQrnb-_AbwlKTDPGvPo6dIk/edit#)] 
+**Open source.** **_Open Referral works in the open._** We promote open data, we develop open source technology, and we share knowledge about all of the above. We specify open source licenses (such as [Creative Commons By-Attribution Share-Alike](https://creativecommons.org/licenses/by-sa/4.0/)) for code, content, and collateral produced through our projects. We also strive to be open in our processes — including contracting and fundraising — to whatever degree is possible. Business intelligence specific to our contracted partners may remain private or clearly attributed. That said, we publicly document our decision-making processes and outputs to whatever degree is appropriate.
 
 **Users’ prerogatives.** **_Open Referral prioritizes the interests of people in need, and the people who serve them._** We focus on the interests of people in need — and the people who help them — as the primary lens through which we design sustainable business models. Throughout our pilot projects, we engage with such stakeholders to ensure that their priorities and realities are taken into account. Here is our summary of our primary user types and their respective needs: [Personas and User Stories](#types-of-use-and-user-personas).
 
@@ -185,41 +185,39 @@ _As a researcher, I want to…_
 
 ## Governance and Participation
 
-Open Referral operates across multiple overlapping layers of decision-making contexts, from **_global_** (as an open community of practice, developing open-access tools) to **_local_** (as a set of place-based pilot projects led by stakeholders in a given geographical region) and **_sectoral_** (with projects in specific subdomains like legal aid, etc). It operates _iteratively_, with regular opportunities to change and grow. 
+Open Referral is an open community of practice – anyone who shares our vision and values is welcome. Our network (which includes human service referral providers, government officials, academics, vendors, community leaders, etc) is primarily assembled in our [Community Forum](https://forum.openreferral.org). We also have a [Slack team](https://openreferral.org/get-involved/join-our-slack-team/), and discuss technical issues in [Github](https://github.com/openreferral).
 
-To promote these qualities, and hold ourselves accountable to them, we aim to build **_core coordination capacity_** that can support both the initiative as a whole as well as **_pilot projects_** with their own leadership structures. We also convene **_assemblies_** and **_workshops_** in which participants across our network come together to share learnings and set agendas for future development.
+Though we are an international initiative, our subject is primarily local and therefore much of the work in our initiative is done locally. This means our decision-making processes are distributed – from **_global_** (as an open community of practice, developing a common standard, collateral materials, open source tools, etc) to **_local_** (as a set of place-based pilot projects led by stakeholders in a given geographical region) and **_sectoral_** (with projects in specific subdomains like legal aid, etc). We operate _iteratively_, with regular opportunities to reflect, change, and grow. 
 
-**Stakeholders** include any intended beneficiary of Open Referral’s work, as described by our [User Personas documentation](#types-of-use-and-user-personas). (These broad types of beneficiary user groups consist of: help-seekers, help providers, data administrators, and data analysts.) 
+**Core team** facilitates alignment and supports activities across the Open Referral network. 
 
-Practically, most stakeholder groups are represented in Open Referral by the organizations that serve them (service/referral providers, technology vendors). 
+At a 'global' level, Open Referral consists of technical and institutional leadership. Core team members a) set the agenda for public discussions; b) oversee accountable administration of any grant funding or other resources in the Open Referral Initiative’s control; and c) make decisions in any instances in which the community cannot reach rough consensus.
 
-**Lead stakeholders** are voluntary representatives of specific stakeholder groups who commit to the design, implementation, and/or evaluation of Open Referral’s protocols and products through resource data exchanges and associated projects – typically in the context of pilot projects. 
+**Workgroups** of designated leads who advise on design, implementation and governance.
 
-Lead stakeholders’ input is prioritized through all phases of Open Referral’s activities; in instances when Open Referral needs more insight to make a decision, we engage with lead stakeholders to solicit relevant feedback from their stakeholder communities.
+Workgroups may be formed by any set of members to operate in accordance with the Initiative’s values and principles, and are empowered to make proposals subject to [rough consensus](https://en.wikipedia.org/wiki/Rough_consensus) of the Initiative’s community. Workgroups can consist of at least two community members who agree to collaborate on a stated objective such as the development of Open Referral’s data specifications, implementation guidance, tooling, the governance model for Open Referral itself, etc. Workgroups should include at least one **Subject Matter Expert** to represent users’ needs, and at least one **Lead Facilitator** to be accountable for coordinating activities including setting agendas and taking detailed notes – all of which is expected to be reported on in our regular Assemblies and/or shared in [Open Referral’s community forum](https://forum.openreferral.org/) with appropriate notice. Additional Workgroup members can be nominated by the community (including self-nominations by community members) and/or invited by core team members. 
 
-**Global community of practice**: practitioners, experts, vendors, community leaders, etc. 
+Workgroups should demonstrate that aspects of any proposal put forth are directly informed by perspectives and interests expressed by representatives of Open Referral’s [primary beneficiary groups](#types-of-use-and-user-personas) – and are expected to field and respond accordingly to any such feedback received externally. In instances where rough consensus cannot be attained, even after parties have put forth and evaluated alternative proposals and feedback from lead stakeholders of pilot projects has been solicited, Core Team leads reserve the right to make decisions (and will appropriately document the rationale for decisions and ensure the result of those decisions are subject to subsequent evaluation and possible revision). 
 
-Open to all participants who share our vision and values, our network is primarily assembled in our [Google group](https://groups.google.com/g/openreferral/), [Slack team](https://openreferral.org/get-involved/join-our-slack-team/), [Github repo](https://github.com/openreferral), and other channels (blog, email list, etc).
+**Assemblies and Workshops** – gatherings open to all members of the community are held on a quasi-regular basis to facilitate alignment around the mission of the Initiative.
 
-**Core team** facilitating alignment and supporting activities across the Open Referral network. 
+Leadership and technical implementers regularly convene at Assemblies (a brief open meeting, held roughly monthly). The Assemblies are open; you can [join the Forum](https://forum.openreferral.org/) and request to be added to the calendar. 
 
-At a 'global' level, Open Referral consists of technical and institutional leadership roles. Core team members a) set the agenda for public discussions; b) oversee accountable administration of any grant funding or other resources in the Open Referral Initiative’s control; and c) make decisions in any instances in which the community cannot reach rough consensus.
+We also host quasi-annual Workshops (longer open meetings) in which we share, learn, deliberate, and generate proposals. Workshops and Assemblies are not decision-making events, but are critical opportunities for sharing knowledge, building relationships, and setting the agenda for future development. These events can generate and prioritize “user stories,” feature backlogs, and possible courses of action to meet the needs expressed by those user stories. ([See this report back from the inaugural workshop.](https://docs.google.com/document/d/1kivG6TTw1LKhJRAQHeqH7fTIxZZaDojXRRBYEd_ltWw/edit#))
 
 **Local pilots** implementing data exchanges, evaluating specs, planning for the future.
 
 Open Referral focuses much of our work in local pilot projects. In pilots, project stakeholders collaborate to promote access to up-to-date resource directory data in their communities, by using Open Referral’s data exchange specifications to share resource directory data among existing and/or emerging systems. In return, stakeholders can receive facilitation, technical solutions and support, and other kinds of capacity-building when possible, helpful, and appropriate. Feedback from such stakeholders shapes the ongoing evolution of Open Referral.
 
-Pilot projects’ objectives include short-term demonstrations of the value of open and interoperable resource directory systems, and strategic plans for long-term sustainability of such systems. Local pilot projects should consist of **_teams_**, anchored around **_lead_ _stakeholders_** (as above) who will be represented by some **_leadership structure_** (a ‘table’ or ‘committee,’ etc) – and ideally supported by some core-coordinating capacity of their own (sometimes called [a ‘backbone’](https://www.collectiveimpactforum.org/resources/value-backbone-organizations-collective-impact) as in the Collective Impact coalition model). Pilot projects might also be supported by **_partners_**, i.e., organizations that provide material support, technical assistance and/or other in-kind resources – such as philanthropic funders, contracting agencies, civic technology networks, software vendors, etc., who can help with implementation, if not decision-making. 
+Pilot projects’ objectives include short-term demonstrations of the value of open and interoperable resource directory systems, and strategic plans for long-term sustainability of such systems. Local pilot projects should consist of **_teams_**, anchored around **_lead_ _stakeholders_** (see below) who will be represented by some **_leadership structure_** (a ‘table’ or ‘committee,’ etc) – and ideally supported by some core-coordinating capacity of their own (sometimes called [a ‘backbone’](https://www.collectiveimpactforum.org/resources/value-backbone-organizations-collective-impact) as in the Collective Impact coalition model). Pilot projects might also be supported by **_partners_**, i.e., organizations that provide material support, technical assistance and/or other in-kind resources – such as philanthropic funders, contracting agencies, civic technology networks, software vendors, etc., who can help with implementation, if not decision-making. 
 
-**Workgroups** of designated leads who advise on design, implementation and governance.
-
-Workgroups may be formed by any set of members to operate in accordance with the Initiative’s values and principles, and are empowered to make proposals subject to [rough consensus](https://en.wikipedia.org/wiki/Rough_consensus) of the Initiative’s community. Workgroups can consist of at least two community members who agree to collaborate on a stated objective such as the development of Open Referral’s data specifications, implementation guidance, tooling, the governance model for Open Referral itself, etc. Workgroups should include at least one **Subject Matter Expert** to represent users’ needs, and at least one **Lead Facilitator** to be accountable for coordinating activities including setting agendas and taking detailed notes – all of which is to be shared in Open Referral’s public forum with appropriate notice. Additional Workgroup members can be nominated by the community (including self-nominations by community members) and/or invited by core team members. 
+**Stakeholders** include any intended beneficiary of Open Referral’s work, as described by our [User Personas documentation](#types-of-use-and-user-personas). (These broad types of beneficiary user groups consist of: help-seekers, help providers, data administrators, and data analysts.) 
 
-Workgroups should demonstrate that aspects of any proposal put forth are directly informed by perspectives and interests expressed by representatives of Open Referral’s [primary beneficiary groups](#types-of-use-and-user-personas) – and are expected to field and respond accordingly to any such feedback received externally. In instances where rough consensus cannot be attained, even after parties have put forth and evaluated alternative proposals and feedback from lead stakeholders of pilot projects has been solicited, Core Team leads reserve the right to make decisions (and will appropriately document the rationale for decisions and ensure the result of those decisions are subject to subsequent evaluation and possible revision). 
+Practically, most stakeholder groups are represented in Open Referral by the organizations that serve them (service/referral providers, technology vendors). 
 
-**Assemblies and Workshops** – gatherings open to all members of the community are held on an as-needed basis to facilitate alignment around the mission of the Initiative.
+**Lead stakeholders** are voluntary representatives of specific stakeholder groups who commit to the design, implementation, and/or evaluation of Open Referral’s protocols and products through resource data exchanges and associated projects – typically in the context of pilot projects. 
 
-Global and local leadership convene regularly at Assemblies (a brief open meeting) and Workshops (longer open meetings) to share, learn, deliberate, and generate proposals. Workshops and Assemblies are not decision-making events, but are critical opportunities for sharing knowledge, building relationships, and setting the agenda for future development. These events can generate and prioritize “user stories,” feature backlogs, and possible courses of action to meet the needs expressed by those user stories. ([See this report back from the inaugural workshop.](https://docs.google.com/document/d/1kivG6TTw1LKhJRAQHeqH7fTIxZZaDojXRRBYEd_ltWw/edit#))
+Lead stakeholders’ input is prioritized through all phases of Open Referral’s activities; in instances when Open Referral needs more insight to make a decision, we engage with lead stakeholders to solicit relevant feedback from their stakeholder communities.
 
 
 ## Get Involved