Broken/Prompt:History of AXA: Difference between revisions

Browse history interactively

Newer edit →

Content deleted Content added

VisualWikitext

Inline

Revision as of 23:41, 5 February 2026

Access to this page is restricted to authorized editors.

@@ Line 60: / Line 60: @@
 Success criteria
 If I read your report, I should understand: (1) what changed when and why, (2) how AXA’s business model evolved, and (3) what external forces and internal decisions best explain AXA’s trajectory.
+-->
+<!--
+CONVERT DEEP RESEARCH REPORT TO MEDIAWIKI
+**Role:** You are a senior Wikipedia Administrator and MediaWiki syntax expert known for engaging, high-quality encyclopedic writing.
+**Task:** Transform the provided "Deep Research Report" (History of AXA) into a publication-ready **MediaWiki article** about the company’s historical development. **CRITICAL:** You must output the entire response (including the references) inside a single code block. Use **American English**.
+---
+## I. Tone & Editorial Standards (Fluid Encyclopedic Prose)
+. **Narrative Flow (Crucial):** Do not write as a list of disconnected facts. Write in **cohesive, fluid paragraphs** that connect events and causes (examples: “Following this acquisition,” “In response to regulatory changes,” “Consequently,” “In parallel with”). The result should read like a coherent corporate history, not a timeline dump.
+. **Neutral Point of View (NPOV):** Maintain an objective tone. Avoid praise, hype, or editorial judgments. If the input contains interpretation or claims of “leadership,” “first,” “largest,” etc., attribute them to the cited sources.
+. **Scope Control:** The subject is **AXA’s history**. Focus on: origins, rebranding, expansion, major mergers and acquisitions, portfolio reshaping, leadership eras, strategic plans, crises and risk management, ESG/climate commitments, and major controversies/disputes that materially affected the group. Mention secondary entities (acquired companies, regulators, peers) only as needed for clarity.
+. **No Invention Rule:** Use the report as the sole factual basis. Do not add facts, figures, dates, or sources not present in the report. If a detail is missing, omit it.
+---
+## II. Formatting & MediaWiki Syntax (Strict)
+. **Strict Paragraph Structure & Visual Cues:**
+   - **Emoji Cues (Mandatory):** Start **every paragraph** with exactly **one emoji**. **Each emoji must be unique across the entire article.**
+   - **Lead Paragraph Rule:** The lead paragraph must begin with an emoji followed immediately by `'''AXA'''` in MediaWiki bold syntax (no Markdown bold).
+   - **Bold Cue Rule (After the Lead):** For every paragraph after the lead, start with:
+     `😀 '''Concise cue.'''` then continue the paragraph.
+     - The cue must be short (2–6 words) and match the paragraph theme (examples: `'''Origins in Normandy.'''`, `'''UAP merger integration.'''`, `'''Climate divestment policy.'''`).
+   - **Avoid Bullet Points:** Do not use bullet points for history, milestones, strategies, or controversies. Convert timeline/table content into prose.
+. **Wiki Markup Rules:**
+   - Headings: `== Section ==`, `=== Subsection ===`
+   - Bold: use `'''like this'''`
+   - **Do not add interlinks** (no `[[term]]`).
+   - Do not add images, infoboxes, navboxes, or templates except `{{section separator}}` and `{{reflist}}`.
+. **Date Style:** Use a consistent style throughout (example: “November 1996” or “1996”). Keep it internally consistent.
+---
+## III. Mandatory Page Structure
+. **Page Header Structure (MANDATORY):** The very first line of your output code block must be:
+) `== Overview ==`
+   Then immediately provide:
+) The introductory lead paragraph (starts with an emoji, then `'''AXA'''`).
+. **Section Separators (MANDATORY):**
+   - Before **each** level-2 heading (`== ... ==`) after the overview block, insert:
+     `{{section separator}}`
+. **Required Section Layout (Use these level-2 headings in this order):**
+   - `== Overview ==` (lead only)
+   - `== Origins and formation ==`
+   - `== Brand and identity ==`
+   - `== Expansion and globalization ==`
+   - `== Strategy, risk, and portfolio shifts ==`
+   - `== ESG and climate initiatives ==`
+   - `== Controversies and disputes ==`
+   - `== Legacy and positioning ==`
+   - `== References ==`
+   Notes:
+   - Use level-3 subsections by era when helpful (example: `=== 1980s consolidation in France ===`, `=== 1990s global scale-up ===`, `=== 2000–2016 crisis-proofing ===`, `=== 2016–present transformation ===`).
+   - Ensure each section contains narrative paragraphs with the required emoji + bold cue rules.
+---
+## IV. Citation Logic (CRITICAL)
+. The input contains in-text numeric markers (example: `1`, `[1]`, `[45]`) and a corresponding **source list**. You must:
+) **Match:** Map each marker to the correct source in the provided list.
+) **Format:** Convert each marker into an inline citation using:
+      `<ref>{{cite web |url=INSERT_URL |title=INSERT_TITLE |publisher=INSERT_PUBLISHER |accessdate=2026-02-05}}</ref>`
+      - If the source is a PDF or a book listed with a URL, still use `cite web` (unless the report provides full bibliographic fields, in which case you may use `cite book`).
+) **Deduplicate:** Use named references:
+      - First use: `<ref name="TAG">{{cite web ...}}</ref>`
+      - Repeat use: `<ref name="TAG" />`
+      - TAG should be short and stable (example: `axa-timeline`, `atlas-mag-axa-growth`, `reuters-2011-aph`, `independent-1996-uap`).
+) **Reference Section:** End with:
+      `== References ==`
+      `{{reflist}}`
+. **Citation placement:** Add citations at the end of the relevant sentence, not as a standalone sentence. Avoid citation spam; cite the most claim-heavy sentences.
+---
+## V. Input (ATTACHED)
+**Input File (ATTACHED):**
+The "Deep Research Report" titled **History of AXA** (including narrative body, any timeline/table material, in-text numeric markers, and the source list) is attached in this chat. Read it in full and use it as the sole input for the transformation above.
+---
+## VI. Output Container (MANDATORY)
+. Output the final MediaWiki article wrapped in a single standard markdown code block (start with ``` and end with ```). No commentary outside the code block.
 -->