@claritylabs/cl-sdk 3.2.3 → 3.2.4

package/dist/index.mjs

@@ -3787,6 +3787,7 @@ Rules:
 - Keep a coverage when it is a real operational coverage/benefit even if only one term needs cleanup.
 - When changing a term's semantic meaning, set kind to the corrected normalized term kind.
 - Do not add new coverage rows or new terms; this pass cleans the existing projection.
+- If one existing term combines multiple real limit bases, such as "Each Claim / Aggregate", keep the combined term unless another existing term already represents the other basis. Do not relabel it to only one basis and lose information.
 - Include every JSON key in each decision. Use null for scalar fields you are not changing and [] for source ID lists you are not changing.
 - For each coverage decision, always include termDecisions. Use [] when no terms need cleanup.
 - Keep reasons concise and factual.
@@ -5205,6 +5206,18 @@ function spanTableId(span) {
 function isTableCellSpan(span) {
   return spanSourceUnit(span) === "table_cell";
 }
+function isOperationalEvidenceAnchor(span) {
+  const sourceUnit3 = spanSourceUnit(span);
+  if (sourceUnit3 === "page" || sourceUnit3 === "table_cell") return false;
+  if (sourceUnit3 === "table" || sourceUnit3 === "table_row") return true;
+  const text = cleanText([span.text, span.formNumber].filter(Boolean).join(" "), "");
+  if (!text) return false;
+  if (/\bitem\s+\d+\.?\s*(?:named insured|policy number|policy period|renewal|form of business|coverage parts?|premium|extended reporting|producer|forms? and endorsements?)\b/i.test(text)) return true;
+  if (/\b(policy\s*(number|period)|effective date|expiration date|expiry date|named insured|insurer|carrier|broker|producer|premium|total due)\b/i.test(text)) return true;
+  if (/\b(coverage part|forms? and endorsements?|attached at inception|endorsement\s+(?:no\.?|number|#)?\s*[A-Z0-9])\b/i.test(text)) return true;
+  if (/\$[\d,.]+|[0-9]{1,2}\/[0-9]{1,2}\/[0-9]{2,4}|[0-9]{1,2}\s+[A-Za-z]{3,9}\s+[0-9]{4}/.test(text)) return true;
+  return false;
+}
 function operationalProfileEvidence(sourceTree, sourceSpans) {
   const sorted = [...sourceSpans].sort(
     (left, right) => (spanPageStart(left) ?? Number.MAX_SAFE_INTEGER) - (spanPageStart(right) ?? Number.MAX_SAFE_INTEGER) || (left.location?.charStart ?? Number.MAX_SAFE_INTEGER) - (right.location?.charStart ?? Number.MAX_SAFE_INTEGER) || left.id.localeCompare(right.id)
@@ -5214,6 +5227,7 @@ function operationalProfileEvidence(sourceTree, sourceSpans) {
   for (let index = 0; index < sorted.length; index += 1) {
     const score = operationalEvidenceScore(sorted[index]);
     if (score < 8) continue;
+    if (!isOperationalEvidenceAnchor(sorted[index])) continue;
     const tableId2 = spanTableId(sorted[index]);
     if (tableId2 && !isTableCellSpan(sorted[index])) selectedTableIds.add(tableId2);
     const page = spanPageStart(sorted[index]);
@@ -5301,6 +5315,7 @@ Rules:
 - On declarations pages, treat "Item N" labels as section boundaries. Use Item 6 or equivalent coverage-schedule rows for coverage limits, deductibles, aggregate terms, and retroactive dates; do not merge Item 7 premium, Item 8 ERP, Item 9 producer, or Item 10 forms into Item 6 coverage facts.
 - A coverage schedule row's coverage name should come from the "Coverage Part" or equivalent row label. Limit, deductible, aggregate, sublimit, retention, and retroactive-date values belong as nested terms under that coverage, not in the coverage title.
 - If a coverage schedule continues onto the next page before the next item marker, include the continuation rows in the same coverage or declaration item.
+- If one schedule row or continuation row states the same amount with multiple bases, such as "$1,000,000 Each Claim / Aggregate", return separate limit terms for each basis using the same value instead of one combined "Each Claim / Aggregate" term.
 - Forms-and-endorsements schedules are operational form inventory evidence, not coverage limits. Do not turn form schedule rows into coverage units unless the row also states a coverage-specific limit or deductible.
 - Keep each coverage unit tied to one evidence scope: a declaration/core schedule row, a core policy form section, or one specific endorsement schedule. Do not merge declaration facts and endorsement schedule facts into the same coverage unit, even when they use the same coverage name.
 - If the declarations schedule and an endorsement schedule both list Network Security, Social Engineering Fraud, Regulatory Proceedings, or another same-named coverage, return separate coverage units for each supported source scope.