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.
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.
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.
The Formal Contract
The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
Outcomes
Follow-up proposals retain their meeting contextEach proposal has a recorded acceptance or dismissal
Surfaces
api
Preconditions
New proposals require a scheduled, in-progress or held meeting.
5 rules, 3 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
01must prove
Proposed
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.
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.
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.