Bentham AIHuman Insight. AI Oversight.
GuestSign in
Bentham AIHuman Insight. AI Oversight.

Human decisions. AI decisions. Consequences that matter.

Understand
human choice.
Oversee AI decisions.

Two tools for consequential decisions. HBM predicts human choices and helps professionals design behavior change. ADL independently examines the consequences of AI actions.

Start with a saved example. No sign-in required.

Bentham AI  /  A closer look

One event.
Two different questions.

A medication error has occurred. What happens next?

What will people choose?
62Disclose and
document
38Alternative account;
omit error
0Exact
ties

100 synthetic profiles. A saved, conditional calculation — not a measured population rate.

Saved HBM / ADL report examplesInspect the work
Human behavior, understood in context
Independent consequence analysis
Decision records you can examine

Two products. Distinct jobs.

Understand the choice.
Examine the consequences.

HBM models the human chooser. ADL evaluates the AI agent’s options. Both make the basis of an analysis visible.

HBM / Human Behavior Model

Predict the choice.
Explain it.
Design the change.

Understand what people notice, believe, value and anticipate. Model likely choices across a defined group, then compare how changes in circumstances could change behavior.

For trained professionalsHuman choicesPractical change
ADL / Autonomous Decision Layer

Independent oversight
for consequential
AI decisions.

Examine an agent’s proposed actions and the consequences for each affected party. Inspect the evidence, estimates and unknowns in a reviewable decision record — a Logic Receipt.

Healthcare firstReviewable analysisControls in development
How ADL works

A closer look · Narrated introduction

See the choice.
Understand the consequences.

One clinical event. Two separately authored examples. See how HBM models the human chooser and ADL examines the consequences of an AI action.

User-initiated playback with audio, captions and a transcript. HBM 1.8.7: saved run, 5 October 2026. ADL 1.6.0: authored forecast, 5 October 2026.

Read the narration and on-screen case summary

The narrated introduction uses edited passages from the supplied recording. The updated examples are shown on screen and in the linked reports below.

I'm David Marx, founder of Bentham AI. We're bringing together decades of human-factors practice and years of research into human decision-making. Inspired by English philosopher Jeremy Bentham's work on social utility, we're combining our expertise with the power of today's frontier AI models to build two groundbreaking tools: the Human Behavior Model and the Autonomous Decision Layer.

The Human Behavior Model helps professionals explore what people in defined groups are likely to do under particular conditions, and why. What do they notice? What do they expect to gain, avoid, or protect? The point isn't just prediction. It's an explanation you can investigate and use to develop a change worth testing.

The Autonomous Decision Layer brings that concern for human consequences to the AI agents working on our behalf. Think of the ADL as a second, utility-based evaluator alongside your AI agents. The ADL Interpreter examines the available context, the options, and the gains and burdens for those affected. Its Logic Receipt makes evidence, assumptions, and uncertainty visible, so you can question the assessment rather than simply accept an answer.

We're also developing the ADL Governor: connecting that understanding to decisions your organization can support. Start with visibility. Add flags for review. Then, through tested integrations, hold or prevent specified actions where appropriate. You decide the scope of authority. We build the evaluation and controls to support it. Understanding first. Then governance at your direction, one decision at a time.

Watch the HBM and ADL demos here on our site. Then use your invitation to try the analysis tools for yourself. Bring a fictional or non-sensitive case. Examine the findings. Challenge the assumptions. Tell us what's useful, what's missing, and where you'd like to take the conversation. Bentham AI.

The cases shown on screen

Shared setup: A known injection error has occurred. Urgent care is identical under both choices; the final clinical outcome is unknown. Compare accurate disclosure and documentation with an unsupported explanation and omission of the known cause. The human and robotic versions are separately authored cases.

HBM: 62 of 100 synthetic profiles select disclosure; 38 select the alternative explanation and omission; 0 exact ties. The result is conditional on the report's beliefs and assumptions, not a measured population rate. The human report retains unestimated patient clinical remainders.

ADL: Expected Net Utility forecasts for A / B: patient +3.9e-5 / -9.0e-5; dental practice -1.0e-4 / -3.3e-5; treating clinical team +3.7e-6 / -6.7e-6; future service users +1.3e-5 / +1.2e-7. These are independent accounts, not a cross-target total. All 64 expected components are calculated within the declared scope. No Safety Check threshold crossing is identified; that is not clearance.

