Wave 4 — compare what-ifs to decide: CLI — lawsynth scenarios: define N named what-if scenarios (scheduled interventions), compare final-state divergence from baseline in a table + a self-contained multi-series HTML report (overlaid trajectories + legend). lawsynth doctor: environment/health check with a real world round-trip self-test. SDK — Study.add_scenario/compare_scenarios -> ScenarioComparison (table + overlaid-SVG _repr_html_); a cohesive StudyDashboard in lawsynth-notebook that composes equations/trajectory/frontier/regimes/uncertainty/scenarios into one themed Jupyter view; Study._repr_html_ now renders the full dashboard when the notebook package is present, degrading gracefully otherwise. Studio — Scenario Board (9th screen): define scenarios, overlay trajectories (multi-series chart + legend), baseline-divergence table, store-driven selection. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
LawSynth Studio
Studio is the browser orchestration layer for project workspaces, dataset inspection, law discovery, simulation, model structure, uncertainty, regimes, and provenance. It composes the typed API client and state store; numerical execution remains on the LawSynth service/runtime boundary.
The application controller is framework-neutral and can mount its accessible shell into an owned DOM element. Providers are explicit so authentication, persistence, logging, notification delivery, clocks, and identifiers remain replaceable at the application boundary.
const app = createStudioApp({ providers: scope, route: parseRoute(location.href) });
app.mount(document.querySelector("#app")!);
await app.start();
Call stop() during permanent teardown. It flushes pending settings,
unsubscribes state listeners, detaches keyboard shortcuts, cancels the active
workspace, and disposes providers in reverse registration order.