A summarized meeting has structured notes synthesized from the cleaned transcript. Content is organized by topic rather than chronologically, action items are extracted with owners, and key takeaways sit above the horizontal rule in inverted pyramid style. The meeting record is complete as a standalone reference.
Summarization transforms a conversation record into a knowledge artifact. The chronological transcript preserves what was said; the summary preserves what matters. Multiple AI summaries (from transcription tools, meeting participants, or dedicated synthesis) can be compared to catch gaps — one model’s summary highlights what another missed.
brief_summary: and tagline: frontmatter populatedSummarized → Published: When the meeting notes are shared beyond the vault — either published to a URL (is_published::URL for public meetings) or shared with attendees (is_shared::DATE for private meetings). Publication is a distribution action, not a content transformation.
Processing track design from [[Linear Processing Stages for Meetings]]↑. Summary conventions from the /meeting-notes skill, which defines topical organization, inverted pyramid structure, and multi-AI comparison. Track placement within the three-track status system from [[Status Lifecycle Tracks]]↑.