One flawed part, and every method that stood on it, withdrawn together.
Step 1 of 4: In use
A flawed part, withdrawn everywhere it was used.
A flawed building block is withdrawn, along with every method that used it.
Reusable skills. It runs At your administrators’ request.
The withdrawal reaches every method on the part, and stops there.
Withdrawing a part reaches each method that stands on it. Methods that never used it are not touched.
Step 1 of 3: The part
The flawed sort-code part is withdrawn.
The flaw is gone from everywhere, all at once.
On their own, scripts that copied the same flaw are found one at a time. With Duplex, one withdrawal reaches every method that stood on the part.
Step 1 of 3: The flaw
A flaw is found in how sort codes are read.
Every method on the part, and only those.
The withdrawal is exact: it reaches each method that used the flawed part, and leaves every other method as it was.
Step 1 of 5: The part
The flawed part is withdrawn.
Writes and tests small programs.
For a well-defined task, Duplex writes a small program, tests it against known cases and uses it only once it passes.
- A small program, proven on known casesRepetitive, well-defined work is done by a tested program, at almost no cost per run.
- Your model helps once, Duplex checks itFor a hard case your model is asked once, and the proven result is reused from then on.
- A solved problem, answered from its solutionA problem solved once is never paid for again.
- Trust in a program follows its resultsReal-world results raise or lower trust in each program.
- Every proven method, by status and ownerYour team sees every method Duplex relies on, who owns it and where it applies.
- One method, with its tests and historyAny method can be inspected, down to its tests and its track record.
- The reusable parts behind its programsThe building blocks that keep recurring are visible, so your team knows what new work stands on.
- The checks behind a programBefore your team relies on a program, it can see the tests it passed.
- A proven method becomes the preferred oneThe method with the best record is the one used by default.
- A doubtful method, paused straight awayA method that might be unsafe stops being used straight away.
- A fixed method returns to useOnce the cause is fixed and it passes again, a method returns to use.
- A wrong method, withdrawn for goodA method found to be wrong is withdrawn, and never comes back into use.
- A program erased when the law requires itA program and its data are erased when the law or the owner requires it.
- A flawed part, withdrawn everywhere it was usedA flawed building block is withdrawn, along with every method that used it.
- The parts that keep coming backWhat recurs across proven programs becomes a shared part, so new programs start further ahead.
- Every new method tested before useA method reaches your work only once it has passed its tests, whether it is new or changed.
- A new area starts from proven methodsA new work area can start from a library of proven methods, each re-checked locally.
- What its programs solve and saveYour team can see how much work programs take off your AI, and what that saves.
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.