Maintain the record of a governing body

Purpose

Staff establish a recognizable committee record around which service and related work can be organized.

How It Works

Staff start from the committee explorer and choose a name and type. The type supplies initial use of terms and reusable profile values. An optional parent connects this body to the wider committee tree. The record page groups membership, terms, links, history and settings around the same body. Staff review effective settings before supplying exceptions. A save retains omitted information and checks the version that staff read. Status changes express preparation, operation or dormancy. Dissolution uses its own action because it closes related work. Planned custom values remain unavailable, and readers receive the record without change controls.

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: Boards and working bodies remain findable as their people change.Committee parentage preserves separate bodies in a coherent tree.Corrections retain unrelated information.
Surfaces: consoleapi
Intent sources: services-committees:docs/milestones/plans/CMTE-M1-plan.md#2. Scopeservices-committees:docs/milestones/CMTE-M1-committees-seats-and-rosters.md#D1services-committees:docs/milestones/CMTE-M1-committees-seats-and-rosters.md#D6services-committees:docs/milestones/CMTE-M1-committees-seats-and-rosters.md#D12services-committees:docs/milestones/plans/CMTE-M1-plan.md#13. Later product rules applied to this plan (Andrew, 2026-10-19, after approval)services-committees:docs/milestones/plans/CMTE-M1-plan.md#CMTE-M1-S40

Controls

23 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-TEN-004 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

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

Business Rules

