User:Mcint/LlmSummaryPrompt
Jump to navigation
Jump to search
For LLM use, to output summary ready to copy into notes & discord.
= Noisebridge Meeting Notes — Summary Idiom = == Approach == === Ground === * [C]/[c]onsensus everywhere; process implicit. * Summary records entry into '''Big-C Consensus''' register only. === Form === * MediaWiki '''code block responses'''. * Sections as top-level bullets; items as nested bullets: ** ``* (section)`` ** ``** (section item)`` * One section bullet per real section. * One item bullet per real agenda item. * Phrase bundles, not sentences. * Order carries meaning, by convention: ** short, clear lists → order raised ** longer items → context → stakes → considerations → outcome → (notes) === Tone === * Dense; faithful; skimmable. * Mouseover-legible; Discord-signpost-ready. * “Yes, that happened.” == Sections == * Summary begins with date + meeting number, Discord-ready: ``YYYY-MM-DD #NNN`` * Use the '''Meeting Summary''' header order from the template when present. * If the template is blank or partial, use the order below. * Include any sections present in the meeting notes. * Insert additional sections '''between Announcements and Consensus Items''' as applicable. * '''Announcements''' ** Signal words kept. ** date / time / room / guild / counterparty. ** outside involvement; institutional context. ** relevant '''#discord-channel'''. ** paraphrase last, if at all. * '''(Other Sections as Applicable)''' ** Fundraising / Finances / Reports. ** Guilds / Working Groups. ** Standing Items. ** Order as they appear in the notes. * '''Membership''' ** who → category → sponsors. ** objections / blocks if any. ** no permanence implied. * '''Consensus Items''' ** Section always present. ** Lists only '''Big-C Consensus Items'''. ** High-risk / high-value / hard-to-undo; formally handled. ** If none raised / addressed: *** ``None.`` * '''Discussion''' ** Discussions have outcomes, distinct from consensus. ** Outcome type often prompted by raiser: *** decision / advice / temperature check / coordination / other ** Prefer outcome first, then detail: *** e.g. “On LED Art Donation/Loan — Elan seeks notify, vibe-check, coordinate with lender.” ** Phrase order follows Form conventions. ** Enough signal to decide “open + read”.
Subpages, other
[edit | edit source]- Mcint/5MoF/Wiki
- Mcint/GettingInvolved
- Mcint/GettingInvolved/Wiki
- Mcint/Hardware Hacking Kit
- Mcint/LlmSummaryPrompt
- Mcint/Lore
- Mcint/Maxims
- Mcint/NBGov
- Mcint/NBGov/ConflictTransparency
- Mcint/NBRequestsForRonald
- Mcint/New users
- Mcint/NoisebridgeOutOfSight
- Mcint/Project Derisking
- Mcint/Projects
- Mcint/Projects/Member system
- Mcint/ReportingIssues
- Mcint/TendingTheCommons
- Mcint/Todo
- Mcint/WikiMaxxing
- Mcint/WikiStyling
- Mcint/WikiTools
- Mcint/common.css
- Mcint/common.js
- Mcint/gadgets
- Mcint/global.css
- Mcint/global.js
- Mcint/header
- Mcint/pfp
- Mcint/vector-2022.css