lawsynth/docs/getting-started
caelum0x 760bc7e1fe feat(seo): add equation-discovery FAQ page, fix unresolved merge conflicts in docs-site
Adds docs/getting-started/faq.md targeting real search queries people ask
when evaluating equation-discovery / symbolic-regression tools (what SINDy
is, how LawSynth compares to PySINDy/PySR, whether it's free/offline, what
a .lsworld bundle is, and honest current limitations) — claim-gated against
the actual CLI, README, and docs/research/limitations.md.

Also fixes two unresolved git merge-conflict markers left in
apps/docs-site/package.json and src/site.ts from a prior merge (ef2abe9),
which left package.json as invalid JSON and broke `npm run build/test/render`
for the lawsynth.dev static-site pipeline. Resolved both in favor of the
feat/release-cut-2026-09-06 side (keeps seo_titles.test.js in the test script
and fallbackDescription() in renderPage, which seo_titles.ts already exports
and the rest of the file already relies on). Build, full test suite (15/15),
and a deterministic re-render all pass after the fix.

Rendered and deployed via `npx wrangler deploy`; new page verified live at
https://lawsynth.dev/docs/getting-started/faq (200, correct title/meta,
listed in sitemap.xml), and all referenced internal doc links verified 200.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-10-17 14:36:42 +03:00
..
2026-08-16 22:04:11 +03:00
2026-08-16 22:04:11 +03:00
2026-08-16 22:04:11 +03:00

Getting started

LawSynth turns time-series observations into executable mathematical worlds: interpretable law systems you can read, simulate, forecast, compare, and share. The whole product is one loop, and every step is deterministic and offline:

observe (CSV) → discover (laws) → understand (explain) → use (simulate /
forecast / intervene) → compare → share (report / .lsworld bundle) → organize

A discovery is a portable .lsworld bundle; everything downstream — CLI, Python SDK, Studio, and the HTTP services — operates on that same artifact.

  1. installation — build the lawsynth CLI and the Python SDK.
  2. quickstart — run the core loop end to end.
  3. concepts — datasets, worlds, laws, and bundles.
  4. your first world — discover, inspect, and reuse a bundle.
  5. Pick a surface: CLI, Python, or Studio.

Then go deeper with task-oriented, copy-pasteable material:

  1. Cookbook — short recipes for each task (discover, clean, forecast, validate, monitor, export, organize, pipeline, service, Jupyter), each with a CLI recipe and its Python-SDK equivalent.
  2. Tutorials — longer end-to-end walkthroughs that chain many features into one narrative (messy sensor → trusted model, predator–prey ecology, monitoring a running system).

The checked-in examples and the workspace tests are executable and are the source of truth for supported inputs. Discovery finds a sparse fit from the implemented feature library — it is not evidence that an inferred relation is causal or that extrapolation beyond the observed window is valid.