Demo

See how a risky AI workflow becomes a reviewable decision trail.

The demo shows how requests and documents move through checks, approvals, and evidence-ready outcomes in a clear, reviewable sequence.

Workflow sequence

From request to evidence

Request enters -> document checked -> approval required -> decision recorded -> evidence ready

Request received
PalmerAI request received frame showing reviewable request intake.
Request received

Requests enter a reviewable intake step before model-side execution begins.

Proof frames

The same visual system, frame by frame

PalmerAI request received frame showing reviewable request intake.

Request received

Requests enter a reviewable intake step before model-side execution begins.

PalmerAI document checked frame showing inspectability and class signals.

Document checked

Inspectability, type, classes, and policy fit remain visible before the workflow can continue.

PalmerAI approval required frame showing explicit approval state.

Approval required

High-risk or uninspectable inputs create an explicit approval state instead of an informal workaround.

PalmerAI decision recorded frame showing reviewable decision fields.

Decision recorded

Decision state, reason codes, and timestamps remain legible later instead of being rebuilt from raw logs.

PalmerAI evidence ready frame showing exportable review state.

Evidence ready

Evidence exports stay reviewable with hashes, timestamps, policy version, and approval state attached.

Flow walkthrough

1. Request enters

A request or document enters the gateway instead of going straight to a model endpoint.

2. Document checked

Policy, inspectability, and class signals stay visible before the workflow continues.

3. Approval required

Risky or uninspectable events create explicit approval states.

4. Decision logged

Outcome, actor, timestamp, and policy version remain reviewable later.

5. Evidence exported

The final state stays usable for audit, assurance, and partner reporting.

Role views

Operator

Reviews approvals, incidents, evidence, and the wider control picture across environments.

Customer admin

Handles workflow-level approvals and sees what entered the workflow under the customer account.

Partner

Sees client-level summaries without needing raw document content in routine reporting.

Use the demo when buyers need to see the sequence clearly.

The practical question is simple: can the workflow be checked, approved when needed, and explained later without guesswork.