Research Validation Engine

Find the holes before the reviewers do in your research.

Loophole Lab runs three adversarial critique rounds against your draft, returns a structured report, lets you share the result with a read-only link, and surfaces shared-report trends in a lightweight dashboard.

Browser validator live · Read-only shares · Internal dashboard · CLI + API surface

3

Attack Rounds

Self-refutation, methodology interrogation, and statistical or mathematical audit.

4

Supported Inputs

PDF, Markdown, LaTeX source, and plain text submissions.

Read-only

Share Mode

Shared links expose the report only. They do not expose submission controls.

2

Runtime Modes

Live model-backed validation when configured, deterministic offline fallback otherwise.

What Ships Today

A tighter product surface with working entry points.

The landing page now reflects the real application. No waitlist traps, no placeholder pricing, and no dead footer links. The primary flow starts in the validator and stays inside the shipped routes.

Why the cleanup mattered

The surface is finally honest.

The new shell keeps the routes that exist, removes the ones that did not, and makes the browser journey legible from the first scroll.

What stayed

The product still feels like a research instrument.

Structured findings, deterministic checks, and report-first outputs remain the core of the experience. The visual pass just restores the original voice.

Workflow

One path in, one path out, no fake side quests.

The browser surface is deliberately small: submit a draft, inspect the report, share it if needed, and review shared-report patterns in the dashboard.

Step 1

Submit a Draft

Upload a paper file or paste text directly into the validator. Validation progress streams inline instead of blocking behind modal alerts.

Step 2

Read the Report

Findings are grouped by round, tagged by severity, and expandable for attack details, quoted passages, and recommendations.

Step 3

Share or Export

Copy the report as Markdown or create a read-only link for collaborators. Shared reports remain public and unlisted.

Step 4

Inspect Shared Trends

The dashboard shows counts derived from persisted shared reports and a deterministic physics panel backed by existing prover logic.

Product Surface

Real routes, not roadmap cosplay.

Every card below points to a shipped part of the app or a documented runtime behavior already present in the repository.

/app

Validator

The primary browser route for running validations, tracking progress, copying Markdown, and creating share links.

/share/{report_id}

Read-only Reports

Shared reports reuse the validator renderer, hide submission controls, and increment view metrics only after the page loads successfully.

/app/dashboard

Internal Dashboard

Shared-report counts, verdict mix, domain chips, trend lines, and deterministic CHSH reference curves live here.

CLI + API

Operational Surface

The CLI remains available for local runs, while the FastAPI app exposes validation and reporting endpoints plus OpenAPI docs.

FAQ

Common operational questions.

The app can run in deterministic offline mode when LOOPHOLELAB_ALLOW_OFFLINE_MODE=true. The report still renders, but the critique comes from the local fallback instead of a live model.