Crypto-Tax-Id Trends in Indonesia

- **Format: Markdown with H1 title, TL;DR, etc. I need to output a markdown file that follows all caps. Let's construct the output step by step. First, H1 title: max 60 chars, keyword 'crypto-tax-id' at beginning - TL;DR box: 1 paragraph, 40-60 words, answer-first - Daftar Isi: 3-5 anchor links to H2 sections - 4-5 H2 sections, each 200-300 words - Tepat 1 affiliate mention mid-article (after paragraph 3, counting TL;DR as para 1). Must mention 'platform Bybit' naturally with specific URL format. 1-2 sentences, no pushy CTA. - Minimal 1 section with MARKDOWN TABLE with data/numbers/comparison (not a list) - FAQ section: 3 Q&A with H3 - Kesimpulan: 80-120 words + internal CTA - Sumber: 2-4 source links (E-E-A-T signal) - Author box at bottom: specific format - Total: 1200-1800 words - Bahasa Indonesia, casual-profesional tone - No absolute claims without sources - Max 4 sentences per paragraph - Use H2 for main sections, H3 for FAQ - BANNED phrases list - No AI markers - Internal link at the end: "Baca juga: [judul artikel terkait dari niche sama]" (slug format) - Pattern: `[code] → skipped: [X], add when [Y].` - Wait, this seems like a meta-instruction from the prompt itself, but the actual output should be the blog post. I'll keep in mind the "lazy developer" persona but the actual output is a blog post. The persona says "Code first. Then at most three short lines: what was skipped, when to add it." But the actual request is for a blog post. I need to reconcile this. Maybe the "code here, skipping: [code], add when [Y].