Skip to content
Vareon

A result tied to the wrong decision is corrected.

Credit lands on the decision that earned it, even when it was first given to the wrong one.

Forgetting and data control. It runs On an authorised request.

The credit went to the wrong fix. One correction moves it.

The build passes again, and the credit goes to the last change made: a bigger cache.

Step 1 of 4: Green again

The next broken build gets the fix that worked.

While credit sits on the wrong change, the wrong fix keeps being suggested. Once it is moved, the team gets the fix that worked.

Step 1 of 3: The next break

Two weeks later, the build breaks the same way.

The wrong credit, from the day it landed to the day it moved.

Left alone, a result tied to the wrong decision keeps teaching the wrong lesson. Corrected, it teaches the right one from then on.

Step 1 of 4: Monday

Monday: the build passes, and the credit lands on the cache change.

Only someone authorised can move the credit.

Moving the credit is a decision your team makes. It names the result and both decisions, and it is recorded like every other change.

Step 1 of 5: Authorised

The request comes from someone allowed to correct what Duplex has learned.

See it on your own work.

From your own assistant to every agent your company runs, a pilot puts Duplex on your own work, with the measures agreed before it begins.