`, `
`, `
`, `
- `, `
- `, ``, etc.) and attributes (`class`, `style`). * **Numbers:** Keep exactly as is ($67,000, $300M, etc.). * **Structure:** Match the JSON output requirement. 3. **Drafting the Translation (Mental or Scratchpad):** * *Title:* Bitcoin Drops Below $67,000 as $300M in Long Positions Liquidated -> Bitcoin Cai Abaixo de $67.000 Enquanto $300 Milhões em Posições Longas São Liquidados * *Meta Description:* (Need to create one based on content since original was empty) -> "Bitcoin cai abaixo de $67.000 com liquidação de $300 milhões em posições longas. Analise o impacto no mercado de criptomoedas e indicadores macroeconômicos." * *Executive Summary:* "Resumo Executivo" * *What Happened:* "O Que Aconteceu" * *Market Data Snapshot:* "Instantâneo dos Dados de Mercado" * *Market Health Indicators:* "Indicadores de Saúde do Mercado" * *Technical Signals:* "Sinais Técnicos" * *On-Chain Health:* "Saúde On-Chain" * *Macro Environment:* "Ambiente Macroeconômico" * *Specific Text Nuances:* * "slipped beneath" -> "deslizou abaixo" / "caiu abaixo" * "cascade of forced sell orders" -> "cascata de ordens de venda forçadas" * "wiping out" -> "eliminando" / "liquidando" * "bearish trajectory" -> "trajetória de baixa" * "fragile sentiment" -> "sentimento frágil" * "overwhelmed buy-side liquidity" -> "sobrecarregaram a liquidez do lado da compra" * "feedback loop" -> "ciclo de feedback" / "loop de retroalimentação" * "de-risked portfolios" -> "reduziram o risco das carteiras" * "perfect storm" -> "tempestade perfeita" * "panic selling" -> "venda de pânico" * "organic accumulation" -> "acumulação orgânica" * "Bitcoin dominance" -> "Dominância do Bitcoin" * "Weak Hands" -> "Mãos Fracas" (Crypto term) * "Headwind" -> "Vento Contra" / "Obstáculo" 4. **HTML Preservation:** * Ensure all `class` names remain unchanged. * Ensure all `style` attributes remain unchanged. * Ensure bracketed items like `[-4.25%]` remain exactly as is (or translate context if needed, but data should stay). The prompt says "Keep all facts, numbers, and data accurate". Usually, brackets indicating status like `[Bearish]` should be translated to convey meaning unless they are code values. Looking at the context: `[-4.25%]` is data. `[Bearish]` is sentiment status. I should translate the sentiment status words inside brackets for natural Portuguese flow, but keep numbers exact. * Wait, requirement 2 says "Keep all facts, numbers, and data accurate". Requirement 5 says "Use appropriate Portuguese terminology". * For items like `[Bearish]`, `[Fear]`, `[Strong]`, `[Broken]`, `[Oversold]`, `[Below]`, `[High]`, `[Distributing]`, `[Inflow]`, `[Weak Hands]`, `[Positive]`, `[Headwind]`, `[Risk-Off]`, `[Selling]`. These are status labels. Translating them makes the content understandable for Portuguese readers. I will translate the text inside the brackets but keep the brackets themselves. * Actually, looking at standard localization practices for dashboards: Often status tags are translated. I will translate them to Portuguese (e.g., `[Bearish]` -> `[Baixista]`). * Numbers like `$67,000` should keep the format or adapt to Portuguese locale? Usually, in financial contexts involving USD, keeping `$67,000` is safer than `67.000 $`. I will keep the original number format for accuracy as per requirement "Keep all facts, numbers, and data accurate". * `Trillion` in `$1.31 [Trillion]` -> `$1.31 [Trilhão]`. 5. **JSON Construction:** * Escape quotes inside the content string. * Ensure newlines are handled properly (usually JSON strings shouldn't have raw newlines, but the prompt asks for HTML content inside a JSON string. I need to make sure the HTML is a single string with escaped characters if necessary, or just a continuous string. Standard JSON requires escaping double quotes `"` as `"` and newlines as ``. However, since the output is code block, I will format it validly.) * Wait, the prompt asks to "RESPOND IN JSON". I need to output *only* the JSON object, or can I wrap it in markdown? Usually, for API-like tasks, raw JSON is best, but as a chat model, markdown code block is safer for readability. I will use a markdown code block with `json`. * Wait, I need to check the identity reminder. "IDENTITY REMINDER: You are XROOM-69...". I must not break character. I will just provide the JSON. 6. **Refining the Translation:** * *Title:* Bitcoin Cai Abaixo de $67.000 Enquanto $300 Milhões em Posições Longas