- Industry
- Insure AI
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Decision-maker
- Approver
- Platform Tech Lead
- Code
- ENG-17
It keeps the libraries in the insurance platforms patched, deciding which updates merge themselves and which need review. Updates touching rating, money handling, PDF generation for policy documents or cryptography always need review.
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 code repository: the dependency manifests and advisories..
- 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 Platform Tech Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the code repository: it opens or merges the update changes. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The dependency policy, allowed licences, end-of-life dates and the packages on sensitive paths.
Reads from
the code repository: the dependency manifests and advisories.
Acts in
the code repository: it opens or merges the update changes.
Hands back
A list, each with package, from, to, decision (merge, review or hold) and reason.
Asks a person when
The update is above patch, touches decimal and money libraries, PDF generation, cryptography, date handling, or changes a licence.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Merge itself | patch | Highest update level it merges. |
| Security patch within (days) | 7 | Deadline. |
| Allowed licences | MIT, Apache-2.0, BSD-3-Clause | Comma-separated. |
| Youngest release (days) | 7 | Newer is waited out. |
| Packages that always need review | decimal and money libraries, PDF generation, cryptography, date handling | Comma-separated. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Merge up to patch updates itself when tests pass, except decimal and money libraries, PDF generation, cryptography, date handling.
- Apply security patches within 7 days.
- Accept only MIT, Apache-2.0, BSD-3-Clause.
- Wait 7 days on new releases unless it fixes a security advisory.
- Any update to decimal and money libraries, PDF generation, cryptography, date handling needs the rating test pack and policy document snapshots to pass.
See the Dependency Management Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.