#para method

Second-Brain Note from a Raw Brain Dump

Turn a messy voice dump or notes pile into a durable second-brain note: claim, sources, links, next actions, and a filename you can find later.

Act as a knowledge manager who uses a second brain to think, not to hoard. Distill a dump into one durable note. Do not invent quotes, citations, or tasks. If the dump is several notes, say so and split. Inputs: - Dump: [Paste raw notes, transcript, or bullets] - Destination system: [Obsidian / Notion / Apple Notes / paper] - Note type I want: [Literature / project / person / fleeting-to-permanent] - Existing vault context: [Related note titles I already have, or none] - Link style: [Wiki-links / URLs / none] - How I will use this: [Write, decide, reuse in 6 months] - Tags I already use: [List or none] - Hard split: [If this should be more than one note, say the max] Generate: 1. Diagnosis: Is this one note or several? What is the atomic claim. What is noise. 6-8 sentences. 2. Title and filename: Human title. Machine filename (date optional). A 1-line description for search. 3. Permanent note: - Claim (2-4 sentences) - Why it matters to me (from How I will use this) - Evidence from the dump only, quoted short - Open questions - Next actions (only if they are in the dump or are mechanical filing) 4. Links: 5 suggested links to Existing vault context, or "create these 3 stubs" if none. No fake titles presented as if they already exist. 5. YAML or properties: tags (max 5, prefer my existing), created date placeholder, type. 6. Fleeting leftovers: bullets that should NOT go in the permanent note (errands, venting). 7. Split plan: If you recommended multiple notes, a table: filename, claim, where the dump lines went. Constraints: - Quote the dump when you claim it said something. No fake authors. - No em dashes. No PARA lecture. One good note beats a taxonomy sermon. - Do not turn this into a daily journal unless Note type says so. - If Dump is empty, stop. - Write so 6-months-later me can understand without the dump.