<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="files/feed.css"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:ctrm="https://ctrmforbulkliquids.com/ns/feed">
<channel>
  <ctrm:help>
    <ctrm:h>Errata &amp; Updates feed</ctrm:h>
    <ctrm:p>This page is a feed: a list of the entries on the Errata &amp; Updates page at ctrmforbulkliquids.com/errata, in a form that feed readers can check for you. You don't need it to read the entries. A feed reader shows you new entries as they are posted.</ctrm:p>
    <ctrm:h2>To follow it, add the site to a feed reader:</ctrm:h2>
    <ctrm:li><ctrm:b>Feedly</ctrm:b> or <ctrm:b>Inoreader</ctrm:b> (web, iPhone, Android): use the reader's Add or Follow option and paste ctrmforbulkliquids.com. Choose "CTRM for Bulk Liquids: Errata &amp; Updates" if it asks.</ctrm:li>
    <ctrm:li><ctrm:b>NetNewsWire</ctrm:b> (Mac, iPhone, iPad; free): choose File &gt; New Feed and paste ctrmforbulkliquids.com.</ctrm:li>
    <ctrm:li><ctrm:b>Outlook</ctrm:b> (classic Outlook for Windows only): right-click RSS Feeds in the folder list, choose Add a New RSS Feed, and paste https://ctrmforbulkliquids.com/feed.xml.</ctrm:li>
    <ctrm:li><ctrm:b>Other feed readers:</ctrm:b> paste ctrmforbulkliquids.com, or the full address above if the reader asks for it.</ctrm:li>
    <ctrm:h2>Entries, newest first</ctrm:h2>
    <ctrm:note>The full entries, with search and filters, are on the Errata &amp; Updates page at ctrmforbulkliquids.com/errata.</ctrm:note>
  </ctrm:help>
  <title>CTRM for Bulk Liquids: Errata &amp; Updates</title>
  <link>https://ctrmforbulkliquids.com/errata</link>
  <atom:link href="https://ctrmforbulkliquids.com/feed.xml" rel="self" type="application/rss+xml"/>
  <description>Corrections to the printed text of CTRM for Bulk Liquids, clarifications, dated notes on what has changed since the text was fixed, and supplements the printed book does not contain.</description>
  <language>en-us</language>
  <copyright>Copyright 2026 Kent B. Landrum</copyright>
  <lastBuildDate>Sat, 31 Oct 2026 12:00:00 +0000</lastBuildDate>
  <item>
    <title>Update U-0002: Chapter 10, Vendor diligence and contractual terms (Exhibit 10.6)</title>
    <link>https://ctrmforbulkliquids.com/errata#U-0002</link>
    <guid isPermaLink="true">https://ctrmforbulkliquids.com/errata#U-0002</guid>
    <pubDate>Sat, 31 Oct 2026 12:00:00 +0000</pubDate>
    <category>Update</category>
    <description>&lt;p&gt;Most CTRM and ETRM agreements in force today were signed before vendors began shipping AI features, and they say nothing about them. Those features are now arriving through ordinary product releases, generally at no added charge for the time being. With terms of three to five years, a buyer may reach its next renewal after years of use without having established what the features are worth, while the vendor will know what they cost to run and how heavily each customer uses them. The renewal row in the contract terms checklist (Exhibit 10.6) covers renewal terms and price escalation; it does not address capabilities added during the term. The author's August 2026 article suggests keeping a record from the start: what arrived and in which release, how heavily it is used and how well it performs, what would be lost without it, and what the alternatives would cost. The last two set a floor and a ceiling on the capability's value, which gives the buyer a position to negotiate from at renewal.&lt;/p&gt;&lt;p&gt;&lt;a href="https://www.linkedin.com/pulse/what-worth-valuing-embedded-ai-before-your-ctrm-renewal-kent-landrum-mhnoc/"&gt;Read the article&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Applies to: Hardcover; Paperback; Kindle.&lt;/p&gt;&lt;p&gt;Author.&lt;/p&gt;</description>
    <ctrm:date>October 31, 2026</ctrm:date>
    <ctrm:summary>Most CTRM and ETRM agreements in force today were signed before vendors began shipping AI features, and they say nothing about them. Those features are now arriving through ordinary product releases, generally at no added charge for the time being. With terms of three to five years, a buyer may...</ctrm:summary>
  </item>
  <item>
    <title>Update U-0001: Chapter 19, The orchestration layer and the boundary of the system of record (Exhibit 19.4)</title>
    <link>https://ctrmforbulkliquids.com/errata#U-0001</link>
    <guid isPermaLink="true">https://ctrmforbulkliquids.com/errata#U-0001</guid>
    <pubDate>Sat, 31 Oct 2026 12:00:00 +0000</pubDate>
    <category>Update</category>
    <description>&lt;p&gt;Since the text was fixed, more CTRM and ETRM vendors have been adding AI features through routine product releases, and usage-based pricing for those features has become more common. Chapter 19 compares AI embedded in the CTRM with an orchestration layer above it (Exhibit 19.4). Embedded AI raises a cost question the chapter does not take up. The invoices reconcile to the contracts, but they cannot be broken down by business function, so finance and technology can confirm the amount without being able to judge whether it was worth paying. Because the features arrive in ordinary releases, they can also bypass procurement review, as the chapter notes. The author's September 2026 article on the subject recommends starting with attribution: list the AI capabilities in use, including those embedded in vendor releases; measure what each consumes; report that use by business function without moving budget, a practice known as showback; and take that record into the next renewal.&lt;/p&gt;&lt;p&gt;&lt;a href="https://www.jdsupra.com/legalnews/nobody-can-read-the-bill-ai-spend-in-9126434/"&gt;Read the article&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Applies to: Hardcover; Paperback; Kindle.&lt;/p&gt;&lt;p&gt;Author.&lt;/p&gt;</description>
    <ctrm:date>October 31, 2026</ctrm:date>
    <ctrm:summary>Since the text was fixed, more CTRM and ETRM vendors have been adding AI features through routine product releases, and usage-based pricing for those features has become more common. Chapter 19 compares AI embedded in the CTRM with an orchestration layer above it (Exhibit 19.4). Embedded AI raises...</ctrm:summary>
  </item>
  <item>
    <title>Erratum E-0003: Back matter, Glossary: RIN</title>
    <link>https://ctrmforbulkliquids.com/errata#E-0003</link>
    <guid isPermaLink="true">https://ctrmforbulkliquids.com/errata#E-0003</guid>
    <pubDate>Fri, 30 Oct 2026 12:00:00 +0000</pubDate>
    <category>Erratum</category>
    <description>&lt;p&gt;&lt;b&gt;Was:&lt;/b&gt; A unique 38-digit number assigned to each gallon of renewable fuel produced or imported under the U.S. Renewable Fuel Standard.&lt;br&gt;&lt;b&gt;Should read:&lt;/b&gt; A unique 38-digit number generated for renewable fuel produced or imported under the U.S. Renewable Fuel Standard. The number of RINs per gallon follows the fuel's equivalence value, which reflects its energy content relative to ethanol: a gallon of ethanol generates one RIN, and a gallon of biodiesel or renewable diesel generates more than one.&lt;/p&gt;&lt;p&gt;The printed entry describes the ethanol case. Fuels with higher energy content generate more than one RIN per gallon, which affects RIN position and obligation calculations in the CTRM. Chapter 16 is not affected.&lt;/p&gt;&lt;p&gt;Not yet applied in any format.&lt;/p&gt;&lt;p&gt;Applies to: Hardcover; Paperback; Kindle.&lt;/p&gt;&lt;p&gt;Author.&lt;/p&gt;</description>
    <ctrm:date>October 30, 2026</ctrm:date>
    <ctrm:summary>The printed entry describes the ethanol case. Fuels with higher energy content generate more than one RIN per gallon, which affects RIN position and obligation calculations in the CTRM. Chapter 16 is not affected.</ctrm:summary>
  </item>
  <item>
    <title>Erratum E-0002: Back matter, Glossary: Chicago Mercantile Exchange (CME)</title>
    <link>https://ctrmforbulkliquids.com/errata#E-0002</link>
    <guid isPermaLink="true">https://ctrmforbulkliquids.com/errata#E-0002</guid>
    <pubDate>Fri, 30 Oct 2026 12:00:00 +0000</pubDate>
    <category>Erratum</category>
    <description>&lt;p&gt;&lt;b&gt;Was:&lt;/b&gt; A primary U.S. derivatives exchange on which crude oil, refined products, and other commodity futures and options are traded. CME settlement prices are widely referenced in physical commodity contracts…&lt;br&gt;&lt;b&gt;Should read:&lt;/b&gt; A primary U.S. derivatives exchange and part of CME Group, whose New York Mercantile Exchange (NYMEX) lists the principal crude oil and refined products futures and options. CME Group settlement prices are widely referenced in physical commodity contracts…&lt;/p&gt;&lt;p&gt;Crude oil and refined products futures trade on NYMEX, which CME Group owns, as the Glossary's NYMEX entry states. The printed entry placed them on the Chicago Mercantile Exchange itself.&lt;/p&gt;&lt;p&gt;Not yet applied in any format.&lt;/p&gt;&lt;p&gt;Applies to: Hardcover; Paperback; Kindle.&lt;/p&gt;&lt;p&gt;Author.&lt;/p&gt;</description>
    <ctrm:date>October 30, 2026</ctrm:date>
    <ctrm:summary>Crude oil and refined products futures trade on NYMEX, which CME Group owns, as the Glossary's NYMEX entry states. The printed entry placed them on the Chicago Mercantile Exchange itself.</ctrm:summary>
  </item>
  <item>
    <title>Erratum E-0001: Back matter, Glossary: SOC 2</title>
    <link>https://ctrmforbulkliquids.com/errata#E-0001</link>
    <guid isPermaLink="true">https://ctrmforbulkliquids.com/errata#E-0001</guid>
    <pubDate>Fri, 30 Oct 2026 12:00:00 +0000</pubDate>
    <category>Erratum</category>
    <description>&lt;p&gt;&lt;b&gt;Was:&lt;/b&gt; SOC 2. Service Organization Control 2. A reporting framework administered under the AICPA's Trust Services Criteria…&lt;br&gt;&lt;b&gt;Should read:&lt;/b&gt; SOC 2. System and Organization Controls 2. A reporting framework administered under the AICPA's Trust Services Criteria…&lt;/p&gt;&lt;p&gt;The AICPA renamed its SOC reports from Service Organization Control to System and Organization Controls in 2017. The rest of the entry is unchanged.&lt;/p&gt;&lt;p&gt;Not yet applied in any format.&lt;/p&gt;&lt;p&gt;Applies to: Hardcover; Paperback; Kindle.&lt;/p&gt;&lt;p&gt;Author.&lt;/p&gt;</description>
    <ctrm:date>October 30, 2026</ctrm:date>
    <ctrm:summary>The AICPA renamed its SOC reports from Service Organization Control to System and Organization Controls in 2017. The rest of the entry is unchanged.</ctrm:summary>
  </item>
</channel>
</rss>
