Analyzing Underwriting Rules

1. Search the pure directory for .js files containing underwriting rules.
2. Identify the referral code (照會碼) triggered by the rule condition.
3. Look up the referral code's meaning in the corresponding JSON mapping file.
4. Cross-check the business logic against current Taiwan insurance regulations (金管會/保險局法規, 保險法, 商業條款).
5. Report: rule condition → referral code → business meaning → regulatory alignment (compliant / discrepancy / needs verification).

Example lookup command:

Bash
grep -rn "referralCode\|照會碼\|REFER_" pure/*.js

Progress:

• Step 1: Locate relevant .js rule file(s) in pure directory (search by keyword, referral code, or business topic)
• Step 2: Extract the exact condition logic (if/switch/ternary) that triggers each referral code
• Step 3: Find the referral code's textual meaning in the JSON mapping file (search by code value)
• Step 4: Translate the JS condition into plain business language (underwriting terms)
• Step 5: Compare against current Taiwan insurance regulations relevant to that rule (age limits, sum insured caps, disclosure requirements, health declaration rules, etc.)
• Step 6: Flag any mismatch, outdated regulation reference, or ambiguous logic
• Step 7: Summarize findings with code snippet, plain-language explanation, and regulatory citation

Step Details

Step 1-2: Locate & Extract

• Rules are typically expressed as condition blocks that return or set a referral code variable.
• Note the exact variable/field names used (e.g., age, sumInsured, bmi, occupationClass) — these map to insurance business terms.
• Capture the full condition, not just the fired branch — edge cases and boundary values matter for regulatory compliance checks.

Step 3: JSON Lookup

• The JSON file maps code -> description. Match exactly, including leading zeros or code prefixes.
• If a code exists in JS but not in JSON (or vice versa), flag it as an inconsistency.

Step 4: Business Translation

• Convert technical conditions into standard insurance terminology (e.g., bmi > 35 → "體重過重核保加費條件", age >= 65 → "高齡投保限制").
• Use standard Taiwan insurance vocabulary: 核保 (underwriting), 照會 (referral/inquiry), 加費 (loading), 除外 (exclusion), 拒保 (decline), 展延承保 (postpone), 批註 (endorsement), 體檢 (medical exam), 告知事項 (disclosure items).

Step 5-6: Regulatory Check

• Reference current rules from 保險法, 保險業招攬及核保理賠辦法, 人身保險商品審查應注意事項, or relevant 金管會函令.
• Common check points: age-based underwriting limits, mandatory disclosure/告知事項 scope, cooling-off period (契約撤銷權), pre-existing condition exclusions, sum insured limits tied to income or age (like 未成年人保額限制).
• If regulations have changed since the rule was written, explicitly call this out as a potential compliance gap — do not assume the JS code is authoritative.

Example 1: Input:

JavaScript
if (age >= 65 && sumInsured > 3000000) {
  referralCode = "R102";
}

JSON: "R102": "高齡且高保額，需主管核保覆核"

Output:

• 規則說明: 當被保險人年齡達65歲以上，且投保金額超過300萬元時，觸發照會碼 R102。
• 商業意義: 高齡高保額案件需經主管進行人工覆核，屬風險控管機制。
• 法規對照: 目前無明文禁止該年齡與保額組合承保，但需檢視是否符合公司內部風險控管政策及「人身保險商品審查應注意事項」中高齡者商品的核保注意事項。建議確認300萬元門檻是否仍為公司最新風險胃納標準。
• 狀態: 需與業務單位確認門檻數值是否為最新版本。

Example 2: Input:

JavaScript
if (isMinor && sumInsured > minorDeathBenefitCap) {
  referralCode = "R088";
}

JSON: "R088": "未成年人死亡給付超過法定上限"

Output:

• 規則說明: 未成年被保險人之死亡給付投保金額超過 minorDeathBenefitCap 常數值時觸發。
• 商業意義: 對應未成年人保險金額限制的核保管控。
• 法規對照: 需查核 minorDeathBenefitCap 常數是否等於現行保險法第107條及金管會公告之未成年人死亡給付上限金額（該金額會隨政策調整）。這是常見的過時風險點 — 若常數未同步更新，將導致核保錯誤放行或錯誤照會。
• 狀態: ⚠️ 需優先驗證此常數是否為當前法定金額。