Skip to content

CAP-CMT-MTG-008Approve minutes and preserve later corrections

Markdown

CAP-CMT-MTG-008

Approve minutes and preserve later corrections

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationInconsistent

KindCapabilityProduct areaCommitteesModuleMeetings, Decisions and RecruitmentRevision1

Read atservices-committees 36129c24react-console baf6dae3

The Formal Contract

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

Outcomes
Approval protects the circulated text and fingerprintCorrections retain a link to the earlier approved revisionThe committee’s rules select voting or direct approval
Surfaces
api
Preconditions
Approval requires circulated minutes; starting a correction requires the current approved revision.
Postconditions
Approval retains the circulated body fingerprint.
Intent sources
services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#D7services-committees:docs/milestones/CMTE-M7-governance-oversight.md#D1

Controls

30 controls apply, from the corpus control catalogue.

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

Permissions

KeyChecked atScope
committees.minutes.manageapitenant

Business Rules

10 rules, 9 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
Approval requires circulated minutes and refuses records already approved or amended.
no proof recorded yet
lifecycleserviceobserved
02must prove
Proposed
When committee rules require an approval vote, an approval decision uses their selected method; otherwise the permission-bearing caller approves directly and is recorded as the approving actor without a chair-role check.
no proof recorded yet
policyserviceobserved
03must prove
Proposed
A meeting-based approval requires an approving meeting, while an asynchronous approval opens with its closing time and takes effect only when its decision closes carried.
no proof recorded yet
validationserviceobserved
04must prove
Proposed
Approval preserves the circulated body and fingerprint, and the database protects approved content while permitting transition to amended and changes to version metadata.
no proof recorded yet
invariantservice, databaseobserved
05must prove
Proposed
Starting a correction creates the next draft revision linked to the approved original, points the meeting to that new draft, and marks the original amended when the correction is approved.
no proof recorded yet
lifecycleservicetest
06must prove
Proposed
The API requires minutes-management permission for approval and creation of a correction.
no proof recorded yet
permissionapitest
services-committees:modules/decisions/tests/e2e/decisions.e2e.spec.ts#refuses minutes approval to a caller without committees.minutes.manage, 403
07must prove
Proposed
Approval records a business event and submits the configured approval notices for the meeting’s participants.
no proof recorded yet
policyservicetest
08must prove
Proposed
The product should limit the meetings milestone to circulated minutes and introduce approval and correction with the decisions milestone.
origin: CMTE-M3 D7 (Andrew 2026-10-21, services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#Decisions)
no proof recorded yet
policydocumented
09
Proposed
The minutes-awaiting-approval definition describes overdue draft or circulated minutes, but remains withheld from registration, publication, resolution and sweeps until the volunteer phase.
origin: CMTE-M7 D1 (Andrew 2026-10-21, services-committees:docs/milestones/CMTE-M7-governance-oversight.md#Decisions)
policyserviceobserved
10must prove
Proposed
Approval and correction require the current minutes version, and tally-based approval without supplied counts defaults to a declaration that the motion carried.
no proof recorded yet
validationapi, serviceobserved

Scenarios

IdGivenWhenThenProvenance
01The board’s November minutes have circulated and December’s meeting has recorded quorumStaff record a carried voice approval at December’s meetingThe November minutes become approved with their circulated fingerprint and an approving decision referenceobserved

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.