Rhythm 2.0 Specifications

Appearance

SVC-CMT-MTG-meetingsMeeting and Minutes Service

Markdown

SVC-CMT-MTG-meetings

Meeting and Minutes Service

Markdown
  • DocumentDraft
  • ImplementationInconsistent

KindService contractProduct areaCommitteesModuleMeetings, Decisions and RecruitmentRevision1

Read atservices-committees 36129c24react-console baf6dae3

Meeting and Minutes Service ​

What This Service Is For ​

This service holds a committee’s scheduled gatherings and written accounts: recurring timetables, attendance, agendas, papers, notes, minutes and suggested follow-ups. It exposes staff administration, member participation and calendar operations, plus a filtered public meeting read. It performs no inference.

Boundary ​

Meeting and minutes concepts have one logical owner here. The committee module supplies roster and settings facts, while decision code implements quorum and approval behind three meeting-addressed routes. The event dispatcher and asset cleanup hosted in this stack also serve the shared macroservice boundary.

Operations in Words ​

Staff schedule and close gatherings, maintain attendance, release agendas and packets and take drafts through circulation. Minutes approval follows the decision rule, and correction creates a new revision. Accepted follow-ups stop at a meeting record and task placeholder. Member operations answer invitations and expose authorized projections or calendar feeds; they do not establish built member screens.

Events and Jobs ​

Meeting lifecycle changes, circulated minutes and approvals record durable business events. Daily and hourly meeting jobs materialize series and attempt reminders and room work. Shared queue handlers dispatch business events and retire assets. Video attendance code exists without its production delivery entry point.

Consistency Guarantees ​

Explicit writes use record locks and supplied versions. Database changes and durable delivery work commit together, while actual delivery and file preparation have separate failure boundaries. Product’s selected e-mail and endpoint suppression switches are still missing; database grant and trigger protections have not been independently certified.

Owns
DOM-CMT-MTG-001DOM-CMT-MTG-002
Repository
services-committees

Controls

49 controls apply, from the corpus control catalogue.

TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-SEC-001 TC-SEC-002 TC-SEC-003 TC-SEC-004 TC-CRY-001 TC-CRY-002 TC-CRY-003 TC-CRY-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 TC-DAT-007 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-AVL-002 TC-AVL-003 TC-AVL-004 TC-AVL-005 TC-MON-001 TC-MON-002 TC-MON-003 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-VEN-001 TC-VEN-002 TC-VEN-003 TC-PRV-001 TC-PRV-002

Does Not Own

  • The committee module owns the committee, configuration, seats, appointments and roster facts that meeting work reads.
  • The decisions service owns motions and implements the quorum, approval and correction code called by meeting routes.
  • CRM owns people and e-mail addresses and the future shared tasks for accepted follow-ups.
  • Platform owns delivery, managed file storage and video integration; this service records their business inputs.
  • Platform owns attention delivery; the minutes condition is declared here but withheld.
  • Queries owns dataset execution and exports, and the Data Job Engine executes declared bulk operations.

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software