Development status: Customer-authorized production controls are being engineered. The demonstrated reports do not select or execute actions.

Explore the work

One event. Two products.
Different jobs.

Public examples · No sign-in

The endodontist case

A medication error has occurred.

An injection error causes a serious patient reaction. Urgent care is underway. The decision is what to explain and record.

Option A

Disclose and document.

Explain the known error, acknowledge uncertainty and make an accurate clinical record.

Option B

Reassure and omit.

Give an unsupported explanation and prognosis, omitting the known causal details while recording the reaction and care.

HBM · Human-clinician example

What will people choose?

A modeled choice across 100 synthetic clinician profiles.

62Disclose and
document
38Alternative account;
omit error
0Exact
ties

HBM 1.8.7 · 5 October 2026
Conditional calculation, not a measured population rate. The saved run assumes 1% hidden-error exposure and below 1% lawsuit risk conditional on revelation.

ADL · Robotic example

What would each action do?

Separate forecasts for the patient, practice and other affected parties.

A

A / Disclose accurately. Accurate information and informed participation coexist with apprehension, care costs and modeled follow-up risk.

B

B / Alternative explanation. Brief reassurance coexists with misinformation, impaired follow-up choice and greater modeled follow-up burden.

ADL 1.6.0 · 5 October 2026
All 64 expected components calculated within the stated scope. Scenario-specific forecasts, not observed outcomes. No action selected or authorized.

These are separately authored synthetic analyses, not observed outcomes, clinical advice or the selected first pilot workflow. The original injury and urgent care are common to both supplied choices. The previews above are excerpts, not complete reports.

Bring a scenario of your own.

Request analysis access for you or your team. Start with a fictional or approved non-sensitive case.

Saved examples are open. Running a new analysis requires access to the analysis workspace.

Try the demos

Inside ADL

An agent’s explanation
is not sufficient oversight.

The action, the evidence and the consequences need their own examination. ADL separates interpretation, calculation and customer-authorized control.

01 / INTERPRET

Make the judgment visible.

Map the available evidence to each affected party across 28 defined consequence factors. Keep assumptions and missing information in view.

Reports demonstrated
02 / CALCULATE

Make the account checkable.

Record values, probabilities and assumptions so fixed-input calculations can be checked. Keep each affected party’s account separate.

Recorded analysis
03 / GOVERN

Apply the customer’s policy.

Engineer flags, holds and refusals for authorized actions in supported workflows. The agent retains its task; the customer defines the boundary.

In development

The Logic Receipt

A decision record
built for examination.

See what was known, what was estimated, who may be affected and what remains unresolved.

EvidenceAssumptionsAffected-party accountsCalculationsUnknowns

What’s next

Two products.
Clear paths forward.

HBM moves to release. ADL moves through engineering and workflow evaluation.

HBM / Client Alpha

Beginning October 2026

Start with our existing clients.

Existing clients begin using the Alpha version as HBM moves toward full release.

Ask about HBM Alpha

HBM / Full release

April 2027

From understanding
to practical change.

Our six-month release plan brings HBM to trained professionals: frame the choice, model experience, compare changes and measure behavior.

Discuss HBM and practitioner training

ADL / Healthcare pilot program

Recruiting and selecting
pilots in spring 2027.

Bentham AI will select six healthcare pilot partners. With each organization, we will define the decision workflow, operating boundaries and measures of success.

  1. 01
    Monitor

    Replay and shadow decisions; examine evidence and consequences.

  2. 02
    Interact

    Test available context and supervised agent interaction.

  3. 03
    Govern

    Test customer-authorized flags, holds or refusals in supported workflows.

  4. 04
    Read out

    Assess decision quality, workload, implementation and adoption.

Engineering and workflow testing precede activation. Each phase has a separate customer release decision.

Discuss a spring 2027 pilot
David Marx, founder and CEO of Bentham AI
David MarxBS Engineering / JD

The founder

A builder of safety
and accountability systems.

David Marx brings systems engineering, human factors and law to consequential decisions. His work includes mishap-investigation methods for Boeing and NASA, prospective risk modeling and the development of Just Culture.

At Bentham AI, that foundation is being applied to understanding human choices and independently examining AI decisions.

David Marx
Founder & CEO, Bentham AI
Systems engineeringHuman factorsLaw

Start a conversation

