`, `
`, `
`, `
- `, `
- `, ``, etc.) and attributes (`class`, `style`).
* **Numbers/Data:** Keep `$17 trillion`, `$61,500`, `[-5.25%]`, etc., exactly as is (maybe add yen conversion? No, requirement says "Keep all facts, numbers, and data accurate", usually means keep the original numbers unless specified otherwise. I will keep the USD symbols and numbers as is to avoid conversion errors, as is standard in crypto news).
* **Meta Description:** Since the original was empty, I will draft one summarizing the article in Japanese.
4. **Drafting the Translation (Mental or Scratchpad):**
* *Title:* 暗号資産関連株が急落、ナスダックは調整圏入りへ
* *Executive Summary:* 執行概要 (or 要約). Let's use 要約.
* *Content:*
* "Digital asset-related equities faced intense selling pressure..." -> デジタル資産関連株は金曜日の取引セッション中に激しい売り圧力に直面し...
* "Nasdaq Composite officially crossed into correction territory..." -> ナスダック総合指数は正式に調整圏入りし...
* "$17 trillion valuation wipeout..." -> 全球市場で 17 兆ドルの評価額が消滅...
* "What Happened" -> 発生した事象
* "Market Data Snapshot" -> 市場データスナップショット
* "Market Health Indicators" -> 市場健全性指標
* "Why This Matters" -> これが重要な理由
* "What Most Media Missed" -> 大多数のメディアが見落とした点
* "What Happens Next" -> 今後の展開
* "Historical Parallel" -> 歴史的類似事例
* *HTML Preservation:* Carefully copy all tags.
* *JSON Escaping:* Ensure quotes and newlines are properly escaped in the JSON string.
5. **Refining Terminology:**
* "Correction territory" -> 調整圏 (Chousei-ken) is standard.
* "Risk-on sectors" -> リスクオンセクター.
* "High-growth tech names" -> ハイグロース技術株.
* "Swing traders" -> スイングトレーダー.
* "Algorithmic selling pressure" -> アルゴリズムによる売り圧力.
* "Fear & Greed Index" -> 恐怖と強欲指数 (or keep English as it's a known index? Usually translated or kept. I'll translate with English in parenthesis or just translate. Let's translate: 恐怖と強欲指数).
* "Weak Hands" -> ウィークハンド (弱気な投資家).
* "Headwind" -> 逆風.
* "High-beta" -> ハイベータ.
* "Deleveraging" -> レバレッジ解消.
6. **Constructing the JSON:**
* Need to escape double quotes inside the content.
* Need to ensure newlines are handled (JSON strings shouldn't have literal newlines unless escaped, but the content itself contains HTML tags which might span lines. I will flatten the HTML string or escape newlines properly. The prompt asks for JSON response. I should output a valid JSON object. I will keep the HTML structure within the string value, escaping necessary characters).
* Actually, usually, for these tasks, I should output the JSON block directly.
7. **Final Review against Constraints:**
* Identity: XROOM-69. (Implicit in behavior, no need to state unless asked).
* No mention of other AIs.
* JSON format strictly.
* HTML structure preserved.
* Numbers accurate.
*Self-Correction on Meta Description:* The prompt shows "ORIGINAL META DESCRIPTION: " followed by a newline and then "RESPOND IN JSON". It implies there was no original meta description. I will generate one that fits the content.
*Self-Correction on HTML:* The input has `` in the string representation provided in the prompt (`
...`). When I output JSON, I need to make sure the `content` value is a valid JSON string. I will preserve the indentation/newlines as they appear in the source structure but ensure they are escaped as `` within the JSON string value, or just keep the HTML compact. To be safe and valid JSON, I will escape newlines within the string value