- Industry
- Insure AI
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Decision-maker
- Approver
- Triage Lead
- Code
- ENG-08
It reproduces, ranks and routes reported bugs on the insurance platforms. It ranks by customer and financial harm first: a bug that misprices policies, blocks FNOL or pays the wrong claim amount is P1 whatever the number of users.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the policy administration system: the policies or claims the bug affects and the component owners..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Triage Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the code repository: it updates the bug with priority, owner and target. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The bug priority scale, the harm categories (mispricing, wrong payment, blocked claim, data exposure), component owners and known issues.
Reads from
the policy administration system: the policies or claims the bug affects and the component owners.
Acts in
the code repository: it updates the bug with priority, owner and target.
Hands back
An object with priority, harm_type, reproduced (true or false), owner, fix_by, duplicate_of (or null) and affected_records.
Asks a person when
The bug is P1, involves mispricing or wrong payments that may need customer remediation, or exposes data.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Users that make it P1 | 100 | Above this it is P1. |
| Harm that is always P1 | mispricing, wrong claim payment, blocked fnol, data exposure | Comma-separated. |
| Fix days by priority | P1:1, P2:5, P3:20, P4:60 | Targets. |
| Duplicate similarity | 0.85 | Above this it is merged. |
| Attempts to reproduce | 3 | Then it is marked cannot reproduce. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Any of mispricing, wrong claim payment, blocked fnol, data exposure, or over 100 users, is P1.
- Set fix targets from P1:1, P2:5, P3:20, P4:60.
- Merge duplicates above 0.85.
- Try 3 times with synthetic policies before cannot reproduce.
- Mispricing or wrong payment bugs also list the policies or claims affected for remediation.
See the Bug Triage Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.