<?xml version="1.0" encoding="UTF-8"?>
<!--
  SITEMAP.XML - Zamski marketing site

  Maintenance: manually maintained. Mirror against routes.marketing.tsx
  any time a new public-facing route is added or retired.

  2026-08-02 update: investor-primary positioning per founder rulings.
  Added /diligence at Tier 1 and /pre-close-finding at Tier 2 for the
  new investor funnel. The named proof route was cancelled 2026-08-02
  pass 2 per founder ruling F1; the site carries the pattern instead
  of naming any case, and named stories stay in outbound only.

  2026-06-06 rewrite: ground-up rebuild after the executive-intelligence
  positioning rebrand. All previous entries pointed at retired routes
  (/features, /signals, /agent, /mcp, /arcs, /vs/*, /alternatives,
  /why-zamski) which now redirect to /. Including them in the sitemap
  was wasting crawl budget and pointing search engines at 301s.

  Routes intentionally excluded:
  - /report/:owner/:repo  (per-prospect preview surface; internal use)
  - /apply, /signup        (workflow endpoints; thin content)
  - /findings/microsoft/vscode and /golang/go (analyzed but low signal
    count; can re-add later if substantive)
  - Marketing-asset routes (/marketing/screenshot, screenshots/*)
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">

  <!-- ═════════════════════════════════════════════════════════════════
       TIER 1: Critical conversion + entry pages (priority 1.0 - 0.9)
       ═════════════════════════════════════════════════════════════════ -->

  <!-- Homepage. lastmod bumped 2026-08-03 pass 5 P4 after the Why
       columns rewrote and the SampleBriefSection label stack changed. -->
  <url>
    <loc>https://www.zamski.com/</loc>
    <lastmod>2026-08-03</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>

  <!-- Diligence (investor-primary landing, added 2026-08-02) -->
  <url>
    <loc>https://www.zamski.com/diligence</loc>
    <lastmod>2026-08-02</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.95</priority>
  </url>

  <!-- The Pre-Close Finding (investor conversion path, added 2026-08-02) -->
  <url>
    <loc>https://www.zamski.com/pre-close-finding</loc>
    <lastmod>2026-08-02</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.9</priority>
  </url>

  <!-- The 30-Day Finding (own-org conversion path) -->
  <url>
    <loc>https://www.zamski.com/30-day-finding</loc>
    <lastmod>2026-08-02</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.85</priority>
  </url>

  <!-- Public-repo findings index -->
  <url>
    <loc>https://www.zamski.com/findings</loc>
    <lastmod>2026-06-06</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>

  <!-- ═════════════════════════════════════════════════════════════════
       TIER 2: Public-repo finding pages (priority 0.8)
       Each is a substantive analysis of a real open-source repository.
       ═════════════════════════════════════════════════════════════════ -->

  <url>
    <loc>https://www.zamski.com/findings/facebook/react</loc>
    <lastmod>2026-06-06</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>

  <url>
    <loc>https://www.zamski.com/findings/vercel/next.js</loc>
    <lastmod>2026-06-06</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>

  <url>
    <loc>https://www.zamski.com/findings/kubernetes/kubernetes</loc>
    <lastmod>2026-06-06</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>

  <!-- ═════════════════════════════════════════════════════════════════
       TIER 3: Company + contact (priority 0.7)
       ═════════════════════════════════════════════════════════════════ -->

  <url>
    <loc>https://www.zamski.com/about</loc>
    <lastmod>2026-08-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
  </url>

  <url>
    <loc>https://www.zamski.com/government</loc>
    <lastmod>2026-08-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
  </url>

  <url>
    <loc>https://www.zamski.com/contact</loc>
    <lastmod>2026-06-06</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
  </url>

  <!-- FAQ. Added 2026-08-02 pass 2 (F5): rendered content now mirrors
       the FAQPage JSON-LD schema in index.marketing.html and the
       investor section carries the four canonical Q&A pairs.
       Priority bumped to 0.7 on 2026-08-03 pass 3 A2. -->
  <url>
    <loc>https://www.zamski.com/faq</loc>
    <lastmod>2026-08-03</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
  </url>

  <!-- ═════════════════════════════════════════════════════════════════
       TIER 4: Authority + AI-citation pages (priority 0.7 - 0.6)
       Method notes, samples, integrations. Canonical source AI answer
       engines (ChatGPT, Claude.ai, Perplexity) cite when readers ask
       about the method, sample reports, or connector coverage.
       ═════════════════════════════════════════════════════════════════ -->

  <url>
    <loc>https://www.zamski.com/methodology</loc>
    <lastmod>2026-08-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.75</priority>
  </url>

  <!-- /samples lastmod bumped 2026-08-03 pass 4 P5. Hero sub-line
       added (P1) and return CTA switched to the dual pattern (P2). -->
  <url>
    <loc>https://www.zamski.com/samples</loc>
    <lastmod>2026-08-03</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.75</priority>
  </url>

  <url>
    <loc>https://www.zamski.com/integrations</loc>
    <lastmod>2026-08-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
  </url>

  <url>
    <loc>https://www.zamski.com/glossary</loc>
    <lastmod>2026-08-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.5</priority>
  </url>

  <!-- /comparison intentionally omitted while at design-partner stage.
       Page lives at /comparison and is reachable by direct URL for
       procurement responses, but is noindexed and unlisted here so
       crawlers + AI engines skip it. Re-add this entry when there is
       a named customer logo to defend the public positioning. -->

  <!-- ═════════════════════════════════════════════════════════════════
       TIER 5: Legal + trust (priority 0.5 - 0.3)
       ═════════════════════════════════════════════════════════════════ -->

  <url>
    <loc>https://www.zamski.com/security</loc>
    <lastmod>2026-06-06</lastmod>
    <changefreq>quarterly</changefreq>
    <priority>0.5</priority>
  </url>

  <url>
    <loc>https://www.zamski.com/privacy</loc>
    <lastmod>2026-06-06</lastmod>
    <changefreq>quarterly</changefreq>
    <priority>0.4</priority>
  </url>

  <url>
    <loc>https://www.zamski.com/terms</loc>
    <lastmod>2026-06-06</lastmod>
    <changefreq>quarterly</changefreq>
    <priority>0.3</priority>
  </url>

  <url>
    <loc>https://www.zamski.com/cookies</loc>
    <lastmod>2026-06-06</lastmod>
    <changefreq>quarterly</changefreq>
    <priority>0.3</priority>
  </url>

</urlset>
