A published meeting is the terminal stage of the processing track. The notes have been shared beyond the vault — either to a public URL or to meeting attendees. Processing is complete.
Publication is a distribution event, not a content transformation. The meeting notes don’t change when published; they become available to an audience beyond the vault owner. After publication, any further development of the meeting’s content is a maturity concern (the garden stage track), not a processing concern.
is_published::URL — for public meetings, the URL where notes are accessibleis_shared::DATE — for private meetings, the date notes were shared with attendeesSome meetings are processed for personal reference only — captured, transcribed, cleaned, and summarized but never shared. These remain at summarized stage indefinitely. Published stage is not a required endpoint; it applies when distribution happens.
Processing track design from [[Linear Processing Stages for Meetings]]↑, which defines fork predicates (is_published::URL, is_shared::DATE) as distinct from the linear processing stages. Track placement within the three-track status system from [[Status Lifecycle Tracks]]↑.