Minutes

What It Models

Minutes are the written record prepared from a gathering and eventually approved as its official account. The object includes working item notes and suggested follow-ups because they feed that record. A correction preserves the earlier approved body and creates another revision.

Identity and Attributes

The revision identity distinguishes an approved account from its replacement draft. Stored content is a managed file reference plus a byte fingerprint. Production assembly uses agenda order, attendance and notes without inference.

Relationships

A meeting owns its revisions and tracks the newest. An approval decision points at a particular revision, while a correction points at the account it supersedes. Follow-ups retain a task integration link without owning the future CRM task.

Invariants

Body editing, circulation and approval each have their own guards. Circulated text returns to draft before editing. Accepted and dismissed follow-ups are final application decisions, and confidential session notes are excluded from assembly.

How It Is Stored and Shared

The meetings service owns minutes, notes and follow-ups. The decisions service writes approval and correction in the shared database boundary. Platform stores bodies, and Queries reads minutes and action-item datasets. Minutes do not declare custom fields.

Open Design Questions

Product must settle direct approval authority and evidence requirements. Task creation is still a placeholder. Database immutability declarations and the visible attendance correction history require stronger evidence before preparation treats them as guaranteed.