Skip to content
UxerProof

How it works

Eleven steps from an unverified URL to shippable proof

Nothing runs until you have proved you control the target. Nothing is retained that the report does not need.

Execution service not connected. Circuit runs shown here are fictional demo data. The isolated browser workers, queues and AI provider integration are added in the next engineering phase. Nothing on this screen was produced by executing a real website.

  1. 01

    Verify the target

    Add a Project and an Environment, then prove control of the domain with a DNS TXT record, a meta tag or a well-known file. UxerProof will not execute against an unverified target.

  2. 02

    Choose an AI User

    An AI User combines a Persona (goal, patience, expertise, traits) with a device, locale and any assistive constraint such as keyboard-only.

  3. 03

    Compose the Circuit

    Describe the journey as ordered steps: navigate, input, decision, action, verify, handoff. Each step carries an intent and an expectation.

  4. 04

    Preview before you spend

    The preview shows the resolved Circuit — target, mode, participants, steps and the credits it will consume — before anything runs.

  5. 05

    Execute the Run

    Needs execution service

    The execution service drives an isolated browser through the journey as the AI User. Each step produces timing, observations and evidence.

  6. 06

    Synthesise the report

    Steps are classified as completed, friction or blocked. Findings are written against the step where the behaviour occurred, with a concrete recommendation.

  7. 07

    Score transparently

    Completion, friction, clarity, accessibility and consistency are scored separately and combined into the Proof Score.

  8. 08

    Discard what is not needed

    Raw screenshots, traces and execution artefacts are encrypted and deleted within 24 hours — immediately in Ephemeral Mode. Structured findings and selected evidence remain.

  9. 09

    Approve a Baseline

    Freeze a Run you are happy with as the approved comparison state for that Circuit.

  10. 10

    Detect regression

    Needs execution service

    Regression Circuits replay against the Baseline and produce a Before / After Proof, including anything that got worse.

  11. 11

    Account for usage

    Needs execution service

    One credit is one normal Circuit run of up to five minutes. Runs that fail because of our infrastructure are restored automatically.

Walk it with demo data

The demo replays a fictional Circuit end to end, including the report you would receive.

Open the demoSample report