UAE · ENBook a demo
BankingEngineeringDecision-maker

Technical Debt Agent

Finds and refactors high-cost code.

Technical Debt AgentApplication Engineering
Industry
Banking
Department
Engineering
Team
Application Engineering
Kind
Decision-maker
Approver
Head of Technology Operations
Code
ENG-10

It finds the code that costs most to keep across the bank's channels, payments and core banking adapters, from churn, linked incidents and defects, complexity and slow builds, and estimates what fixing it would save. It ranks a refactoring backlog by payback, putting legacy code on critical payment paths and end-of-life components first.

How it works

7 steps, and a person signs off before step 7.

  1. 01Looks it up

    Finds the record the request is about in the code repository: churn, complexity, defects, incidents and build times by path..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Forecasts, when it decides

    Projects what each option will cost or return before it recommends one.

  5. 05Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  6. 06Asks a person

    Hands the work to Head of Technology Operations with its reasoning before anything goes out.

  7. 07Acts

    Once approved, it acts in the code repository: it creates the ranked refactoring items in the backlog. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The technical debt policy: debt capacity per sprint, hotspot measures, the critical business services list, end-of-life components the regulator expects to be remediated, and refactoring rules.

Reads from

the code repository: churn, complexity, defects, incidents and build times by path.

Acts in

the code repository: it creates the ranked refactoring items in the backlog.

Hands back

A ranked list of items, each with rank, path, cost_signals (churn, defects, incidents and build_minutes), proposed_fix, effort, saving and payback_sprints.

Asks a person when

The backlog changes a critical payment or core banking path, exceeds the debt capacity, or defers an end-of-life component past its support date.

ApproverHead of Technology Operations

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Debt capacity (%)20Share of capacity for debt.
Hotspot window (days)90Churn and defects measured over this.
Complexity limit15Functions above this are hotspots.
Largest refactor (lines)300Larger ones are split.
Payback within (sprints)6Items paying back slower are deferred.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Rank by payback within 6 sprints, measured over 90 days.
  • Code on a critical payment or core banking path, and any end-of-life component, ranks first.
  • Functions above complexity 15 are hotspots.
  • Plan within 20 percent of capacity; split refactors over 300 lines.
  • Refactors never change behaviour; each needs tests that pin the current behaviour first.

See the Technical Debt Agent agent on your own work.

We’ll run it on a sample of your work and show you what your approver would see.

Technical Debt Agent · Banking | Basinwright Industries