What's shipped, what's next

core/physics_validator.py — the full engine, live on the deployed site via the self-hosted Python backend.

5-seed, randomized-corruption benchmark with a naive-baseline comparison and a published methodology page — see /benchmark.

Pushed corruption recall from 55% to 71% on the harder, randomized benchmark.

Dataset profiling → physics checks → pattern recognition → targeted follow-up probes → synthesis, via OpenRouter.

Deterministic, reversible fixes (duplicate rows, IDs, timestamp ordering, wrapped angles, short NaN gaps) with a preview before anything is applied.

CSV, JSON, YAML, TOML, TXT, Markdown, VTK, NumPy, and OpenFOAM all normalize into one internal schema.

Predicts likely output-check failures before a simulation runs, with plain-English explanations and config-specific fixes.

login, validate, watch, doctor, explain, repair, api-key, config, usage — identical behavior in both implementations.

All backed by real captured validation runs from this browser — no seeded or synthetic data.

PYTHON_API_URL points the deployed site at the self-hosted Render backend, so the playground and API run the full 1700+ check engine. Falls back to a ~20-check TypeScript engine only if that backend is unreachable. The engine badge in the dashboard tells you which one you're getting.

railway.json and render.yaml exist; still validating the one-click flow end-to-end on both platforms.

Validation jobs are currently in-memory on the API server. A real queue + persistent store is needed before this can run as a production service with restart safety.

Today's auth model is single-user (a real, password-hashed local browser session). Multi-user orgs need a real backend data model — not on the roadmap until there's a durable store to build it on.

No payment provider is integrated. We won't add a fake pricing/billing UI before there's a real Stripe integration behind it.

Event delivery for validation completion, once job storage is durable enough to guarantee at-least-once delivery.

Let users register custom physics checks without forking core/physics_validator.py.