Rhythm 2.0 Specifications

Appearance

CAP-CMT-MTG-004Prepare and share an ordered meeting agenda

Markdown

CAP-CMT-MTG-004

Prepare and share an ordered meeting agenda

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationObserved

Planning

Feature
FEAT-CMT-MTG-02
Key concepts
CON-CMT-MTG-001
Actors
ACT-CMT-002, ACT-CMT-008
Journeys
JNY-CMT-MTG-001
Depends on
CAP-CMT-MTG-001
Related
CAP-CMT-MTG-005, CAP-CMT-MTG-007, CAP-CMT-MTG-010
Proved by
ATS-CMT-MTG-004

KindCapabilityProduct areaCommitteesModuleMeetings, Decisions and RecruitmentRevision1

Read atservices-committees 36129c24react-console baf6dae3

Prepare and share an ordered meeting agenda ​

Purpose ​

An agenda gives the committee a deliberate sequence for its business. The secretary can organise that sequence and retain a connection to business planned for another meeting.

How It Works ​

Staff assemble sections and individual topics before proceedings begin. Titles, descriptions, presenters and optional time allocations help explain each topic. Placement controls let the secretary insert a topic among existing siblings, while whole-agenda replacement can also change its parent. Concurrent additions retain separate positions. Deferring a topic creates a new planned copy rather than moving its notes and materials to the later meeting. The source topic remains a record of the deferral. Deletion checks protect work already recorded against a topic. Publication marks the agenda as shared without making it final. Finalisation follows the meeting lifecycle and prevents further agenda writes. Confidential topics remain subject to meeting-role checks when a portal viewer reads them.

Relationships ​

Scheduling supplies the meeting lifecycle used for finalisation. Packet preparation attaches papers to topics, minutes use agenda order, and decision work can record a motion against a topic.

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes
Meeting business follows an intentional hierarchy and orderDeferred business has a planned copy on a later agendaFinal agendas retain their recorded contents
Surfaces
api
Preconditions
The meeting and agenda remain eligible for editing.
Postconditions
Publication marks the agenda as shared; portal disclosure still follows the viewer’s participation and confidentiality checks.

Controls

22 controls apply, from the corpus control catalogue.

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-SEC-001 TC-SEC-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PI-005 TC-PRV-001 TC-PRV-002

Permissions

KeyChecked atScope
committees.meetings.readapitenant
committees.meetings.manageapitenant

Business Rules

10 rules, 10 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

IdRuleKindEnforced atProvenance
01must prove
Proposed
Agenda items form an ordered hierarchy, with new items appended under a parent or placed before or after a sibling; requesting both placements is refused.
no proof recorded yet
validationservice, databasetest
services-committees:modules/meetings/tests/integration/services/meetings.integration.spec.ts#places an item before another without renumbering the rest’s keys
02must prove
Proposed
Concurrent additions are serialised so each item retains a distinct position and siblings receive consecutive numbers.
no proof recorded yet
invariantservice, databasetest
services-committees:modules/meetings/tests/integration/services/meetings.integration.spec.ts#keeps all ten, each with its own key
03must prove
Proposed
Replacing the agenda order requires the current meeting version, every item exactly once, and each parent before its children.
no proof recorded yet
validationserviceobserved
services-committees:modules/meetings/services/persistence/agenda-items.ts:replaceAgendaOrder
04must prove
Proposed
Deleting an item is refused when it has children, notes, proposed actions, task links or decisions; otherwise its materials are detached and remain on the meeting.
no proof recorded yet
validationservice, databaseobserved
services-committees:modules/meetings/services/persistence/agenda-items.ts:deleteAgendaItem
05must prove
Proposed
Deferral requires the current item version and an editable later meeting of the same committee, marks the original deferred and appends a planned copy, and refuses further edits or deferral of the original.
no proof recorded yet
lifecycleservice, databaseobserved
services-committees:modules/meetings/services/persistence/agenda-items.ts:deferAgendaItem
06must prove
Proposed
An agenda can be published from draft only while its meeting is draft or scheduled.
no proof recorded yet
lifecycleservicetest
services-committees:modules/meetings/tests/unit/services/meeting-lifecycle.spec.ts#publishes a draft agenda of a meeting that has not started
07must prove
Proposed
Calling the meeting to order makes its agenda final, and agenda writes are refused after finalisation or the meeting’s end.
no proof recorded yet
lifecycleservicetest
services-committees:modules/meetings/tests/unit/services/meeting-lifecycle.spec.ts#makes the agenda final at the call to order
08must prove
Proposed
Portal executive-session items are visible only to voting meeting participants, meeting chairs and liaisons.
no proof recorded yet
permissionserviceobserved
services-committees:modules/meetings/services/participation/participation-rule.ts:mayReadConfidential
09must prove
Proposed
An optional item duration, when supplied, must be a whole number from one through 1,440 minutes.
no proof recorded yet
validationapi, databaseobserved
services-committees:modules/meetings/db/agenda-items.table.ts:agenda_items_time_allotted_check
10must prove
Proposed
Agenda item kinds are call to order, consent, report, discussion, motion, election, executive session, information, adjournment or other, and item status is planned, deferred, covered or skipped.
no proof recorded yet
invariantapi, databaseobserved
services-committees:modules/meetings/db/agenda-items.table.ts

Scenarios

IdGivenWhenThenProvenance
01An agenda has a consent section with nested items and a treasurer’s reportThe secretary moves the report to the beginning and promotes a nested item to the top levelThe saved agenda reflects the supplied order and parent assignmentstest
react-console:acceptance/committees/playwright/journeys/meetings/CMT-ACC-0227.spec.ts#CMT-ACC-0227

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