Committees Responsibilities
How the Product Area Is Divided
The governing-body module keeps committees, their places, dated participation and resulting authority. The adjacent meetings and recruitment module owns the work those bodies conduct. Committee closure coordinates the neighboring module’s changes through its owning functions within the closure transaction.
Committees, Seats, Appointments and Authority
Four service modules share responsibility for this module’s five domain objects. Committees owns bodies, configuration, terms and links; Seats owns persistent places and their reservation rules; Appointments owns recorded participation, computed service, published roster functions and date-driven processing; Authority owns mappings, derived-assignment records and repair. The exposed surface includes their declared HTTP operations and business events, while published roster and contact-merge functions remain separate integrations.
The structured guarantees cite the domain invariants and their actual enforcement boundaries. Ordinary service changes commit with selected access, event and enabled attention consequences, while lapse publication and SQL contact merge follow explicit exceptions. Individual staff writes normally serialize on the body, but scheduled and batch work uses the locks described in its own contracts. Seat conversion also performs direct internal writes, an ownership exception still awaiting architectural review.
Meetings, Decisions and Recruitment
Six concepts define this module: meetings, minutes, decisions, conflict disclosures, openings and nominations. Each has an owning service, while related facets such as participants, papers, votes, interests and review delivery work remain within those concepts. Three source services share a database boundary where one business step changes several of them.
The service contracts expose staff administration, member participation and filtered public reads, plus query datasets and bulk meeting operations. The module owns four Submissions subject kinds and a review receiver, but no inspected route declares an operation binding. Whether that alternative satisfies the publication standard remains a proposed assessment.
The listed guarantees identify the verified service or declared constraint boundaries. Locks, supplied versions, unique occurrence and recipient keys, reopening checks and deterministic decision evaluation protect their respective writes. Carried database consequences commit with the result; actual message delivery remains eventual and can be skipped. Database immutability and deletion grants are declared but unverified, so they are excluded from the guarantee list where the claim depends on that evidence.
No page in the permitted console sources administers these records. Product still needs to choose the staff surface, and portal pages outside that source scope remain unverified. The inspected services and workflows perform no inference.
What Is Delegated to Platform and Other Areas
Platform owns security decisions and grants, shared extensibility, attention, reporting, background execution, delivery, console infrastructure and workspace provisioning. Committees computes desired access and calls Platform’s owning function rather than writing grants directly. CRM supplies people and organization facts and coordinates contact consolidation; Membership supplies units and eligibility, with live termination-event delivery still unproved. The adjacent governance module owns the meeting and recruitment records closed by dissolution.