CookieTrail / run-result UI explorations
prototype · static
How should we show a “run”?

One run, many readers.

A single capture walks a site like a real user in Brazil, Germany, California & the UK — pre-consent, accept-all, reject-all, granular and dismiss. Every branch leaves artifacts: a screenshot, the cookie jar, the network beacons, the console, the DOM. Below are three ways to read the same evidence. Can one view inform a dev, a designer and a lawyer?

🎨 Designer — “what does the user actually see?” ⚙️ Dev — “which beacon fired, with what payload?” ⚖️ Lawyer — “is refusal honored under each law?”
01
✓ accept
✕ reject
⊘ dismiss
SPATIAL · branching graph

Branch Canvas

The consent journey as a node-graph. Pre-consent forks into every path; click a node to crack open its evidence drawer. Switch persona to re-route the whole tree. Best for grasping the shape of behaviour.

🎨 strong⚙️ good⚖️ orienting
Open Branch Canvas →
02
🇧🇷
🇩🇪
🇺🇸
🇬🇧
COMPARATIVE · jurisdiction grid

Jurisdiction Matrix

Paths down the side, countries across the top, severity as a heatmap. See at a glance that “Reject all” is honoured in one country and ignored in the next. A diff-mode pins two cells side by side. Best for cross-border questions.

⚖️ strong⚙️ good🎨 scannable
Open Jurisdiction Matrix →
03
NARRATIVE · audit report

Evidence Dossier

A scrollable compliance brief per jurisdiction: a verdict header with grade, then a step-by-step timeline of the run with each finding cited to its raw artifact. Reads like a legal memo; every claim expands to the proof. Best when the output is a document.

⚖️ strong🎨 readable⚙️ deep-dive
Open Evidence Dossier →
04
!
TEMPORAL · real audit runs · LIVE DATA

Audit Playback

Step through the real Browserbase audits of prospect sites frame by frame — actual screenshots, the fork at the consent decision, and tracker states from the cookies each run really wrote. ←→ steps time, ↑↓ flips the path.

⚖️ strong🎨 strong⚙️ evidence-linked
Open Audit Playback →