Release meeting papers as a packet

Purpose

A packet brings together the papers supporting a meeting. Staff prepare the entries and publish them when the collection is ready to share.

How It Works

Staff add papers to the meeting as a whole or connect them to individual agenda topics. A title and classification identify each entry without embedding the file in the meeting record. File preparation runs before the material write, and the saved reference is attached transactionally. Publication releases the existing collection, while subsequent additions inherit immediate release. Audience settings still govern what a signed-in reader receives. Current committee participation can matter alongside an explicit meeting participant record. Held meetings can still receive supporting papers, although a cancelled meeting cannot. Deleting an entry records detachment rather than promising immediate file removal. The cleanup consumer handles later retirement. Link-only entries and editable labels and ordering remain approved directions whose complete behaviour is not established here.

Relationships

Agenda preparation supplies optional topic links. Participant communications handle publication notices, and the shared file pipeline supplies preparation and retirement.

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: Meeting papers retain managed file referencesPublication releases the prepared packet together
Surfaces: api
Preconditions: The meeting is available and has not been cancelled.
Intent sources: services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#D10services-committees:docs/milestones/plans/CMTE-M3-plan.md#4. Assumptions

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-DAT-004 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

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

Business Rules

9 rules, 8 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	A material identifies its meeting, optionally an agenda item of that meeting, and exactly one managed file or document reference. no proof recorded yet	validation	service, database	observed services-committees:modules/meetings/db/meeting-materials.table.ts:meeting_materials_one_file_check
`02`must prove Proposed	File preparation produces a permanent reference in the meeting-materials storage area and rejects foreign-workspace references or unsafe files. no proof recorded yet	validation	service	test services-committees:modules/meetings/tests/integration/services/meetings.integration.spec.ts#refuses a file of another tenant and writes nothing
`03`must prove Proposed	Adding material to a cancelled meeting is refused. no proof recorded yet	validation	service	observed services-committees:modules/meetings/services/persistence/meeting-materials.ts:addMaterial
`04`must prove Proposed	Packet publication is allowed once before a meeting ends, stamps unreleased materials as published, and causes later additions to receive a publication timestamp immediately. no proof recorded yet	lifecycle	service	test services-committees:modules/meetings/tests/unit/services/meeting-lifecycle.spec.ts#publishes the packet once, of a meeting that has not ended
`05`must prove Proposed	Portal material disclosure requires both its audience permission and either a publication timestamp or a non-draft agenda viewed by someone participating in the meeting or committee. no proof recorded yet	permission	service	observed services-committees:modules/meetings/services/portal/portal-meetings.ts:pageFor
`06`must prove Proposed	Material deletion detaches its managed asset in the same transaction, leaving subsequent cleanup to retire eligible files. no proof recorded yet	lifecycle	service	observed services-committees:modules/meetings/services/persistence/meeting-materials.ts:deleteMaterial
`07`must prove Proposed	The product should accept a packet item containing only a title and web address while the shared upload control is unavailable. origin: CMTE-M3 D10 (Andrew 2026-10-21, services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#Decisions) no proof recorded yet	policy		documented services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#Decisions
`08`must prove Proposed	The product should support renaming and reordering packet entries, while replacing a file requires removing the old entry and adding another. origin: CMTE-M3 D12 item 7 (Andrew 2026-10-21, services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#Decisions) no proof recorded yet	policy		documented services-committees:docs/milestones/plans/CMTE-M3-plan.md#D12. Smaller rules to approve as a group
`09` Proposed	The proposed storage direction uses managed files until a Documents library is available, with the stored material shape reserving either kind of reference.	policy	database	documented services-committees:docs/milestones/plans/CMTE-M3-plan.md#4. Assumptions

Scenarios

Id	Given	When	Then	Provenance
`01`	A scheduled meeting has prepared supporting papers	Staff publish its packet	The meeting receives a packet publication timestamp	test services-committees:modules/meetings/tests/e2e/meetings.e2e.spec.ts#publishes the packet

Planning

Release meeting papers as a packet ​

Purpose ​

How It Works ​

Relationships ​