We need to produce JSON with fields: seo_title, summary, key_entities (companies, people, locations), expert_faq (question, answer), internal_link_anchor, primary_keyword, secondary_keywords, content_type.

Constraints: summary must be 180-250 words, split into exactly 3-4 paragraphs, each paragraph 45-65 words. Must bold selectively with double asterisks, 3-5 bolded terms total.

We have source: "Set Up Your Own DoH Service" article URL from nochan.net, Hacker News points 7, comments 2. The source is just headline? The original text: "Set Up Your Own DoH Service". That's 5 words? Actually "Set Up Your Own DoH Service" is 6 words. The source says original: Article URL ... Comments URL ... Points: 7 # Comments: 2. So we only have that headline. We must elaborate based on what is provided, but cannot invent facts not in source. However we can infer context: DoH = DNS over HTTPS, a protocol for encrypting DNS queries. We can talk about setting up your own DoH service, its significance for privacy, tools like Cloudflare's cloudflared, etc. But we must not invent facts not in source. However we can elaborate on what is provided: The article is about setting up your own DoH service. We can explain what DoH is, why someone might want to run their own, mention typical software, but we must ensure not to add specifics not implied. The source implies that there is an article guiding how to set up a DoH service. We can talk about general steps: using a server, configuring a DoH resolver like CoreDNS, etc. But are those specifics in source? Not explicitly. However we can say "The article likely covers steps such as choosing a resolver software, configuring TLS certificates, and exposing the service over HTTPS." Is that invented? It's implied by the topic. The instruction: "do NOT invent facts, stats, or background information from your training data." But we can use general knowledge? The policy says we must not hallucinate. However we can elaborate on what is provided: The sou