<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:video="http://www.google.com/schemas/sitemap-video/1.1">
  <url><loc>https://hapax.fi/</loc></url>
  <url><loc>https://hapax.fi/advisory.html</loc></url>
  <url><loc>https://hapax.fi/training.html</loc></url>
  <url><loc>https://hapax.fi/counsel.html</loc></url>
  <url><loc>https://hapax.fi/notes.html</loc></url>
  <url><loc>https://hapax.fi/note-anthropic-books.html</loc></url>
  <url><loc>https://hapax.fi/note-staff-ai-rules.html</loc></url>
  <url><loc>https://hapax.fi/note-eu-data.html</loc></url>
  <url><loc>https://hapax.fi/trust.html</loc></url>
  <url><loc>https://hapax.fi/work.html</loc></url>
  <url><loc>https://hapax.fi/shapes.html</loc></url>
  <url><loc>https://hapax.fi/uncertainty.html</loc></url>
  <url><loc>https://hapax.fi/case-erp-cleanup.html</loc></url>
  <url><loc>https://hapax.fi/case-invoices.html</loc></url>
  <url><loc>https://hapax.fi/case-contracts.html</loc></url>
  <url><loc>https://hapax.fi/case-board-reporting.html</loc></url>
  <url><loc>https://hapax.fi/case-anomaly-detection.html</loc></url>
  <url><loc>https://hapax.fi/case-churn.html</loc></url>
  <url><loc>https://hapax.fi/case-tenders.html</loc></url>
  <url><loc>https://hapax.fi/case-inbox.html</loc></url>
  <url><loc>https://hapax.fi/case-training-outcomes.html</loc></url>
  <url><loc>https://hapax.fi/case-talent-screening.html</loc></url>
  <url><loc>https://hapax.fi/case-skills-library.html</loc></url>
  <url>
    <loc>https://hapax.fi/film-erp-cleanup.html</loc>
    <video:video>
      <video:thumbnail_loc>https://hapax.fi/films/case-erp-cleanup.poster.jpg</video:thumbnail_loc>
      <video:title>The automation that retires itself</video:title>
      <video:description>On 240 fabricated month-end reports from a fictional SAP system, with every correct value recorded in advance, a language model parsed each one while a second system learned the repeating formats and wrote ordinary code for them. 184 of 240 ended up on that code, at an estimated two fifths of the cost.</video:description>
      <video:content_loc>https://hapax.fi/films/case-erp-cleanup.mp4</video:content_loc>
      <video:duration>96</video:duration>
      <video:publication_date>2026-10-07</video:publication_date>
    </video:video>
  </url>
  <url>
    <loc>https://hapax.fi/film-board-reporting.html</loc>
    <video:video>
      <video:thumbnail_loc>https://hapax.fi/films/case-board-reporting.poster.jpg</video:thumbnail_loc>
      <video:title>The board pack that answers back</video:title>
      <video:description>Two years of fabricated monthly financials for a fictional Nordic manufacturer, with four scenarios hidden in the data and the correct findings written first. Three independent AI analyses found all four, with no false positives and no wrong figures across thirty findings. The strongest evidence in one scenario went unexamined.</video:description>
      <video:content_loc>https://hapax.fi/films/case-board-reporting.mp4</video:content_loc>
      <video:duration>120</video:duration>
      <video:publication_date>2026-10-07</video:publication_date>
    </video:video>
  </url>
  <url>
    <loc>https://hapax.fi/film-anomaly-detection.html</loc>
    <video:video>
      <video:thumbnail_loc>https://hapax.fi/films/case-anomaly-detection.poster.jpg</video:thumbnail_loc>
      <video:title>The anomaly nobody caught</video:title>
      <video:description>We built a 50,000-row purchase ledger, hid 87 irregularities in it, and screened it three ways. Rule-based checks caught 48. A statistical anomaly detector caught none. The slow vendor price drift at the centre of the design was missed by every layer. A follow-up report catches three freshly planted drifts on new data but cannot see the vendor that prompted it.</video:description>
      <video:content_loc>https://hapax.fi/films/case-anomaly-detection.mp4</video:content_loc>
      <video:duration>121</video:duration>
      <video:publication_date>2026-10-07</video:publication_date>
    </video:video>
  </url>
  <url>
    <loc>https://hapax.fi/film-tenders.html</loc>
    <video:video>
      <video:thumbnail_loc>https://hapax.fi/films/case-tenders.poster.jpg</video:thumbnail_loc>
      <video:title>Sixteen tenders, answered two ways</video:title>
      <video:description>Sixteen invented tenders and 510 requirements, answered two ways. Fourteen simulated people with a chatbot produced per-tender medians from 64.3% to 93.3%. A workflow run once per tender answered every requirement on 11 of 14 and refused both tenders the firm cannot win. The only three requirements nobody found were mandatory forms mentioned once inside an annex.</video:description>
      <video:content_loc>https://hapax.fi/films/case-tenders.mp4</video:content_loc>
      <video:duration>114</video:duration>
      <video:publication_date>2026-10-08</video:publication_date>
    </video:video>
  </url>
  <url>
    <loc>https://hapax.fi/film-churn.html</loc>
    <video:video>
      <video:thumbnail_loc>https://hapax.fi/films/case-churn.poster.jpg</video:thumbnail_loc>
      <video:title>The churn a usage model can’t see</video:title>
      <video:description>On 500 fabricated accounts with 3,777 support tickets and a known answer key, a usage model catches the accounts whose logins drop before they cancel. A language model reads the tickets, finds nine more genuine churners in the top hundred, and adds €1.14M in annual revenue the usage data misses.</video:description>
      <video:content_loc>https://hapax.fi/films/case-churn.mp4</video:content_loc>
      <video:duration>117</video:duration>
      <video:publication_date>2026-10-08</video:publication_date>
    </video:video>
  </url>
  <url>
    <loc>https://hapax.fi/film-inbox.html</loc>
    <video:video>
      <video:thumbnail_loc>https://hapax.fi/films/case-inbox.poster.jpg</video:thumbnail_loc>
      <video:title>One hundred and fifty emails, three gates</video:title>
      <video:description>An invented equipment-rental firm in Oulu, a 30-clause policy handbook and 150 synthetic customer emails. A pipeline classifies each one, drafts a reply with clause citations, checks the draft against three rules and routes the result. 122 were sent automatically without a single rule violation. All seven safety and data-request emails were escalated. Six emails asking for more information were misclassified as routine. Three of six expectations were met.</video:description>
      <video:content_loc>https://hapax.fi/films/case-inbox.mp4</video:content_loc>
      <video:duration>84</video:duration>
      <video:publication_date>2026-10-08</video:publication_date>
    </video:video>
  </url>
  <url>
    <loc>https://hapax.fi/film-training-outcomes.html</loc>
    <video:video>
      <video:thumbnail_loc>https://hapax.fi/films/case-training-outcomes.poster.jpg</video:thumbnail_loc>
      <video:title>Forty learners, three instruments</video:title>
      <video:description>Forty simulated learners sat a two-day programme with their true improvement set beforehand. The assessment recovered the overall learning effect to within 0.01 of the planted 0.13 and caught six of the seven people whose confidence rose while their competence did not. The industry-standard feedback form correlated with real learning at r = 0.10. A 94%-reliable scorer flips two of six verdicts. The cohort is simulated, so what is tested is the instrument, not the training.</video:description>
      <video:content_loc>https://hapax.fi/films/case-training-outcomes.mp4</video:content_loc>
      <video:duration>97</video:duration>
      <video:publication_date>2026-10-08</video:publication_date>
    </video:video>
  </url>
  <url>
    <loc>https://hapax.fi/film-talent-screening.html</loc>
    <video:video>
      <video:thumbnail_loc>https://hapax.fi/films/case-talent-screening.poster.jpg</video:thumbnail_loc>
      <video:title>Two hundred and forty applications, screened four ways</video:title>
      <video:description>240 synthetic applications for a signal-processing role at a fictional instruments maker in Oulu, screened four ways and checked against an answer key no screening arm could see. A workflow read every application against twelve requirements and returned evidence dossiers with verbatim quotes but no ranking or verdict. It caught 14 of 15 credential inflations and identified 19 of 22 keyword stuffers. Four of ten predictions were met.</video:description>
      <video:content_loc>https://hapax.fi/films/case-talent-screening.mp4</video:content_loc>
      <video:duration>116</video:duration>
      <video:publication_date>2026-10-08</video:publication_date>
    </video:video>
  </url>
  <url>
    <loc>https://hapax.fi/film-skills-library.html</loc>
    <video:video>
      <video:thumbnail_loc>https://hapax.fi/films/case-skills-library.poster.jpg</video:thumbnail_loc>
      <video:title>Sixty questions, and what happens when you write the rules down</video:title>
      <video:description>Sixty requests to a fictional Finnish retailer, each with the correct answer written first and held out. Without written rules, an AI assistant scored 49.7%. With a single document of definitions and worked examples, 99.3%. A cheaper model with the rules scored 29 points above the main model without. Six of twelve predictions were met.</video:description>
      <video:content_loc>https://hapax.fi/films/case-skills-library.mp4</video:content_loc>
      <video:duration>104</video:duration>
      <video:publication_date>2026-10-16</video:publication_date>
    </video:video>
  </url>
</urlset>
