Recorded paths and fingerprints
Inspect navigation decisions. Understand how a route was found.
Browser Explorer · GameInteractive example
Explore the pages, decisions and routes behind a navigation task. Follow the journey and inspect what the explorer learned along the way.
What makes it useful
Inspect navigation decisions. Understand how a route was found.
Compare execution paths. Diagnose behavior.
Retain completed work. Revisit a partial run.
A closer look
The capability, the action, and what it means for you.
| Feature | What you can do | Why it matters |
|---|---|---|
| Recorded paths and fingerprints | What you can doInspect navigation decisions. | Why it mattersUnderstand how a route was found. |
| Manual and automated modes | What you can doCompare execution paths. | Why it mattersDiagnose behavior. |
| Receipts and resume | What you can doRetain completed work. | Why it mattersRevisit a partial run. |
3 capabilities
Work in progress. No LLM execution is permitted. Automated GMAT answering is disabled until a deterministic solver exists; manual GMAT play remains available. Earlier full GMAT runs used an LLM and do not meet this requirement. Other levels use the Jev policy and Web Navigator. The game opens inside Games Platform. Account creation, opponent games and headless sign-in remain unfinished.
Game session with a separate Jev controller.
Observe → Jev decision → Web Navigator ↑ │ └── Save graph ← Verify ───┘
Our own engine owns transitions; Web Navigator owns browser effects. Saved paths are observed candidates, not admitted procedures.
Browser Explorer · Game