CAP-CMT-MTG-013Find any decision in the register and report on governance records

CAP-CMT-MTG-013

Find any decision in the register and report on governance records

Markdown

DocumentDraft
Product intentProposed
ImplementationPartially observed

Planning

Feature: FEAT-CMT-MTG-03
Key concepts: CON-CMT-MTG-003
Actors: ACT-CMT-002, ACT-CMT-008
Journeys: JNY-CMT-MTG-003
Depends on: CAP-CMT-MTG-010
Related: CAP-CMT-MTG-015
Proved by: ATS-CMT-MTG-013
Exercised by: JNY-CMT-MTG-002

KindCapabilityProduct areaCommitteesModuleMeetings, Decisions and RecruitmentRevision1

Read atservices-committees 36129c24react-console baf6dae3

Find any decision in the register and report on governance records

Purpose

Staff find any decision of any committee and report on meetings, decisions and recruitment in Queries.

How It Works

The register lists every decision, for one committee or across the whole association, newest first, and can be narrowed by kind, outcome, status, meeting, the dates it opened and words in its title or text. Reading a decision shows its frozen voters, every vote and every recusal. A confidential executive-session decision, with its recusals, is visible only to those who manage decisions; to anyone else it does not exist. Another association never sees any of it. Staff also report on meetings, attendance, minutes, action items, decisions, votes, openings, nominations and disclosures in Queries, each dataset behind its own read permission and the disclosures behind the sensitive one. Access is association-wide today: whoever manages decisions does so for every committee. Every change is kept as a version, though nothing shows that history yet.

Relationships

Relates to CAP-CMT-MTG-010 because the register lists the decisions recorded there.
Relates to CAP-CMT-MTG-015 because the recusals shown with a decision.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

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

Outcomes: Every decision findable by its words, kind, outcome or dateConfidential decisions seen only by those who manage decisionsReports that agree with the records
Surfaces: api
Intent sources: services-committees:docs/milestones/CMTE-M1-committees-seats-and-rosters.md#D11

Controls

20 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-PRV-001 TC-PRV-002

Permissions

Key	Checked at	Scope
`committees.decisions.read`	api	tenant
`committees.decisions.manage`	api	tenant

Business Rules

8 rules, 6 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.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	The register lists decisions newest first, for one committee or the whole workspace, filtered by kind, outcome, status, meeting, the dates opened and words, a page at a time; an unknown filter value is refused. no proof recorded yet	validation	api, service	test services-committees:modules/decisions/tests/e2e/decisions.e2e.spec.ts#refuses an unknown outcome filter with 400
`02`must prove Proposed	A confidential decision and its recusals are visible in the console only to those who manage decisions; to anyone else they do not exist. no proof recorded yet	permission	api, service	test services-committees:modules/decisions/tests/integration/api/confidential-reads.integration.spec.ts#answers the bookkeeper 404 for the confidential decision
`03`must prove Proposed	Reading the register needs the decisions read permission. no proof recorded yet	permission	api	test services-committees:modules/decisions/tests/e2e/decisions.e2e.spec.ts#refuses the register to a caller with no decisions key, 403
`04` Proposed	A decision reads with its frozen voters, its votes and its recusals.	policy	api, service	test services-committees:modules/decisions/tests/e2e/decisions.e2e.spec.ts#reads the auditor’s decision with its ten voters, nine votes and one recusal
`05`must prove Proposed	Decisions of one association are never visible to another. no proof recorded yet	permission	database	test services-committees:modules/decisions/tests/integration/services/decisions.integration.spec.ts#does not read it from another tenant
`06`must prove Proposed	Meetings, attendance, minutes, action items, decisions, votes, openings, nominations and disclosures are reportable in Queries, each under its own read permission and disclosures under the sensitive one. no proof recorded yet	permission	api	observed services-committees:aws/committees.metadata.ts
`07`must prove Proposed	Decision authority is association-wide: whoever manages decisions acts on every committee’s decisions, and a committee-scoped grant does not reach them. origin: CMTE-M1 D11 (Andrew 2026-10-19 18:05 ET, services-committees:docs/milestones/CMTE-M1-committees-seats-and-rosters.md#Decisions) no proof recorded yet	permission	api	documented services-committees:docs/milestones/CMTE-M1-committees-seats-and-rosters.md#Decisions
`08` Proposed	Every change of a decision is kept as a version with who made it, though no route shows that history yet.	invariant	database	observed services-committees:modules/decisions/db/decisions.table.ts

Scenarios

Id	Given	When	Then	Provenance
`01`	Four decisions of the September meeting, one confidential	The chair and a member with the read key open the register	The chair sees four; the member sees three	test services-committees:modules/decisions/tests/e2e/decisions.e2e.spec.ts#shows the chair the register of four decisions, the confidential one among them

Planning

Find any decision in the register and report on governance records ​

Purpose ​

How It Works ​

Relationships ​

Controls

Permissions

Business Rules

Scenarios

Find any decision in the register and report on governance records

Purpose

How It Works

Relationships