Executed demonstration · Fictional website · No AI model used

Inside an executed demonstration

A broken route.
A visible repair.

A missing contact page blocked the inquiry route. After repair, the same task checks reached the handoff.

Example Probate & Estate Planning · Fictional website

Scripted browser test. No AI model or consumer assistant was run.

Baseline · Broken variant

9successful tasks
out of 15 classified

6 task failures

Completed / planned
15 / 15
Excluded observations
0

Retest · Repaired variant

15successful tasks
out of 15 classified

0 task failures

Completed / planned
15 / 15
Excluded observations
0

5 journeys × 3 repetitions per variant. All planned trials ran; completion is separate from task success.

01 · The finding

The next step led
to a missing page.

The observed contact link points to /contact-missing and returns HTTP 404. Contact entry and inquiry handoff fail in all three repetitions each.

“The requested contact route is unavailable. No contact or booking was completed.”
Actual broken-fixture browser capture showing Page not found and an unavailable contact route.
Before: the contact destination is missingCaptured page: /contact-missingOpen full-size screenshot
Actual repaired-fixture capture showing the inquiry handoff, empty name and email fields, and instructions to stop before entering information.
After: the inquiry handoff is visibleCaptured page: /inquiryOpen full-size screenshot

02 · The bounded repair

Restore the route.
Check it again.

Point the visible contact navigation to /contact, make that page available, and provide its visible /inquiry handoff link and destination.

//contact/inquiry

Retest: 3 / 3 contact tasks and 3 / 3 handoff tasks succeeded. The browser stopped before form entry or submission.

Inspect the contact page

Structured-data syntax also changed and was not evaluated. The retest does not isolate the effect of a single change.

03 · The complete picture

Every task stays
in the report.

Each task was repeated 3 times per variant. Success means its recorded fixture condition was met.

Successful tasks / classified observations, by journey
JourneyBaselineRetest
Named service disclosure3 / 30 task failures0 excluded3 / 30 task failures0 excluded
Office and service area3 / 30 task failures0 excluded3 / 30 task failures0 excluded
Consultation process and fee policy3 / 30 task failures0 excluded3 / 30 task failures0 excluded
Contact entry route0 / 33 task failures0 excluded3 / 30 task failures0 excluded
Approved inquiry handoff0 / 33 task failures0 excluded3 / 30 task failures0 excluded

An unchanged limitation

Unknown fees stayed unknown.

Fees and availability stayed undisclosed. These tasks succeeded by reporting the unknowns accurately. A successful extraction does not establish adequate pricing disclosure.

Method and evidence

A result you can inspect.

How this demonstration was run

This local fixture tests the collection and reporting workflow. It does not measure a real business or predict consumer AI behavior. Repetitions are controlled checks, not a statistical sample.

Method
Deterministic observed-link navigation with recorded DOM observations and viewport screenshots.
Environment
Isolated local fixture; separate worker and temporary PostgreSQL database. No public website requests or paid APIs.
Browser and runtime
Playwright 1.63.0 · Chromium 153.0.8010.12 · Node v24.15.0
1280 × 800 viewport · en-US · Page JavaScript disabled
Per-trial limits
6 pages, 15 actions, 45 seconds maximum. No typing, submissions, sign-in or transactions.
Versioned configuration
Suite estate-probate 1.0.0
Prompt direct-site-readonly-1.0.0
Harness rendered-dom-1.0.0
Evaluator evidence-1.0.0
Safety policy readonly-1.0.0
Matching original fingerprints
bf701300d99eb704487708327882168b87036b08fe886e64fd90b4594a2189e5
Execution window
to

The repaired variant changed both navigation and JSON-LD syntax. The journey evaluator did not assess JSON-LD, so this comparison cannot attribute the results to a single change. Fees and availability were neither invented nor added; an authorized owner would need to confirm any future disclosure.

The same original configuration was retained. Public JSON replaces the temporary local origin with [local fixture]; screenshots are unmodified. This is a scripted fixture evaluation, not an approved customer assessment, accessibility certification or readiness score.

Download the execution record

Public records include every trial, capture reference and integrity check.

Start with your own website

What should an agent
be able to find?

Discuss an audit