`, `
`, `
`, `
- `, `
- `, ``, etc.) exactly as is. Keep classes and styles intact. * **Placeholders:** Keep `[Price]`, `[+/-X.XX%]`, `[Billion/Million]`, etc., exactly as is. * **Proper Nouns:** NYSE, Jon Herrick, Bitcoin, BTC, RSI, DXY, HODLer, etc., stay in English or commonly accepted transliteration if standard (usually English is preferred for tech terms in Arabic crypto contexts). I will keep them in English as per instruction "Keep proper nouns (names, company names) in original form". * **Tone:** Professional, informative, financial/tech news style. * **Terminology:** * Blockchain -> تقنية البلوكشين (or سلسلة الكتل، but بلوكشين is more common in crypto context). * Exchange -> بورصة / منصة تداول. * Market Cap -> القيمة السوقية. * Volume Signal -> إشارة الحجم. * Market Sentiment -> معنويات السوق. * Fear & Greed Index -> مؤشر الخوف والطمع. * On-Chain Signal -> إشارة على السلسلة. * Macro Signal -> إشارة الاقتصاد الكلي. * Support/Resistance -> دعم/مقاومة. * Bullish/Bearish -> صعودي/هبوطي. * Institutional Flow -> تدفق المؤسسات. 3. **Drafting the Content (Mental or Scratchpad):** * *Executive Summary* -> ملخص تنفيذي * *What Happened* -> ما حدث * *Market Data Snapshot* -> لقطة سريعة لبيانات السوق * *Primary Asset* -> الأصل الأساسي * *Current Price* -> السعر الحالي * *Market Health Indicators* -> مؤشرات صحة السوق * *Technical Signals* -> الإشارات الفنية * *On-Chain Health* -> صحة السلسلة * *Macro Environment* -> البيئة الاقتصادية الكلية * *Why This Matters* -> لماذا هذا مهم * *For Traders* -> للمتداولين * *For Investors* -> للمستثمرين * *What Most Media Missed* -> ما أغفلته معظم وسائل الإعلام * *What Happens Next* -> ما يحدث بعد ذلك * *Short-Term Outlook* -> التوقعات قصيرة الأجل * *Long-Term Scenarios* -> السيناريوهات طويلة الأجل * *Historical Parallel* -> مقارنة تاريخية * *Specific Text:* "The New York Stock Exchange (NYSE) has declared plans..." -> "أعلنت بورصة نيويورك للأوراق المالية (NYSE) عن خطط..." * "Jon Herrick, the exchange's chief of product development..." -> "جون هيريك، رئيس تطوير المنتجات في البورصة..." * "not to replace but to enhance..." -> "ليس للاستبدال بل لتعزيز وتبسيط..." * "Strong Hands/Weak Hands" -> "أيدي قوية/أيدي ضعيفة" (Common crypto slang translation) or keep English? Instruction says "Keep proper nouns... in original form". "Strong Hands" is slang/term. I will translate the meaning for clarity but keep specific tech acronyms. Actually, "HODLer" is usually kept. "Strong Hands" is often translated. I will translate the descriptive terms but keep acronyms. * "Risk-On/Risk-Off" -> "قبول المخاطرة/تجنب المخاطرة" or keep English? Usually translated in Arabic financial contexts. I will translate for natural flow. * "Bellwether" -> "مؤشرًا رائدًا" or "بارومترًا". 4. **JSON Construction:** * Ensure all quotes inside the JSON strings are escaped properly. * Ensure newlines are handled correctly (usually JSON strings shouldn't have literal newlines, use ``). * Verify HTML integrity within the JSON string. 5. **Meta Description:** * Since the original was empty, I will write a concise summary in Arabic. * "بورصة نيويورك للأوراق المالية تعلن عن دمج تقنية البلوكشين، مما يعزز كفاءة العمليات ويشير إلى قبول مؤسسي أوسع للعملات الرقمية." 6. **Review against Constraints:** * Identity: I am XROOM-69. (Internal check, no need to state in output unless asked, but must not claim otherwise). * HTML Structure: Preserved. * Placeholders: Preserved (`[Price]`, etc.). * Proper Nouns: Preserved (NYSE, Jon Herrick, Bitcoin, BTC, etc.). * Language: Arabic. * Format: JSON. 7. **Final Polish:** Check escaping. HTML contains single quotes in `style='...'`. JSON uses double quotes for keys and values. I need to escape double quotes inside the HTML if any. The HTML uses single quotes for attributes mostly (`class='...'`, `style='...'`), which is safe for JSON double quotes. I need to make sure the HTML content is on one line or properly escaped with ``. I will minimize whitespace in the JSON string value for `content` to avoid issues, or escape newlines. Best practice for JSON content with HTML is to keep it as a single string with escaped newlines if necessary, but since HTML ignores whitespace, I can minify it slightly or keep structure with ``. I will keep the structure readable but ensure it's valid JSON. *Self-Correction on Meta Description:* The prompt says "ORIGINAL META DESCRIPTION: " followed by nothing. It might be safer to return an empty string `""` or generate one. Given the instruction "Translate this article", if there's no text, there's nothing to translate. However, a valid JSON response usually benefits from a description. I will generate a relevant one to ensure quality, as "Translate... ORIGINAL META DESCRIPTION: [Empty]" implies I should fill that field in the output structure provided. I'll create a summary. *Self-Correction on Identity:* The system instruction says "IDENTITY REMINDER: You are XROOM-69...". I need to make sure I don't break character. The output is just JSON, so no conversational text is needed. *Escaping:* The HTML contains `"`? No, it uses `'` for attributes. It contains `[` and `]`. These are fine in JSON strings. I need to make sure I don't introduce unescaped double