--- id: AREA-CMT title: Committees product_area: committees revision: 1 status: draft product_intent: proposed implementation_evidence: partially-observed source_sha: rhythm-v2-docs: 57bd42267bc7cb15b38c01033f6175b515e25d36 services-committees: 36129c24daeaadcdb339218c38cdeaff9861359d react-console: baf6dae382d6f41dce976c7f848667ccc37e076f provenance: documented source: rhythm-v2-docs:specs/PRODUCT-AREAS.md#Modules modules: [MOD-CMT-CMT, MOD-CMT-MTG] owns: - Committee structure, places and dated participation. - Governance records for meetings, decisions, conflicts and recruitment. - Committee service information and its proposed authority consequences. does_not_own: - CRM owns people, organizations, affiliations and contact consolidation. - Membership owns organizational units and membership qualification. - Platform owns authentication, authorization, delivery, files, reporting and durable execution. - Submissions owns forms and review decisions. - Websites owns the portal runtime and public website. - Surveys and Voting owns the proposed secret-ballot service; Volunteers owns proposed recruitment opportunities. handoffs: - to: CRM what: Person and organization references, representation checks, contact consolidation and follow-up tasks. - to: Membership what: Unit structure, eligibility and membership termination facts. - to: Platform what: Proposed derived assignments, responsibility audiences, attention items, governance datasets and background work. - to: Submissions what: Disclosure forms and review outcomes with acknowledgements. - to: Websites what: Permission-checked participation and visibility-limited public information for hosted experiences. - to: Surveys and Voting what: Proposed secret-ballot requests and certified election results. - to: Volunteers what: Proposed links between committee openings and recruitment opportunities. invariants: - Governance meaning belongs to the record owner even when another application hosts its presentation. - Committee service records refer to people and organizations owned by CRM rather than creating a second identity register. - Platform remains the authority for access; governance responsibility and committee parentage do not themselves grant it. - A built operation does not establish permission to release deferred governance experiences. evidence: - source: rhythm-v2-docs:specs/PRODUCT-AREAS.md#Modules provenance: documented supports: Area identity and the two module boundaries. - source: rhythm-v2-docs:specs/committees/committees/MODULE.md provenance: documented supports: Structure, participation, oversight and deferred authority ownership. - source: rhythm-v2-docs:specs/committees/meetings/MODULE.md provenance: documented supports: Meeting, decision, recruitment and disclosure ownership and deferred hosted surfaces. - source: rhythm-v2-docs:specs/committees/ACTORS.md provenance: documented supports: Staff, participants, visitors, workers and integrating applications. - source: rhythm-v2-docs:specs/committees/RESPONSIBILITIES.md provenance: documented supports: Record ownership and delegated concerns. - source: rhythm-v2-docs:specs/committees/committees/FINDINGS.md#OQ-CMT-CMT-001; specs/committees/meetings/FINDINGS.md#OQ-CMT-MTG-001; OQ-CMT-MTG-002; OQ-CMT-MTG-009 provenance: unknown supports: Authority release, staff hosting, portal exposure and notice audience decisions remain open. --- # Committees ## Purpose and Outcomes Committees gives an association a shared account of its governing bodies and the people who serve on them. Governance staff use that account to keep organizational structure, dated service and committee work connected. Readers can understand how a body is organized and how participation changes over time without maintaining a separate list of people. Administrators align shared governance choices with the association’s own practices. The area also brings the records of collective work into that account. Meetings, formal decisions, conflicts and recruitment belong beside the bodies and participation they concern. This creates a basis for following governance work across changes in office, committee composition and staff responsibility. The desired outcome is an understandable record of who serves, what work belongs to the body and which neighboring application supplies the next part of the process. Delivery is uneven across this scope. Staff already use the committee structure and service experience in the console. Meetings, decisions and recruitment have service implementations, while their hosted experiences and several portal uses await product decisions. Appointment-derived authority is likewise an implemented extension awaiting its release decision. These boundaries keep the overview useful without treating every implemented operation as an accepted customer experience. ## Scope and Boundaries The area owns governance records and their meaning: committee structure and service in one module, and collective work and recruitment in the other. It hands record consequences between those modules while retaining each owner’s responsibility. CRM supplies people, organizations and affiliations and coordinates contact consolidation. Membership supplies organizational units and qualification facts. Platform supplies security, shared presentation, files, communication delivery, reporting, staff attention and durable execution. Submissions supplies forms and review outcomes. Websites hosts the portal and public website; Committees supplies the governance information those experiences consume. Secret ballots depend on Surveys and Voting, and recruitment opportunities depend on Volunteers. The module charters describe these as proposed connections rather than completed services. A reference to an outside record does not transfer ownership of that record into Committees. ## How the Area Is Divided **Committee Structure, Service and Proposed Authority** is the starting point for understanding governing bodies, the places within them and dated participation. Open it when the question concerns governance structure, service history, staff oversight or the proposed connection between office holding and access. Its charter identifies the neighboring systems that supply identity, eligibility and shared infrastructure. **Meetings, Decisions and Recruitment** covers the collective work attached to those bodies and the process of finding future participants. Open it when the question concerns meeting records, governance outcomes, conflicts or recruitment ownership. Its charter also explains the deferred surface decisions and the integration boundaries that make a service implementation different from a released experience. ## Area-Level Invariants The area keeps governance ownership with the module responsible for the record, including when a screen appears in another application. It uses CRM’s people and organizations as identity references. Platform remains responsible for authorization; committee parentage and staff responsibility routing do not establish access by themselves. Implementation evidence and release approval remain separate throughout the area. ## Open Ownership Questions Product still decides where staff administer meetings, decisions and recruitment, and which public and portal operations remain reachable before the portal stage. The release boundary for appointment-derived authority also remains open. Recruitment notices need an audience decision that distinguishes committee office holders from staff with assigned responsibility. The owning modules retain these questions and their options.