Bring a decision
worth understanding.

Show us the human behavior you want to change or the AI decision you want independently examined.

HBM / Saved analysis excerpt

100 synthetic clinician profiles

What will people choose?

A human endodontist must decide what to disclose and document after a known injection error. Urgent care is already underway.

HBM 1.8.7Saved run: 5 October 2026Human-clinician case
62Disclose and document
38Alternative account; omit error
0Exact ties
This is a conditional calculation for 100 synthetic profiles, not an observed percentage of clinicians. It is not a measured prediction of how the clinical population would behave.

Source: supplied HBM 1.8.7 report, saved run 5 October 2026. The independent patient account retains unestimated clinical remainders; this is separate from the calculated human-choice result.

Read the full HBM report · 12 pages

ADL / Logic Receipt excerpt

Robotic case / Independent affected-party accounts

What would each action do?

Compare two supplied explanations and clinical records after a known robotic injection error. Each target retains a separate consequence account. The original injury and immediate urgent care are not charged again.

ADL 1.6.0Saved run: 5 October 2026No action authorized

Patient consequences, in plain language.

A

Disclose accurately. Accurate information, informed participation and usable recourse coexist with apprehension, care costs and a small modeled residual chance of preventable longer-term functional burden.

B

Alternative explanation. Brief reassurance coexists with misinformation, impaired follow-up choice and greater modeled follow-up burden. Discovery is not required for those immediate differences.

The forecast begins after the error and initiation of urgent care. It estimates defined option-linked changes, not total lifetime welfare or the original injury.

Source: ADL 1.6.0 consequence report, authored forecast 5 October 2026. These scenario-specific model estimates do not establish the patient's actual outcome.

Read the full ADL report · 45 pages

HBM / From insight to change

Predict the choice.
Explain it. Design the change.

HBM is a standalone tool for trained professionals working to influence patterns of behavior across a defined group.

01 / Frame the choice

Define the decision.

Describe the people, conditions and supplied options.

02 / Model experience

Understand the chooser.

Examine what is noticed, believed, valued and anticipated.

03 / Compare changes

Model the redesign.

Compare how a specified change could alter likely choices.

04 / Measure behavior

Compare with practice.

Measure observed choices and practical outcomes.

Client Alpha begins in October 2026. Full release is planned for April 2027. Public examples introduce the product; they do not substitute for practitioner training.
Ask about HBM

Method and evidence

Make the analysis examinable.

Interpretation, calculation and control have distinct jobs. Each needs its own evidence.

What is a Logic Receipt?

A reviewable decision record containing evidence, assumptions, separate affected-party accounts, the calculation record and unresolved information. It supports examination of the analysis rather than reliance on an agent’s account of itself.

What do the displayed examples establish?

They show analytical output from separately authored synthetic cases. They are not observed outcomes, calibrated clinical population rates or a demonstration of functioning live-agent controls.

Does ADL choose or execute an action here?

No. The saved robotic comparison selects and authorizes no action. The Governor is being engineered for customer-authorized controls in supported, tested integrations.

Does checkable arithmetic make the judgment correct?

No. A fixed-input calculation can be checked while its interpretation or estimates remain mistaken. Evidence, assumptions and unknowns must still be examined.

Can I try a scenario of my own?

Request analysis access. Use fictional or approved non-sensitive scenarios; do not enter patient information or confidential operational records into a public demonstration.

Explore Bentham AI

Start with the work.
Then try your own scenario.

Saved examples can be explored without an account. Running a new analysis requires access to the analysis workspace.

Explore a saved example.

Inspect the HBM result or the ADL affected-party forecast, including assumptions and unknowns.

Request analysis access.

Tell us who you are and what kind of decision you would like to explore. Access is separate from professional training.

Prepare an access inquiry

Use fictional or approved non-sensitive cases. Do not submit patient records, credentials or confidential operational information.

Review-draft connection note: this local preview does not sign you in, provision accounts or run either analytical model. Connect the approved invitation and authentication flow before publication.

Start a conversation

Bring a decision
worth understanding.

Tell us which tool you would like to discuss and the kind of decision you have in mind.

Review preview: this form prepares text in your browser only. Nothing is sent, stored remotely or saved between sessions. A working contact destination is not connected.

Please do not include patient information, confidential case details or credentials.

Preview the inquiry below, then copy it or save a text file for your review.