Poisson Tasks is out. Find where your agent breaks before your users do. Read the launch
Poisson Prove is out. It tells you whether a change to your agent really changed how often it fails. Read the launch
Poisson Labs

Poisson LabsData workflows and pipelines

Know what evidence it takes to take a workflow off manual review.

An agent drafts answers, resolutions, flags and reroutes, and a person approves every one. Poisson says which action types a change made worse, and how many cases it would take to clear a threshold you choose.

Results come from a synthetic copy of a payments back office, calibrated to public comparables.

● OpenSynthetic back office · CI workflow previewSwitch to the cheaper model

600 actions per version

build
poisson cloud / provefailed

1 of 4 action types got worse.

Merge blocked
report.md · a cheaper model, harmful actions
Action typeBefore → afterVerdict
RFI answers0.0% → 0.0%no significant change
Break resolutions0.0% → 0.0%no significant change
Late-payout flags0.7% → 0.0%no significant change
Reroute drafts4.0% → 22.7%worse
Harmful means it would have cost money or trust had it gone out. The agent never moves funds. A tightened prompt then took wrong late-payout flags and reroute drafts to zero.

01The threshold

What would it take to stop approving by hand?

Cases needed for the interval's lower bound to clear a threshold you choose, if the rate so far continued. "Not at this rate" means the agent has to get better first.

report.md · cases to clear each threshold
Action typeRight so farPast 90%Past 95%Past 98%Past 99%
RFI answers94.7%159 casesnot at this ratenot at this ratenot at this rate
Break resolutions100.0%alreadyalready189 cases381 cases
Late-payout flags87.3%not at this ratenot at this ratenot at this ratenot at this rate
Reroute drafts83.3%not at this ratenot at this ratenot at this ratenot at this rate
Not a recommendation to drop approval. The threshold is yours.

02Where a bad number enters

Wrong answers: 43 → 24, of 300.

Trace names the first step that carried a wrong figure, so the fix goes where the error entered.

trace · where each wrong figure entered
The agentBeforeAfter
did its own work, its query or its arithmetic, with no planted wrong figure read along the way3318
ran a query that left the cancelled payments out of the failed total106
p = 0.013 at the run level, across 3 question families; read by input, p = 0.25, and no single family moved significantly on its own. The version, the provider and the hour changed together.

03Where it runs

Inside your own infrastructure.

Poisson Cloud runs in your own cloud account. Keys, prompts and outputs stay on your side, and sending run records to us is a switch you control.

MATH ASINFRASTRUCTURE.

Talk to us