<?xml version="1.0" encoding="UTF-8"?>
<!--
  Every page on the site, and nothing that is not a page. Eight documents: the
  front door, one per audience, the two deep references, and the two legal
  pages. The sections inside each one are anchors and are deliberately not
  listed, because naming an anchor here asks a crawler to index the same page
  several times.

  The front door is now the application's own document, served with the whole
  offer in its markup and enhanced into the live example by the WebAssembly for
  a reader who runs it; see web/static/index.html. Its entry below is unchanged
  because its URL is unchanged, which is the point of the arrangement. The seven
  pages under it are the long versions and are not folded into it: the app
  shaped home was added, the deep content was not thrown away, and every one of
  these is linked from that document's own header or footer.

  /app/ is deliberately absent. It is the same document under a second URL, and
  asking for it to be indexed beside the canonical one would be asking for the
  front door to be indexed twice; robots.txt closes it for the same reason.

  The marketing tree no longer carries a front page of its own. It had one for
  as long as / was a static document, and keeping it after the application took
  that address left a second, unlinked statement of the same offer at
  /index.html for a crawler to find and for somebody to have to keep true. It
  was removed rather than redirected: nothing on the site linked it, it was
  never in this file, and its canonical already named the page below.

  /llms.txt is not listed. It is the machine readable brief for AI agents rather
  than a page for a search result, and it is announced where an agent will
  actually look for it, in a `<link rel="alternate">` on every page and in a
  block of its own in robots.txt.

  `lastmod` is edited by hand when the copy changes rather than stamped by the
  build, because a rebuild that changed nothing should not claim the page is new.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://verigrant.com/</loc>
    <lastmod>2026-09-12</lastmod>
    <changefreq>monthly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://verigrant.com/job-seekers.html</loc>
    <lastmod>2026-09-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://verigrant.com/employers.html</loc>
    <lastmod>2026-09-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://verigrant.com/agents.html</loc>
    <lastmod>2026-09-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://verigrant.com/for-agents.html</loc>
    <lastmod>2026-09-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://verigrant.com/security.html</loc>
    <lastmod>2026-09-02</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
  </url>
  <!--
    The two legal pages. `lastmod` is their effective date rather than the day
    the file was edited, because for these two documents those are the same
    claim: a change to the wording is a new version with a new effective date,
    and the consent records that name a version have to be able to point at the
    document that was actually shown.
  -->
  <url>
    <loc>https://verigrant.com/terms.html</loc>
    <lastmod>2026-09-08</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.4</priority>
  </url>
  <url>
    <loc>https://verigrant.com/privacy.html</loc>
    <lastmod>2026-09-08</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.4</priority>
  </url>
</urlset>
