Objective

{TL;DR — one self-contained sentence beginning with the bolded, memo-linked subject name. If a source URL exists, make it a markdown link: Subject. This is the line answer engines extract first — it must define the subject completely on its own, with no reliance on surrounding context. Prose only, no list markers. Target: 20–35 words.}

{Opening paragraph — 60–110 words in neutral, Wikipedia-style voice. Expand the TL;DR with category, function, and why the subject matters. Do not re-bold the name. Weave in @mentions for named entities that have memos; search the library first with search_memos. Voice rules: third-person, factual, non-promotional; no puffery (“innovative,” “powerful,” “groundbreaking,” “important”); no first person; no rhetorical questions; attribute contested or interpretive claims (“According to…“, “It is described as…“); paraphrase over quotation; avoid throat-clearing (“In today’s world,” “At its core”); do not mention missing information. Every paragraph must stand alone — a reader dropped into any chunk should still get a complete fact.}

{Key Facts subsection — include the ## Key Facts header and this block ONLY if the subject has structured attributes worth extracting (entity, product, company, framework, place, person with role). Skip entirely for abstract concepts or very short entries. Each bullet is a self-contained “Attribute: value” pair — the closest a memo comes to schema markup and highly extractable by answer engines. Target: 3–7 bullets. Omit any line that does not apply; never invent values. Example attributes: Category, Origin (year founded/created/published), Role / Function, Home / URL, Parent / Ecosystem (@mention of larger system), Notable for. Tailor the attribute set to the subject type.}

{How It Works subsection — include the ## How It Works header and this block ONLY when the subject has mechanism, process, or internal structure worth documenting (products, features, frameworks, methodologies). Skip for people and abstract ideas. Write 1–3 atomic paragraphs OR a bulleted list of capabilities in the form “Capability name — one-sentence description.” Each item must stand alone. Target: 3–8 bullets or 150–300 words of prose. Lead with the most important mechanism; answer engines cite the first 1–2 sentences of every subsection.}

{Why It Matters subsection — include the ## Why It Matters header and this block ONLY when there is a functional, systemic, or cultural claim to make beyond what the opening paragraph covered. 1–2 atomic paragraphs, 1–3 sentences each, explaining the role the subject plays, the problem it solves, or the pattern it represents in a broader system. Attribute interpretive claims cleanly. Target: 80–160 words.}

{FAQ subsection — include the ## FAQ header and this block for any memo with public or SEO intent; strongly recommended. Answer engines cite question-shaped headings disproportionately. Write 2–5 short Q&A pairs as ### Question followed by a 1–3 sentence answer. Each question should be a real query a reader might type. Each answer must begin with a direct, self-contained response in the first sentence; expand only if needed. Example question shapes: “What is X used for?“, “How is X different from Y?“, “Does X support Z?“, “Who created X?“, “When was X introduced?“. Total target: 150–400 words.}

{Related subsection — include the ## Related header and this block whenever 3+ genuinely related memos exist in the library. Bulleted list of 3–7 @mentions in the form “@Title — one-line relationship description.” Only link memos that exist and are genuinely related; do not pad. This section builds the entity graph LLMs use for retrieval. Use the url field from search_memos results; never construct URLs manually.}

{If any subsection above is skipped, omit its entire placeholder line — do not leave a blank line behind. No blank lines anywhere in the final memo.}

Subjective

{Write 1 paragraph in first-person reflective voice ONLY if subjective context was provided in chat. If no subjective context was provided, output nothing here — not even a blank line. The # Subjective header above must remain regardless. Content rules when populated: intimate, thoughtful, precise; shift clearly from encyclopedic distance into lived experience; no invented emotions or conclusions; no generic self-help language or TED-talk phrasing; no exaggerated vulnerability. Focus on resonance — why this matters to me, how I’ve encountered it, what tension it names, what pattern it represents in my life or work. Preserve and integrate any @mentions given in context. Avoid repeating the objective definition; translate it into personal meaning, metaphor, or orientation. End with a gently conclusive line, not a performative one. Target: 70–120 words.}

Contexts

{1–3 precise 🏷️#hashtags as bulleted items that name the collection this memo belongs to, not what it mentions. Ask “Is this memo a [tag]?” not “Does this memo mention [tag]?” Use existing tags before inventing new ones — check list_tags first. Alphabetize. Never duplicate tags between Contexts and the notes # Tags section. Format each as its own bullet: - #tag-name.}