<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Grossi.CATModels — BattleActs Exam 8 Forum</title>
        <link>https://www.battleacts8.ca/8/forum/index.php?p=/</link>
        <pubDate>Sun, 05 Apr 2026 16:44:10 +0000</pubDate>
        <language>en</language>
            <description>Grossi.CATModels — BattleActs Exam 8 Forum</description>
    <atom:link href="https://www.battleacts8.ca/8/forum/index.php?p=/categories/grossi-catmodels/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>Inuring Coverage</title>
        <link>https://www.battleacts8.ca/8/forum/index.php?p=/discussion/42/inuring-coverage</link>
        <pubDate>Mon, 27 Sep 2021 19:07:49 +0000</pubDate>
        <category>Grossi.CATModels</category>
        <dc:creator>ph2warne</dc:creator>
        <guid isPermaLink="false">42@/8/forum/index.php?p=/discussions</guid>
        <description><![CDATA[<p>The Hurricane example at the bottom of the CATModels wiki computes the coverage paid under each policy as if there is no overlap in coverage with other treaties in place.  Should it be obvious to assume that the payout of one treaty would be unaffected by the presence of the other, given they overlap on the same layer of loss?  </p><p>Had I instead assumed that the Excess Treaty was inuring to the Pro-Rata Treaty, the primary insurer would have been responsible for an additional 0.6M (1.5M x 0.4 = 0.6M, excluding Excess Treaty's share of this layer).  Is there ever a situation where I should be assuming that one treaty is inuring to another, or better to always assume not unless otherwise stated (ex. with interlocking clause)? If assumptions need to be made, is there a conventional "order of operations" if not explicitly stated (i.e., first apply excess coverage, then pro-rata coverage, etc.)?</p>]]>
        </description>
    </item>
   </channel>
</rss>
