Improve / IMP-1

Score model 2.3 → 2.3.1 No clear answer

Use this page to check whether the score model change moved denials. Telemetry showed the change in credit.score_model_version at +3.25 h. Nobody at Auga proposed this change, so the measurement starts here.

ProposedNot by Auga, found in telemetry
LiveOld value gone by +3.22 h
MeasuredOnly before and after is available
Result on denials
No clear answer
Effect
−5 pts
23% to 18%
Compared by
Before, after
the old value ended
Ranges stop overlapping at
Never

The measurement

Every run up to the end of the file is counted
Compare
2.32.3.1 +0 h+2 h+4 h+6 h+8 h+10 h
DeniedApproved or referredSelect a mark:
Before the change
23% (14% to 35%), 14/60
After the change
18% (11% to 30%), 11/60
0%Denied, likely range (95%)100%

We cannot tell the runs before and after the change apart (−5 percentage points). The old value ended at the change, so no runs on the old value remain to compare with. Next, read What the measurement cannot say.

What moved with the change

Before and after, to +11.95 h
MeasureBeforeAfter
Denied23%18%
Median DTI0.280.27
Median reported income47,50044,500
Median risk score737740
Median duration3.5 s3.6 s
Tokens per run173179
Failed steps per run0.020.02

What the measurement cannot say

We cannot say why denials moved. The table lists what moved at the same time, and that is not a proven cause chain. can show the reason.

We cannot say whether the denials were wrong. We can say only that they moved. The file is synthetic, with a fault added on purpose, and real denials can be right.

We cannot say how sure we are of any moment when the ranges stop overlapping. Checking after every run makes such a moment look more certain than it is.

We cannot say which change moved denials. No runs stayed on the old value, so anything else that changed at that time looks the same.

The page is a prototype and a working draft. Auga computes the measured figures from Rootplant credit-4217, a synthetic file of 400 runs. The proposal and the rollout are simulated. Dashed links show planned features and open a note about them.

How the groups compare

The likely ranges overlap, so we cannot tell the runs before and after the change apart.

More exactly

Denied before the change: 14 of 60 runs, 23%, 95% interval 14% to 35%. Denied after the change: 11 of 60 runs, 18%, 95% interval 11% to 30%. The intervals overlap, so the result is not separated.

Proposal writer

Not built
What it will do

The proposal writer turns a finding into a concrete change and a written reason. Statistics choose what to change, and a model only writes it down.

Why Improve needs it

A cause is not an action. Knowing that DTI drives denials does not say what to edit. A person wrote the proposal on this page by hand.

Today

The proposal writer is not built. The rule stays that a model may not create or remove a link in the graph.

Agent Health

Partly
What it will do

The Agent Health page of each agent lists the changes that moved it and links here.

Why Improve needs it

Agent Health shows the current state. Improve follows what happens when that state changes, and that is the reason to return.

Today

The code is on branch feat/agent-health. It has no server route, no dashboard view and no link to mandates.

Choice of outcome

Partly
What it will do

A person says what counts as a failed run for each agent, and whether each run can be judged. Auga can follow several outcomes for one change.

Why Improve needs it

Here a denial counts as a failed run. A denial can be correct, so this figure only says that denials moved, not that they were wrong.

Today

A person sets the outcome by hand in the health report, with --outcome key=value. In Inbox, the engine's judges decide the outcome.

Rule for when to stop

Not built
What it will do

A test decides when a measurement may stop. It corrects for checking again after each run. The exact term is a sequential test.

Why Improve needs it

This page checks the likely ranges (95% intervals) after every run. Checking that often makes any moment when the ranges stop overlapping look more certain than it is.

Today

The rule for when to stop is not in the product. Mandate Simulator has a Bernoulli CUSUM alarm as a separate prototype.

Basemath, the measurement service

Partly
What it will do

Basemath runs this comparison as a service on live traffic. It covers every change, each agent and each outcome, with one API for this page.

Why Improve needs it

Basemath produces every result on this page. After a proposal goes live, the same comparison measures what it did.

Today

The comparison exists in auga/health.py on a branch. This page contains a copy of it, checked against that report. There is no endpoint yet.

Run view

Partly
What it will do

The run view opens the single run behind a mark. It shows the steps, the values and the path through the agents, but only data that may pass the data boundary.

Why Improve needs it

A person has to be able to check a result against real runs before believing it.

Today

Evidence has a run space. A full view of one run does not exist yet.

Cause chain in Evidence

In Auga
What it will do

The link opens the graph at this change, with its grade and the path to the outcome. A result can then show how the change had that effect.

Why Improve needs it

Measuring shows that something moved. Evidence can show why, and which setting to change. Proposals need that answer.

Today

Evidence exists. Its screening stops at 15 signals, and in our test suite that kept real links out of the graph.

Independent rule check

Partly
What it will do

Auga also checks every measured improvement against the result of a rule, and the agent cannot learn to satisfy that rule.

Why Improve needs it

If an automatic judge scores success, proposals can start to follow the preference of the judge rather than the outcome.

Today

auga/judgebias.py exists. The fix that lets it run on Inbox data is PR augalabs/augapro#113, which was not merged at the last check.

Rollout control

Not built
What it will do

Rollout control reads or sets the share of traffic on the new value. It uses your organisation's feature flags or deployment tool.

Why Improve needs it

A comparison with runs on the old version at the same time is possible only while both versions run. The exact term is concurrent control. After a sudden change, only a weaker before-and-after comparison remains.

Today

Rollout control is not built. The rollout on this page is simulated.