<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Trisilva Insights</title>
    <link>https://trisilva.ai/insights</link>
    <description>Writing from the team building the platform: open standards, audit-clean operations, and the mechanics of running insurance on modern infrastructure.</description>
    <language>en</language>
    <atom:link href="https://trisilva.ai/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OPIN: carrying an open insurance standard forward, and authoring the profile each market needs.</title>
      <link>https://trisilva.ai/insights/opin-open-insurance-standard</link>
      <guid isPermaLink="true">https://trisilva.ai/insights/opin-open-insurance-standard</guid>
      <description>The standard is at v1.5.0-draft and Vietnam&apos;s profile sits on top of it at v0.2. What the standard settles, where it is still thin, and what an open licence does and does not protect an insurer from.</description>
      <category>White paper</category>
      <pubDate>Mon, 10 Aug 2026 02:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Closing Asia&apos;s insurance gaps: systems that were never built to meet.</title>
      <link>https://trisilva.ai/insights/closing-asias-insurance-gaps</link>
      <guid isPermaLink="true">https://trisilva.ai/insights/closing-asias-insurance-gaps</guid>
      <description>Three things stop insurers, their sales channels and their repair networks working as one system. Which ones costs most, which ones you cannot see, and what we have learned putting a claims operation live one insurer at a time.</description>
      <category>Post</category>
      <pubDate>Thu, 30 Jul 2026 02:00:00 GMT</pubDate>
    </item>
    <item>
      <title>From FNOL to settlement: the anatomy of a claim on ClaimFlow.</title>
      <link>https://trisilva.ai/insights/fnol-to-settlement-anatomy-of-a-claim</link>
      <guid isPermaLink="true">https://trisilva.ai/insights/fnol-to-settlement-anatomy-of-a-claim</guid>
      <description>One motor claim from first notice to settlement, with the nine service levels that decide who owes the next action and by when. Plus a plain statement of which parts run today and which are still architecture.</description>
      <category>Deep-dive</category>
      <pubDate>Tue, 21 Jul 2026 02:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Selling a policy where the customer already is: distribution mechanics on MicroFlow.</title>
      <link>https://trisilva.ai/insights/distribution-mechanics-on-microflow</link>
      <guid isPermaLink="true">https://trisilva.ai/insights/distribution-mechanics-on-microflow</guid>
      <description>How an embedded policy is issued inside a transaction, allocated to an insurer behind it, and reconciled afterwards across four regulators. The design of the engine, not a count of deployments.</description>
      <category>Deep-dive</category>
      <pubDate>Thu, 09 Jul 2026 02:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Audit-clean multi-tenancy: running many insurers on one backbone without mixing their data.</title>
      <link>https://trisilva.ai/insights/audit-clean-multi-tenancy</link>
      <guid isPermaLink="true">https://trisilva.ai/insights/audit-clean-multi-tenancy</guid>
      <description>Separation between insurers is a property of a design. Proving it to a regulator is a record. What each one requires, where data residency fits, and the read-side question a write-side audit trail does not answer.</description>
      <category>White paper</category>
      <pubDate>Thu, 02 Jul 2026 02:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Why we build AI-first, and what that rules out.</title>
      <link>https://trisilva.ai/insights/why-we-build-ai-first</link>
      <guid isPermaLink="true">https://trisilva.ai/insights/why-we-build-ai-first</guid>
      <description>A test for AI-first that a buyer can actually apply, what it rules out, and the place where our own product does yet pass.</description>
      <category>Post</category>
      <pubDate>Tue, 30 Jun 2026 02:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Outcome-based mechanics: pricing a claims operation on results, not seats.</title>
      <link>https://trisilva.ai/insights/outcome-based-mechanics</link>
      <guid isPermaLink="true">https://trisilva.ai/insights/outcome-based-mechanics</guid>
      <description>What an outcome has to contain before a fee can attach to it: the edge cases, the calendars, the attribution problem, and why we have not signed one of these yet.</description>
      <category>White paper</category>
      <pubDate>Wed, 24 Jun 2026 02:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The anti-corruption adapter: connecting to a legacy core without inheriting its model.</title>
      <link>https://trisilva.ai/insights/anti-corruption-adapter</link>
      <guid isPermaLink="true">https://trisilva.ai/insights/anti-corruption-adapter</guid>
      <description>Whose vocabulary wins at the boundary decides what every later integration costs. What the translation layer buys, what it costs every month afterwards, and the question that tells you whether a platform really holds the line.</description>
      <category>Post</category>
      <pubDate>Tue, 16 Jun 2026 02:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
