FOR ORGANISATIONS / AI DOCUMENT WORK

From AI-assisted work to a decision and a result

Review an AI-assisted financial report or customer response against approved sources and review rules. Auxtho prepares findings and supporting passages; a responsible person resolves exceptions and makes the decision. The product also has an internal operating, investigation, defence and replay layer

Explore the document workflow

Actual hosted App capture · Owned synthetic QA. Evidence inspection is separate from assessment and approval

PRODUCT / TECHNOLOGY / RESEARCH / Auxtho

What the work looks like

Start with one report sentence, not an architecture diagram. Auxtho prepares what needs checking, the person decides, and the approved work continues through a recorded output path

01 / PREPARE

Check the claim

Auxtho checks selected claims against approved sources and review rules, shows supporting passages and prepares exceptions with reasons

02 / DECIDE

Approve the exact version

The person corrects, approves, holds or rejects. A changed version cannot reuse approval for the earlier version

03 / FOLLOW THROUGH

Keep the result connected

Content and individual files have distinct decisions. Preserve the actual result—or an explicit unconfirmed state—for later reconstruction

AUXTHO / HOSTED APP WALKTHROUGH

See the sentence and the source

The report amount is linked to the relevant row in the approved source. A reviewer can inspect what supports the claim rather than rely on a citation label

The visible “not evaluated” label belongs to this source-inspection screen. Opening evidence is not a new assessment or approval

One product. Two different roles

CUSTOMER-FACING / AUXTHO APP

Review the work. Make the decision

The customer-facing App lets users inspect report findings and sources, make version-specific decisions, and review saved-file outcomes

INTERNAL / AUXTHO CONSOLE

Operate, investigate and re-examine

Auxtho personnel use Console to operate, investigate and re-examine work. Replay connects recorded evidence and decisions with review, handoff and Lab. Separate re-execution compares results while preserving the original record

What has been verified

Inspect the recorded workflow: the source, the person’s decision, the saved files and the later recovery sequence

7 OCTOBER 2026 / HOSTED APP

The owned case recorded review of working version 2, the content decision, and separate JSON and PDF approvals and saves. Downloaded files matched the recorded outputs: JSON 9,531 bytes and PDF 50,137 bytes

Source inspection, review decisions and file approvals are separate steps. The video does not show external recipient delivery

LOCAL / BROADER WORKFLOW

Selected-claim checks, source-bound findings, human correction, exact-version decision binding and explicit unconfirmed outcomes have been implemented and locally tested in synthetic cases. This broader verification is separate from the hosted video

9 OCTOBER 2026 / DESIGNATED PDF

A controlled mismatch in the approved PDF’s file-format metadata caused download refusal and an incident record. After metadata restoration, the PDF was separately quarantined and released by an authorised operator. The recovered download matched the approved PDF byte for byte; the same job’s JSON stayed available and unchanged

This later QA sequence reused the approved PDF; it is separate from the 7 October video. File release left the incident open

10 OCTOBER 2026 / LOCAL REPLAY CONNECTION

Selected-policy application has been connected to actual replay judgment and the result record in the local implementation, with targeted backend and screen checks passed

Hosted rollout and acceptance of this new connection remain separate. Replay preserves the original record and does not activate a production policy

The cases use owned, noncustomer test material. These results do not establish financial-institution production outcomes, prevention of a named breach, recipient delivery, or MAS certification

AUXTHO / HOSTED APP WALKTHROUGH

Evidence
Decision
Result

Watch the actual hosted App screens from an owned test case. The short film follows source inspection, a reviewed version, and separately approved JSON and PDF files

See the verification scope

Recorded synthetic QA · 7 October 2026 · Silent, 30-second walkthrough. Saved-file verification, not recipient delivery

START WITH THE WORK

What would you
trust AI to do?

Tell us about one document workflow, one review decision, or one task you need to keep under human direction. Start with the problem—not a list of features

Talk to Auxtho