--- id: ACTORS-CMT title: People and Services in Committee Work product_area: committees revision: 2 status: draft product_intent: proposed source_sha: services-committees: 36129c24daeaadcdb339218c38cdeaff9861359d react-console: baf6dae382d6f41dce976c7f848667ccc37e076f actors: - id: ACT-CMT-001 name: Governance Staff who: >- A colleague responsible for operating boards and committees through the staff console. goals: - 'Maintain dated participation by body, office and capacity.' - Prepare places and subsequent slates. can_broadly: - 'Maintain bodies, calendars and relationships and record their closure.' - Manage the structure of committee places. - Record and change participation individually or through larger jobs. - 'Inspect dated rosters, change accounts and contact involvement.' represented_by: - committees.application.access - committees.committees.manage - committees.appointments.manage - committees.seats.manage - committees.committees.read - committees.appointments.read - committees.configuration.read - Association-wide Committees Standard User role surfaces: - console - api - id: ACT-CMT-002 name: Governance Administrator who: >- A colleague who maintains reusable committee policy, application choices and proposed authority mappings. goals: - Supply useful shared governance profiles. - Align configuration with the customer’s bylaws. can_broadly: - Perform the governance staff work. - 'Maintain classifications, offices and application settings.' - Configure proposed authority mappings and request drift repair. represented_by: - committees.configuration.manage - committees.configuration.read - committees.committee-layouts.read - committees.committee-layouts.create - committees.committee-layouts.update - committees.committee-layouts.delete - Association-wide Committees Administrator role surfaces: - console - api - id: ACT-CMT-003 name: Governance Reader who: >- A colleague who investigates governance information without changing the records. goals: - Understand present and historical committee participation. can_broadly: - 'Inspect association-wide bodies, places, service and change accounts.' - Use the standard governance reports. represented_by: - committees.application.access - committees.committees.read - committees.appointments.read - committees.configuration.read - committees.authority.read - Committees Read-Only role surfaces: - console - api - id: ACT-CMT-004 name: Responsible Appointment Staff who: >- A colleague assigned appointment responsibility over the association or a particular body or unit, with administrators as the fallback audience. goals: - >- Find expiring terms, gaps, unanswered offers and limited service without a separate search. can_broadly: - Receive relevant Home and Attention items and follow them to the body. represented_by: - >- Committee appointment responsibility in Platform, without a permission grant surfaces: - console - id: ACT-CMT-005 name: Committee Participant who: >- A CRM person with committee service or a pending invitation whose response staff can record. goals: - Understand their participation and respond to an invitation. can_broadly: - >- The built authenticated portal routes expose own participation and allowed rosters and accept own offer responses; their product release remains deferred. represented_by: - committees.self.read - committees.rosters.read surfaces: - portal - id: ACT-CMT-006 name: Scheduled Service Worker who: >- Rhythm background processing that maintains governance records and conditions without an interactive request. goals: - Reflect calendar consequences once even when work repeats. can_broadly: - 'Complete terms, lapse offers and retire dated places.' - Process larger appointment changes and authority re-derivation. - Refresh staff attention and compare derived authority with Platform. represented_by: - Rhythm system attribution in governance history surfaces: - job - id: ACT-CMT-007 name: Integrating Application who: >- A Rhythm application or Platform component that exchanges governance facts through service contracts. goals: - 'Keep service aligned with membership, identity and security records.' can_broadly: - Consume the documented membership termination contract. - Transfer participation during CRM contact merging. - Validate grant authority and synchronize Platform assignments. - Load source governance information through data operations. represented_by: - membership.term.terminated event - CRM merge participant functions - platform.sync_derived_assignments - Management permissions for the imported resource surfaces: - api - job - id: ACT-CMT-008 name: Governance Record Reader who: >- A staff reader with access to committee records and no corresponding management authority. goals: - Locate governance records and understand their current standing can_broadly: - 'Inspect meeting records, minutes and the decision register' - 'Review openings, forecasts and nominations within granted read access' represented_by: - committees.meetings.read - committees.decisions.read - committees.openings.read - committees.nominations.read surfaces: - api - console - id: ACT-CMT-009 name: Meeting Chair or Liaison who: >- A person recorded as the chair or liaison for a meeting, with additional staff actions available only under staff permissions. goals: - Help participants respond and maintain the meeting’s attendance can_broadly: - >- Answer another participant’s invitation and record attendance through meeting-role authority - >- Request quorum evaluation and manage decisions through the relevant authorised staff operations - >- Use minutes approval where the governing rules and staff authority permit represented_by: - >- committees.portal.participate (with a chair or liaison role at the meeting) - committees.meetings.manage - committees.minutes.manage - committees.decisions.manage surfaces: - portal - api - id: ACT-CMT-010 name: Website Visitor who: >- An anonymous or signed-in visitor requesting publicly available committee information. goals: - Find public gatherings and advertised vacancies can_broadly: - Read public meeting information - Read openings made available through public directory settings represented_by: - no permission required for public operations surfaces: - portal - id: ACT-CMT-011 name: Committee Background Worker who: >- A scheduled or event-driven service process that performs committee work without an interactive caller. goals: - Process due governance work - Keep event-driven changes and acknowledgements moving can_broadly: - Generate recurring meetings and process due notices - Close eligible recorded asynchronous decisions - Create disclosure obligations - Handle appointment-start events that count towards filling openings represented_by: - scheduled committee work and event-consumer identities surfaces: - job - id: ACT-CMT-012 name: Governance Result Provider who: >- A connected service that supplies a review decision or certified election outcome to Committees. goals: - Deliver a result for application without duplicate effects can_broadly: - Submit review decisions or certified election events - >- Receive processing acknowledgements where the integration contract provides them represented_by: - Submissions decision intake - certified-election event intake surfaces: - job evidence: - >- services-committees:aws/committees.service.ts; docs/milestones/CMTE-M1-committees-seats-and-rosters.md#D11; docs/milestones/plans/CMTE-M7-plan.md#D6; modules/appointments/services/membership-events; lib/record-merge/committees-references.ts; modules/committees/services/persistence/change-histories.ts - >- react-console:acceptance/committees/inventory/permissions.json; docs/committees/CMTE-M1-console.md --- # People and Services in Committee Work Governance staff operate bodies and record participation, administrators maintain shared choices, and readers investigate service. Responsibility assignments direct staff attention without replacing permissions. Participants are the people described by the records, with staff recording their responses in the accepted console scope. Background workers and integrating applications maintain dated consequences and connected records; the existing portal and authority engines still require their release decisions.