Agentic Eyes reports & evidence

An Agentic Eyes report is only as useful as it is credible. Two mechanisms carry that weight: portable report formats, and evidence-grounded findings with telemetry behind them.

Reports you can hand to anyone

• Standalone HTML export — a self-contained report file; open it anywhere, attach it to a ticket, forward it to a founder or agency unchanged.
• PDF export — the same report for channels where a single document is expected.
• Share links — a URL for a completed run, for stakeholders who should read the finding but never touch the platform.

The report reads as a message from the user, not a QA artifact — that’s deliberate. It’s the same voice whether the reader is a growth lead or an engineer.

Evidence behind every claim

A persona’s narrative is backed by structured session telemetry:

• Route sequences — the actual path through the site, loops and revisits preserved, so “I kept ending up back at the homepage” is a verifiable observation with counts behind it (repeated_route_visit_count, repeated_action_count).
• Interaction and failure counts — derived from the real action trace, not the persona’s recollection.
• Deterministic browser evidence — an allowlisted browser trace plus runtime observations, kept separate from model claims. What the browser did and what the model said about it never blur into one field.
• Bounded, privacy-safe counters — console failures are integer counts only; console message content is never retained, because it can contain credentials or form values.

Groundedness

Findings pass a groundedness pass — tying each reported issue to captured evidence from the session — so a persona can’t convincingly describe friction that didn’t happen. This is the same philosophy as the hallucination gate: the model’s claims are checked against recorded reality, and provenance travels with the finding.

Retention shape

Simulation sessions persist one row per run (scoped by run, project, and owner) with terminal states including completed, failed, abandoned, and canceled — behavioral analysis sees them all, so abandonment rates aren’t survivorship bias. URLs retain origin and path only; never query strings or fragments; all payloads pass recursive redaction before storage.