Let’s talk
SEE DIGITAL HUMAN OPERATE

The action.
The reasoning.
In the same frame.

Original synthetic motor-claims demo showing the application alongside the model’s reasoning panelWatch the 55-second demo
Claim form & applicationModel reasoning
THE DIGITAL HUMAN PLATFORM

Your expertise.
New capacity.

The way your best people work,
made useful across your organization.

Watch the work unfold Explore a partnership ↗
Expert work Your specialist Knowledge + actionDesigned for your environment.
FOLLOW ONE EXCEPTION

From observed work
to usable intelligence.

One insurance question with conflicting information.
See the recorded answer, then explore how the product is designed to learn.

RECORDED Q&A / CONCEPT INTERFACEInsurance intake Anonymized
01 / CAPTURE

The steps are visible. Capture the reason.

The intake summary names a condition, but the form says Unknown. The recorded answer checks the source, then the linked records.

With consent, keep the context, actions, corrections and outcome inside your environment.

Capture Agent · buildingLearn from the judgment behind the click.
Expert workstationFrom a recorded Q&A
CLAIM INTAKERecreated view

Two different signals.

Valid intakeSpecific conditionAuthoritative source
Claim formUnknownException to investigate
THE RECORDED ANSWERVerify the intake source.
KEEP THE REASON WITH THE WORK
ContextDecisionOutcome
Consented observation

Concept based on a recorded Q&A. Pause controls and privacy protections on the device are planned requirements.

02 / LEARN

Learn from your best. Keep the compliance floor.

Five people take 5, 6, 7, 20 and 22 minutes. The average hides what makes the best work different.

The rules come first. Then learn more from examples that are accurate and efficient.

Specialist training · demonstratedLearn what makes the best work better.
Learning from expert workIllustrative task times
Compliance gateEvery example must pass first.
REQUIRED
Expert band · 5–7 minLonger task times
Compliance
Measured expertise
Specialist

Speed alone is not expertise. Good examples must also be accurate and follow the rules.

03 / IMPROVE

Try a better path. Keep what works.

Learn from expert examples. Try a different approach, check the result, and keep it only when it meets the rules.

Examples of correcting mistakes help the model learn. Separate tests check how it handles work it has not seen.

Illustrative learning mechanism · not a measured curveFollow the rules. Check the improvement.Explore the evaluations ↗
Learning from outcomesIllustrative mechanism
CAPABILITYLearn → explore → verify
Learn from examplesLearn from tested outcomes

Dashed line: best observed demonstration.

01Try a variation
02Verify the outcome
03Keep or revise

Every attempt must meet the rules. Training examples stay separate from the final test.

Expert workstationFrom a recorded Q&A
CLAIM INTAKERecreated view

Two different signals.

Valid intakeSpecific conditionAuthoritative source
Claim formUnknownException to investigate
THE RECORDED ANSWERVerify the intake source.
KEEP THE REASON WITH THE WORK
ContextDecisionOutcome
Consented observation

Concept based on a recorded Q&A. Pause controls and privacy protections on the device are planned requirements.

PRODUCT CONCEPT · SCROLL TO FOLLOW THE LEARNING
04 / KNOWLEDGE, THEN ACTION

Ask with context.
Act with evidence.

The aim is to help people answer questions and carry out work, with the right checks and approvals.

A / ASK

A question in the middle of work.

See one recorded claims answer and two documented workflow rules. Open the source notes to understand what each example shows.

Knowledge demo · recordedExplore a separate execution demo ↓
Ask CompanionRecorded Q&A
WORKFLOW QUESTION

The intake summary says severe migraine headaches; the form says Unknown. Linked absence and disability records are not yet synchronized. What comes next?

Digital Human

Check the valid intake summary, resolve the conflicting condition, and confirm the linked records are synchronized before disability review.

Explains the source and the next check
Source and context Recorded Q&A
Recorded claims Q&A · Probe 1 · May 27, 2026

Adapted from the recorded answer about which source to use and what to check next. No record update or claim approval is shown.

Company names and identifying details removed

Paraphrased from the recorded Q&A or documented workflow, as labeled. These are prepared responses, not a live chat.

B / OPERATE

The work, across applications.

Watch a separate insurance demo check a policy, fill the claim form, add a client note and confirm the outcome through the existing applications.

Operator Console · in development

Silent highlights using synthetic data. The claim is registered and remains under review.

ACTUAL APP RECORDING00:55 / SILENT HIGHLIGHTS
01 / Verify coverage

The policy coverage is checked before the claim is registered.

A silent 54.5-second highlights cut using synthetic demo data. Selected sequences play at 2× speed; form recovery and the expanded reasoning have time to read. The full application and reasoning panel remain visible together. Pause or use the chapters to inspect a moment. The claim is registered and under review, not approved or paid.

Read the scene overview
  1. Verify coverage. The policy coverage is checked before the claim is registered.
  2. Fill the form. The application fills with claim details while the actual reasoning trail remains alongside it.
  3. Recover the amount. An edited amount is corrected back to 2,500. Watch the recovery and the remaining fields.
  4. Add a task. The registered claim appears with New status. A client-note task is added.
  5. Write the note. The client note and expanded reasoning show the work and its explanation in the same frame.
  6. Confirm the outcome. The reasoning records completion. The confirmation email keeps the claim in New status for review.
ONE INTELLIGENCE. FOUR WAYS TO WORK.

Different people.
One shared capability.

Follow the same work from the expert’s desk to the team, the operations leader and the reviewer.

01 / For the expertBuilding

Capture Agent

Learn from how an expert works, with that person in control of capture.

Capability details
  • Visible capture status
  • Pause at any time
  • On-device privacy handling
  • No individual productivity scores
02 / For the teamPlanned

Ask Companion

Help the team find an answer and see the examples behind it.

Capability details
  • Links to supporting examples
  • Read-only guidance
  • Say when the evidence is insufficient
  • Feedback for improvement
03 / For the operations leaderPlanned

Variance Map

See where the same work is handled differently, and where the team could improve.

Capability details
  • Workflow-level patterns
  • Work volumes and differences
  • Team coaching opportunities
  • Aggregate views, never individual rankings
04 / For operations and complianceIn development

Operator Console

Review the proposed action and its evidence before deciding what may proceed.

Capability details
  • Review and escalation queue
  • Approval rules for each workflow
  • Action and outcome records
  • Human oversight

Availability as of September 2026. Specialist training and tests on specific tasks have been demonstrated. Capture and execution tools are in development; general autonomous operation for customers is not yet available.

THE GRADUATION RULE

Give it responsibility.
As it earns your trust.

Start by helping a person decide. Expand responsibility only when customer testing shows it is ready.

  1. 01

    Grounded knowledge

    Help a person decide.

  2. 02

    One bounded action

    Keep approval in the loop.

  3. 03

    Broader responsibility

    Expand only after validation.

Explore the controls ↗
PLANNED CAPABILITIES

Designed for the people responsible.

Review

Proposed actions and supporting evidence, ready for a person to review. Availability will be agreed with design partners.

Inspect

A searchable history of decisions, with evidence to inspect and export. Availability will be agreed with design partners.

Improve

Alerts when applications change, results worsen or the same problem repeats. Availability will be agreed with design partners.

START WITH ONE WORKFLOW

A clear path
to proof.

Choose one workflow. Prepare access and examples. Target a 60-day pilot, then use a separate customer test to decide what comes next.

Explore your pilot
60days

PILOT TARGET

Readiness first.
Evidence before expansion.

A target after prerequisites are ready, not an automatic production date. Timing depends on readiness, complexity and validation.