<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Tiber River Consulting Blog</title>
  <link>https://tiberriverconsulting.com/blog/</link>
  <description>Notes on private AI for regulated professions: client confidentiality, on-premises architecture, and source-cited output.</description>
  <language>en-us</language>
  <lastBuildDate>Tue, 08 Sep 2026 12:00:00 GMT</lastBuildDate>
  <atom:link href="https://tiberriverconsulting.com/blog/rss.xml" rel="self" type="application/rss+xml"/>

  <item>
    <title>Why AI output should wait in an approval queue</title>
    <link>https://tiberriverconsulting.com/blog/ai-approval-queue/</link>
    <guid>https://tiberriverconsulting.com/blog/ai-approval-queue/</guid>
    <pubDate>Tue, 08 Sep 2026 12:00:00 GMT</pubDate>
    <description>Firms already run on sign-off, and most AI tools give that habit nowhere to live. What an approval queue entry has to carry, why chat-window review doesn't hold up, and what the accepted and rejected items leave behind.</description>
  </item>

  <item>
    <title>How to read an AI vendor's security page</title>
    <link>https://tiberriverconsulting.com/blog/ai-vendor-security-page/</link>
    <guid>https://tiberriverconsulting.com/blog/ai-vendor-security-page/</guid>
    <pubDate>Tue, 01 Sep 2026 12:00:00 GMT</pubDate>
    <description>A vendor security page is a sales document that still rewards careful reading. How law firms read one for scope instead of adjectives, the three specifics to hunt for, and why the page is never the contract.</description>
  </item>

  <item>
    <title>What "your files never leave the building" means, technically</title>
    <link>https://tiberriverconsulting.com/blog/files-never-leave-the-building/</link>
    <guid>https://tiberriverconsulting.com/blog/files-never-leave-the-building/</guid>
    <pubDate>Tue, 25 Aug 2026 12:00:00 GMT</pubDate>
    <description>A no-egress claim is only worth what your firm can verify. The three kinds of data that can leave an on-premises legal AI system, what the architecture has to do about each, and how to test the boundary from your own firewall.</description>
  </item>

  <item>
    <title>Private AI for law firms: why client files should stay in the building</title>
    <link>https://tiberriverconsulting.com/blog/private-ai-for-law-firms/</link>
    <guid>https://tiberriverconsulting.com/blog/private-ai-for-law-firms/</guid>
    <pubDate>Thu, 20 Aug 2026 12:00:00 GMT</pubDate>
    <description>Cloud AI asks law firms to send client files to someone else's servers. There is another way: private AI on hardware the firm owns, with citations, access controls, and an audit trail you can verify.</description>
  </item>

  <item>
    <title>The verification tax: the real reason lawyers don't trust AI</title>
    <link>https://tiberriverconsulting.com/blog/the-verification-tax/</link>
    <guid>https://tiberriverconsulting.com/blog/the-verification-tax/</guid>
    <pubDate>Thu, 20 Aug 2026 12:00:00 GMT</pubDate>
    <description>A confident AI answer you have to re-check line by line saves nothing. How source-linked output and honest refusals remove the verification tax that keeps law firms from adopting AI.</description>
  </item>

</channel>
</rss>
