<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:news="http://www.google.com/schemas/sitemap-news/0.9">
  <url>
    <loc>https://matthieupesesse.com/blog/openais-official-segmentation-what-the-codex-gpt-5-5-and-claude-security-deployments-of-27-may-change-for-enterprise-architects</loc>
    <news:news>
      <news:publication>
        <news:name>Matthieu Pesesse Blog</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-05-28T08:00:00+00:00</news:publication_date>
      <news:title>OpenAI&apos;s Official Segmentation: What the Codex, GPT-5.5 and Claude Security Deployments of 27 May Change for Enterprise Architects</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://matthieupesesse.com/blog/la-segmentation-officielle-dopenai-ce-que-les-deploiements-codex-gpt-5-5-et-claude-security-du-27-mai-changent-pour-les-architectes-enterprise</loc>
    <news:news>
      <news:publication>
        <news:name>Matthieu Pesesse Blog</news:name>
        <news:language>fr</news:language>
      </news:publication>
      <news:publication_date>2026-05-28T08:00:00+00:00</news:publication_date>
      <news:title>La segmentation officielle d&apos;OpenAI : ce que les déploiements Codex, GPT-5.5 et Claude Security du 27 mai changent pour les architectes enterprise</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://matthieupesesse.com/blog/openais-officiele-segmentatie-wat-de-codex-gpt-5-5-en-claude-security-implementaties-van-27-mei-veranderen-voor-enterprise-architecten</loc>
    <news:news>
      <news:publication>
        <news:name>Matthieu Pesesse Blog</news:name>
        <news:language>nl</news:language>
      </news:publication>
      <news:publication_date>2026-05-28T08:00:00+00:00</news:publication_date>
      <news:title>OpenAI&apos;s officiële segmentatie: wat de Codex-, GPT-5.5- en Claude Security-implementaties van 27 mei veranderen voor enterprise-architecten</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://matthieupesesse.com/blog/google-i-o-2026-what-the-2025-analytical-map-left-blank</loc>
    <news:news>
      <news:publication>
        <news:name>Matthieu Pesesse Blog</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-05-27T08:00:00+00:00</news:publication_date>
      <news:title>Google I/O 2026: What the 2025 Analytical Map Left Blank</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://matthieupesesse.com/blog/google-i-o-2026-ce-que-la-carte-analytique-de-2025-navait-pas-trace</loc>
    <news:news>
      <news:publication>
        <news:name>Matthieu Pesesse Blog</news:name>
        <news:language>fr</news:language>
      </news:publication>
      <news:publication_date>2026-05-27T08:00:00+00:00</news:publication_date>
      <news:title>Google I/O 2026 : ce que la carte analytique de 2025 n&apos;avait pas tracé</news:title>
    </news:news>
  </url>
  <url>
    <loc>https://matthieupesesse.com/blog/google-i-o-2026-wat-de-analytische-kaart-van-2025-niet-had-ingetekend</loc>
    <news:news>
      <news:publication>
        <news:name>Matthieu Pesesse Blog</news:name>
        <news:language>nl</news:language>
      </news:publication>
      <news:publication_date>2026-05-27T08:00:00+00:00</news:publication_date>
      <news:title>Google I/O 2026: wat de analytische kaart van 2025 niet had ingetekend</news:title>
    </news:news>
  </url>
</urlset>
