<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:image="http://www.google.com/schemas/sitemap-image/1.1">
  <url>
    <loc>https://whyrep.com/</loc>
    <lastmod>2026-08-02</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
    <image:image>
      <image:loc>https://whyrep.com/assets/og-image-v2.png</image:loc>
    </image:image>
  </url>
  <!-- Added 2026-07-26 with the page itself. Indexable on purpose: a reachable, crawlable
       privacy policy is what both app stores check for at submission, and a policy nobody
       can find is worth less than one they can. priority/changefreq omitted deliberately,
       Google ignores both. -->
  <url>
    <loc>https://whyrep.com/privacy</loc>
    <lastmod>2026-08-06</lastmod>
  </url>
  <!-- Added 2026-08-01 with the page itself. Same reasoning as /privacy, and one step
       stronger: Google Play's User Data policy requires the account deletion route to be
       "prominently featured and easily discoverable", so it is indexed deliberately rather
       than tolerated. -->
  <url>
    <loc>https://whyrep.com/delete-account</loc>
    <lastmod>2026-08-01</lastmod>
  </url>
  <!-- The section lived at /guides/ from 2026-08-06 and was renamed to /blog/ on 2026-08-12.
       The three old URLs are 301ed in landing/_redirects rather than dropped, because they
       were already indexed. Only the new URLs are listed here: a sitemap advertising a
       redirecting URL asks Google to crawl a hop it does not need. -->
  <url>
    <loc>https://whyrep.com/blog/</loc>
    <lastmod>2026-08-12</lastmod>
  </url>
  <!-- Added 2026-08-12. Traced to progression-detection.md's Final Algorithm, "What gets
       compared", with Test Vectors 8 and 9 behind the substitution and the permanent baseline.
       This one SHIPS: the flag and the best-set substitution run in the live progression engine
       and the suggestion card is surfaced on a finished session. -->
  <url>
    <loc>https://whyrep.com/blog/when-your-second-set-beats-your-first/</loc>
    <lastmod>2026-08-12</lastmod>
  </url>
  <!-- Added 2026-08-12. Traced to progression-detection.md's "Approved regression reasons",
       reproduced in full, with Test Vectors 17 to 19 behind the deficit and sleep conditions.
       The rule is implemented and tested; nothing in the app populates its inputs, so the post
       states plainly that no reason is ever cited in the shipped build. -->
  <url>
    <loc>https://whyrep.com/blog/why-your-lift-went-down/</loc>
    <lastmod>2026-08-12</lastmod>
  </url>
  <!-- Added 2026-08-12. Traced to weekly-volume.md's Final Algorithm, sections 2 to 5, with
       Test Vectors behind every number. The doc is status:draft, which the 2026-08-06 per-claim
       ruling explicitly permits for Final Algorithm claims. The post states in its own body that
       the screen is not built yet, which is the separate "does it ship" test. -->
  <url>
    <loc>https://whyrep.com/blog/how-many-sets-per-muscle-per-week/</loc>
    <lastmod>2026-08-12</lastmod>
  </url>
  <!-- Added 2026-08-12. Traced to autoregulation-deloads.md's Deload Policy and Final Algorithm.
       Same draft/ship reasoning as above: the deload STANCE is settled and final, the detection
       described is not implemented, and the post says so rather than implying a shipped feature.
       The systemic-signal threshold is deliberately absent from the post, because the doc flags
       that number as not yet re-tuned, and a self-flagged number is the one thing the per-claim
       ruling forbids publishing. -->
  <url>
    <loc>https://whyrep.com/blog/why-whyrep-never-tells-you-to-deload/</loc>
    <lastmod>2026-08-12</lastmod>
  </url>
  <!-- Added 2026-08-07 at /guides/what-counts-as-progressive-overload/, moved 2026-08-12. Leads
       the progressive-overload cluster: Google Trends measures that term as several times larger
       than the plateau term the 2026-07-26 plan made the pillar. Traced to progression-detection.md's
       Final Algorithm. priority/changefreq omitted deliberately, Google ignores both. -->
  <url>
    <loc>https://whyrep.com/blog/what-counts-as-progressive-overload/</loc>
    <lastmod>2026-08-12</lastmod>
  </url>
  <!-- Added 2026-08-06 as the first page in the section, moved 2026-08-12. Reference content
       built from a signed methodology doc, per the 2026-08-06 per-claim citation ruling. -->
  <url>
    <loc>https://whyrep.com/blog/how-many-stalled-sessions-is-a-plateau/</loc>
    <lastmod>2026-08-12</lastmod>
  </url>
</urlset>
