--- id: CAP-CMT-MTG-009 title: Record and decide meeting follow-up proposals feature: FEAT-CMT-MTG-02 product_area: committees module: meetings revision: 1 status: draft product_intent: proposed implementation_evidence: partially-observed supersedes: - react-console acceptance inventory CAP-CMT-MTG-020 - react-console acceptance journeys CMT-ACC-0243 source_sha: services-committees: 36129c24daeaadcdb339218c38cdeaff9861359d react-console: baf6dae382d6f41dce976c7f848667ccc37e076f intent_sources: - 'services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#D8' - 'services-committees:docs/milestones/plans/CMTE-M3-plan.md#4. Assumptions' purpose: >- The secretary retains proposed follow-up work and records which proposals the meeting keeps or dismisses. outcomes: - Follow-up proposals retain their meeting context - Each proposal has a recorded acceptance or dismissal concepts: - CON-CMT-MTG-002 actors: - ACT-CMT-002 - ACT-CMT-008 surfaces: - api preconditions: - 'New proposals require a scheduled, in-progress or held meeting.' postconditions: [] permissions: - key: committees.meetings.read where_checked: api scope: tenant - key: committees.meetings.manage where_checked: api scope: tenant rules: - id: BR-CAP-CMT-MTG-009-01 proved_by: [ATS-CMT-MTG-007-14, ATS-CMT-MTG-009-01, ATS-CMT-MTG-009-04, ATS-CMT-MTG-009-05, TST-CMT-MTG-122, TST-CMT-MTG-216] statement: >- Proposing follow-up work is refused for draft or cancelled meetings, any linked agenda item must belong to the meeting, and minutes-origin proposals require an existing minutes record. kind: validation enforced_at: - service must_prove: true provenance: test source: >- services-committees:modules/meetings/tests/integration/services/minutes.integration.spec.ts#proposes an item from the minutes, naming them origin: none - id: BR-CAP-CMT-MTG-009-02 proved_by: [ATS-CMT-MTG-009-02, TST-CMT-MTG-122, TST-CMT-MTG-216] statement: >- Acceptance or dismissal requires the current proposal version and a still-proposed item; an already decided item cannot be decided again. kind: lifecycle enforced_at: - service must_prove: true provenance: test source: >- services-committees:modules/meetings/tests/integration/services/minutes.integration.spec.ts#refuses to accept an item already decided origin: none - id: BR-CAP-CMT-MTG-009-03 proved_by: [ATS-CMT-MTG-009-03, TST-CMT-MTG-122, TST-CMT-MTG-212, TST-CMT-MTG-216] statement: >- Acceptance records the proposal as accepted and creates a linked record with no task identity, without invoking CRM task creation. kind: policy enforced_at: - service - database must_prove: true provenance: test source: >- services-committees:modules/meetings/tests/integration/services/minutes.integration.spec.ts#writes the accepted item’s task link with a null task id, from the minutes origin: >- CMTE-M3 D8 (Andrew 2026-10-21, services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#Decisions) - id: BR-CAP-CMT-MTG-009-04 proved_by: [] statement: >- The earlier architectural proposal routes accepted follow-up work to CRM tasks with staff assignees until volunteer assignment becomes available; the later meetings decision keeps only the meeting record for that milestone. kind: policy enforced_at: [] must_prove: false provenance: documented source: 'services-committees:docs/milestones/plans/CMTE-M3-plan.md#4. Assumptions' origin: none - id: BR-CAP-CMT-MTG-009-05 proved_by: [] statement: >- A follow-up proposal can store a responsible contact, due date and proposed, accepted or dismissed status, but supplies no task reminders, execution tracking or personal task list. kind: policy enforced_at: - service must_prove: false provenance: observed source: >- services-committees:modules/meetings/services/persistence/proposed-action-items.ts:proposeActionItem; services-committees:modules/meetings/ports/task-creator.ts:taskCreator origin: none scenarios: - id: SC-CAP-CMT-MTG-009-01 given: The November minutes propose that the treasurer circulate a revised budget by December when: The secretary accepts the proposal then: The proposal retains accepted status and a task link without a task identity provenance: test source: >- react-console:acceptance/committees/playwright/journeys/meetings/CMT-ACC-0243.spec.ts#CMT-ACC-0243 edge_cases: [] constraints: [] depends_on: - CAP-CMT-MTG-001 related: - CAP-CMT-MTG-007 journeys: - JNY-CMT-MTG-001 open_questions: [] evidence: - >- services-committees at 36129c24: Follow-up proposals, acceptance and dismissal, and the unavailable CRM task creator. - >- react-console at baf6dae3: the meeting acceptance specifications cited by this capability and its acceptance set. controls: - 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-DAT-001 - TC-DAT-002 - TC-DAT-003 - 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 exercised_by: [FAS-CMT-MTG-02-01, FAS-CMT-MTG-02-05] suites: [TST-CMT-MTG-122, TST-CMT-MTG-212, TST-CMT-MTG-216] --- # Record and decide meeting follow-up proposals ## Purpose A meeting can produce work that deserves a recorded answer before it becomes a task. The secretary captures that work and decides which proposals to retain. ## How It Works Staff enter follow-up titles and optional descriptions against a called meeting. An agenda topic can identify the discussion that produced the work. A responsible contact and due date provide context without establishing a task assignment. Selecting a minutes origin also records the meeting’s current minutes reference. The secretary accepts or dismisses each proposal using its saved version. An accepted proposal receives a task-link record whose task identity is empty. Dismissal retains the proposal’s recorded outcome without such a link. The current workflow does not invoke the available task-creation port. The later meetings decision keeps this work on the meeting for that milestone, although the earlier plan still describes a staff-task proposal. Task reminders and execution progress require a separately delivered task workflow. ## Relationships Minutes preparation supplies source context for minutes-origin proposals. Agenda preparation supplies topic links. CRM remains the owner of any future tasks created from accepted work.