<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tingvar build log</title>
    <link>https://tingvar.com/changelog</link>
    <description>Every change Tingvar ships, dated, with regressions and known issues in the same feed as the additions.</description>
    <language>en-GB</language>
    <lastBuildDate>Fri, 04 Sept 2026 09:00:00 +0000</lastBuildDate>
    <atom:link href="https://tingvar.com/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Added: The price set is published and the free tier is withdrawn</title>
      <link>https://tingvar.com/changelog#price-set-published</link>
      <guid isPermaLink="true">https://tingvar.com/changelog#price-set-published</guid>
      <pubDate>Fri, 04 Sept 2026 09:00:00 +0000</pubDate>
      <description>Professional and Team now carry a published monthly figure in US dollars, taken from the approved plan catalogue, and an Enterprise tier is priced per company. The free tier is withdrawn. In its place every plan carries the Pitch-Ready guarantee: end your first session inside the published window and the payment is refunded in full. The statutory withdrawal right in the UK and the EEA is separate from that guarantee and is unaffected by it.</description>
      <category>site</category>
    </item>
    <item>
      <title>Fixed: The registered entity details are published</title>
      <link>https://tingvar.com/changelog#legal-identity-published</link>
      <guid isPermaLink="true">https://tingvar.com/changelog#legal-identity-published</guid>
      <pubDate>Fri, 04 Sept 2026 09:00:00 +0000</pubDate>
      <description>The entity name, the company registration number, the jurisdiction, the governing law, the data protection contact and the minimum age are all resolved and render wherever they belong. The placeholder mechanism that stood in for them is gone from every page, and the production build no longer fails on any of them. This closes the known issue logged in August. The registered office address is deliberately published as an online company rather than a street address, and will be updated when a registered office exists.</description>
      <category>site</category>
    </item>
    <item>
      <title>Removed: An unmeasured voice to voice latency target has been withdrawn</title>
      <link>https://tingvar.com/changelog#latency-target-withdrawn</link>
      <guid isPermaLink="true">https://tingvar.com/changelog#latency-target-withdrawn</guid>
      <pubDate>Mon, 24 Aug 2026 09:00:00 +0000</pubDate>
      <description>The earlier figure came from vendor documentation and was never measured against a running room. It is gone from every surface and the measured value replaces it. A target read out as though it were a measurement is the failure this site is meant to be the opposite of, and it was ours before it was anybody else&apos;s.</description>
      <category>web</category>
      <category>site</category>
    </item>
    <item>
      <title>Added: Every figure and every answer on the site now resolves from a register</title>
      <link>https://tingvar.com/changelog#registers-published</link>
      <guid isPermaLink="true">https://tingvar.com/changelog#registers-published</guid>
      <pubDate>Mon, 24 Aug 2026 09:00:00 +0000</pubDate>
      <description>The facts, questions, glossary, redirect and pending registers went in together. A page names a node and renders what comes back, so a figure here and the same figure in the machine readable copy of the page are one node and cannot drift apart. A page that states a number the register does not carry fails the build.</description>
      <category>site</category>
    </item>
    <item>
      <title>Known issue: The registered entity details are not published yet</title>
      <link>https://tingvar.com/changelog#legal-identity-outstanding</link>
      <guid isPermaLink="true">https://tingvar.com/changelog#legal-identity-outstanding</guid>
      <pubDate>Mon, 24 Aug 2026 09:00:00 +0000</pubDate>
      <description>The entity name, the company registration number and the registered address are outstanding. Every place they belong renders a visibly labelled placeholder rather than a guess, and a production build fails while any of them is unresolved. The about page is written for the resolved state and will carry the details the day they land.</description>
      <category>site</category>
    </item>
    <item>
      <title>Known issue: Session audio and transcripts are processed in the United States only</title>
      <link>https://tingvar.com/changelog#no-eu-processing-region</link>
      <guid isPermaLink="true">https://tingvar.com/changelog#no-eu-processing-region</guid>
      <pubDate>Mon, 24 Aug 2026 09:00:00 +0000</pubDate>
      <description>There is no processing region inside the European Economic Area and there is no way to ask for one. For a customer in the United Kingdom or the European Union that is a transfer out of the region, covered by Standard Contractual Clauses and the data processing agreement. If your procurement requires local residency we cannot meet it today, and we would rather you knew that before you bought.</description>
      <category>web</category>
      <category>site</category>
    </item>
    <item>
      <title>Added: The decision layer test result is published with its coverage</title>
      <link>https://tingvar.com/changelog#decision-layer-suite</link>
      <guid isPermaLink="true">https://tingvar.com/changelog#decision-layer-suite</guid>
      <pubDate>Sun, 23 Aug 2026 09:00:00 +0000</pubDate>
      <description>The turn taking policy, the bid scoring and the configuration guards are built and verified, and the suite result is on the evidence page with the date it was taken. The suite does not cover the client application, which is not started, and the evidence page says that in the row above the figure rather than in a footnote.</description>
      <category>web</category>
    </item>
    <item>
      <title>Added: The four persona voice samples are published, and labelled for what they are</title>
      <link>https://tingvar.com/changelog#persona-voice-samples</link>
      <guid isPermaLink="true">https://tingvar.com/changelog#persona-voice-samples</guid>
      <pubDate>Sun, 23 Aug 2026 09:00:00 +0000</pubDate>
      <description>Each sample is rendered with the same voice the product uses for that persona, so the voice is real. The words are scripted and every player says so beside the control. No sample is presented as a recording of a session, because no session has been recorded.</description>
      <category>site</category>
    </item>
    <item>
      <title>Known issue: No real human session has taken place, and every measured turn used pre-rendered audio</title>
      <link>https://tingvar.com/changelog#no-real-sessions</link>
      <guid isPermaLink="true">https://tingvar.com/changelog#no-real-sessions</guid>
      <pubDate>Wed, 19 Aug 2026 09:00:00 +0000</pubDate>
      <description>Everything measured so far is a measurement of the machine and not of a conversation. Nothing on this site is a recording of a session, and the one demonstration on the home page is a labelled reconstruction. The first real session will be published in full, with consent and with its redaction log, when there is one.</description>
      <category>web</category>
    </item>
    <item>
      <title>Changed: Voice to voice latency is now a measurement rather than a target</title>
      <link>https://tingvar.com/changelog#voice-to-voice-measured</link>
      <guid isPermaLink="true">https://tingvar.com/changelog#voice-to-voice-measured</guid>
      <pubDate>Wed, 19 Aug 2026 09:00:00 +0000</pubDate>
      <description>One run against a real media server produced the median, the ninety fifth and the ninety ninth percentile, with a stage by stage breakdown. More than half of the median is the model generating speech. The figure is published with its method everywhere it appears, and it is a floor to defend rather than headroom to spend.</description>
      <category>web</category>
      <category>site</category>
    </item>
  </channel>
</rss>
