<?xml version="1.0" encoding="UTF-8"?>
<!--
  One URL is correct here, not a stub. PulseLMS has exactly one public,
  indexable, enumerable page: the landing page at "/".

  Deliberately excluded, so nobody "fixes" this by adding them back:
    /login       — thin, and duplicates the landing page's sign-in CTA.
    /verify/<serial> — public, but one URL per certificate serial; not
                   enumerable, and Disallowed in robots.txt.
    public catalog — exists only as an API endpoint (/api/public/v1/catalog,
                   which requires an ?org= alias). There is no SPA route
                   rendering it, so there is no page to list.
    everything else — requires sign-in. See public/robots.txt.

  /demo IS listed: it is public, has no side effects on GET (a sandbox is only
  leased by POSTing a persona choice), and is the page we most want a search or an
  AI assistant to send somebody to.

  /terms and /privacy are listed too: public, static, and the pages a search result
  or a prospective customer's legal review will look for by name.

  Add a <url> here the moment another genuinely public page ships (a pricing or
  features route, a per-org public catalog page, self-service signup).
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://learn.mypulsetech.com/</loc>
    <lastmod>2026-07-26</lastmod>
    <changefreq>monthly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://learn.mypulsetech.com/demo</loc>
    <lastmod>2026-07-26</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://learn.mypulsetech.com/terms</loc>
    <lastmod>2026-07-26</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
  <url>
    <loc>https://learn.mypulsetech.com/privacy</loc>
    <lastmod>2026-07-26</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
</urlset>
