A meeting note records a synchronous conversation — who participated, what was discussed, what was decided, and what follows. Meeting notes belong to the [[Household Precinct]]: they have templates and conventions suited to capture-first workflows, not the formal structural contracts of [[Garden Precinct]] form types.
Meeting notes live in Meetings/ and use body predicates for classification and attendees:
- is_a::[\[\[Meeting Note\]\]](Meeting%20Note.html)
- has_status::[\[\[Summarized Stage\]\]](Summarized%20Stage.html)
- attendee::[[Person Name]]↑
attendee::[[Person Name]]↑ in the body, not YAML arrays. Full name on first reference; each attendee links to a person note in People/Individuals/.has_status:: with the appropriate stage predicate.--- divider; detailed discussion topics below.created, reviewed, brief_summary, tagline, ground-rules, duration.Simple meetings are flat files. When a meeting has a transcript, chat log, slides, or recording, it becomes a compound document: a folder with the meeting note as the lead file and sidecars at the folder root.
Meetings/
2026-03-05 Meeting Name/
2026-03-05 Meeting Name.md ← lead file (is_a::[\[\[Meeting Note\]\]](Meeting%20Note.html))
2026-03-05 Meeting Name - Transcript (Cleaned).md
2026-03-05 Meeting Name - Chat.md
recording.sidecar.md
Archives/ ← gitignored binaries
recording.mp4
audio.m4a
Garden nodes are often extracted from meeting notes. Decisions made in meetings become [\[\[Decision Form\]\]](Decision%20Form.html) entries. Patterns observed become [\[\[Pattern Form\]\]](Pattern%20Form.html) entries. The meeting note remains the source record in the household precinct; extracted forms use extracted_from:: to link back from the garden precinct.
Conventions from [[Deep Context Garden Conventions]]↑, “Vault Types” section. Meeting predicate architecture from D8-D13 decisions in garden-foundation workstream.