14 rules, 11 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	Each committee references a known type and, when supplied, a code unique within the workspace. origin: services-committees:docs/milestones/plans/CMTE-M1-plan.md#CMTE-M1-S25 proved by `ATS-CMT-CMT-003-01`, `TST-CMT-CMT-256`	validation	service, database	test services-committees:modules/committees/tests/integration/services/persistence/committees.integration.spec.ts#refuses a second committee with the same code
`02`must prove Proposed	A committee parent must exist and cannot be the committee itself or any descendant. origin: services-committees:docs/milestones/plans/CMTE-M1-plan.md#CMTE-M1-S27 proved by `ATS-CMT-CMT-003-02`, `TST-CMT-CMT-112`, `TST-CMT-CMT-256`	invariant	database	test services-committees:modules/committees/tests/integration/services/persistence/committees.integration.spec.ts#refuses a parent that would make a cycle
`03` Proposed	Committee parentage supports navigation without passing membership, counts or access to the parent.	policy		documented services-committees:docs/milestones/plans/CMTE-M2-plan.md#4. Assumptions (A4)
`04`must prove Proposed	Committee edits change supplied fields and preserve omitted parentage, unit, status, portal choices and other information. ✓ Correcting Finance’s name leaves its board parent and unit attached.✗ A descriptive correction cannot silently remove the existing parent. origin: services-committees:docs/milestones/CMTE-M1-committees-seats-and-rosters.md#D1 proved by `ATS-CMT-CMT-003-03`, `TST-CMT-CMT-100`, `TST-CMT-CMT-243`, `TST-CMT-CMT-251`	policy	api, service, console	test services-committees:modules/committees/tests/integration/services/cmte-m1-rules.integration.spec.ts#keeps every other field the edit did not carry
`05`must prove Proposed	A committee update using an obsolete version is rejected without replacing the newer record. origin: services-committees:docs/milestones/plans/CMTE-M1-plan.md#CMTE-M1-S33 proved by `ATS-CMT-CMT-003-03`, `TST-CMT-CMT-100`, `TST-CMT-CMT-243`, `TST-CMT-CMT-251`	invariant	service	test services-committees:modules/committees/tests/e2e/cmte-m1-rules.e2e.spec.ts#refuses a PUT made against a stale version with 409
`06`must prove Proposed	Committee creation copies its type's use of terms unless staff explicitly choose a different value. proved by `ATS-CMT-CMT-001-13`, `ATS-CMT-CMT-003-04`, `TST-CMT-CMT-252`, `TST-CMT-CMT-255`	calculation	service, console	test services-committees:modules/committees/tests/integration/services/persistence/committee-member-count.integration.spec.ts#takes the type’s value when the create names none
`07`must prove Proposed	Omitted committee settings survive edits, and the effective profile identifies inherited sources while use of terms and portal visibility remain committee choices. proved by `ATS-CMT-CMT-003-04`, `TST-CMT-CMT-252`, `TST-CMT-CMT-255`	calculation	service, console	observed services-committees:modules/committees/services/profile/effective-profile.ts:committeeEffectiveProfile; services-committees:modules/committees/services/persistence/committees.ts:carriedColumnsOf
`08`must prove Proposed	Staff create and edit actions cannot enter dissolved status, and a dissolved committee cannot return to another status through editing. origin: services-committees:docs/milestones/plans/CMTE-M1-plan.md#D12. Approve the remaining build-time rules as a group? (item 7) proved by `ATS-CMT-CMT-003-05`, `ATS-CMT-CMT-003-10`, `TST-CMT-CMT-263`, `TST-CMT-CMT-279`	lifecycle	service	test services-committees:tests/integration/api/committee-status.integration.spec.ts#refuses a replace moving the dissolved committee back to active, 409 committee_dissolved
`09` Proposed	Staff may edit a committee from any of proposed, active and inactive to either of the others. proved by `ATS-CMT-CMT-003-10`	lifecycle	service	observed services-committees:modules/committees/services/lifecycle/status-change.ts:statusChangeRefusal
`10`must prove Proposed	Adopting terms requires every current or future appointment to identify a term, while past termless service and declined or cancelled offers do not prevent the switch. origin: services-committees:docs/milestones/plans/CMTE-M1-plan.md#D12. Approve the remaining build-time rules as a group? (item 9) proved by `ATS-CMT-CMT-003-06`, `ATS-CMT-CMT-003-09`, `TST-CMT-CMT-251`	validation	service	test services-committees:modules/committees/tests/integration/services/cmte-m1-rules.integration.spec.ts#refuses a switch while a current appointment names no term, naming why
`11`must prove Proposed	The product should support committee custom values and shared forms and layouts on committees as the sole extensible Committees record. origin: services-committees:docs/milestones/plans/CMTE-M1-plan.md#13. Later product rules applied to this plan (Andrew, 2026-10-19, after approval) no proof recorded yet	policy	console, api	unknown FND-CMT-CMT-009
`12` Proposed	Declared committee-layout permissions describe administration but do not demonstrate available form or layout operations.	permission		observed services-committees:aws/committees.service.ts:COMMITTEE_LAYOUTS_PERMISSIONS
`13`must prove Proposed	Committee management permits creation and changes, while a reader receives the records without change controls and cannot write through the API. origin: services-committees:docs/milestones/CMTE-M1-committees-seats-and-rosters.md#D11 proved by `ATS-CMT-CMT-003-07`, `TST-CMT-CMT-109`	permission	api, console	test react-console:acceptance/committees/playwright/journeys/console/CMTE-M1-S15.spec.ts#CMTE-M1-S15
`14`must prove Proposed	Committee creation and dissolution state their business events within the writing transaction; ordinary corrections state no committee event. proved by `ATS-CMT-CMT-003-08`	lifecycle	service	observed services-committees:modules/committees/services/events/committee-events.ts:publishCommitteeWrite

Scenarios

Id	Given	When	Then	Provenance
`01`	The committee explorer is open.	Create Board of Trustees using the board type and populated fields.	Use of terms follows the initial type choice and the record appears on its page, explorer and reporting dataset.	test react-console:acceptance/committees/playwright/journeys/console/CMTE-M1-S02.spec.ts#CMTE-M1-S02
`02`	Finance belongs beneath the board and to a unit.	Save a description-only correction.	The description changes while parentage, unit and portal choices remain.	test react-console:acceptance/committees/playwright/journeys/console/CMTE-M1-S03.spec.ts#CMTE-M1-S03
`03`	Audit belongs beneath Finance, which belongs beneath the board.	Choose Audit as the board's parent.	The circular parentage is refused.	test react-console:acceptance/committees/playwright/journeys/console/CMTE-M1-S27.spec.ts#CMTE-M1-S27

Planning

Implementation

Maintain the record of a governing body ​

Purpose ​

How It Works ​