caelum0x 7087e7925e feat(product): symbolic simplify (egraph), model compose/edit, hosted-deploy
Wave 11 — the three candidates:
CLI — lawsynth simplify (egraph equality saturation extracts the lowest-cost
EQUIVALENT law; proves equivalence by simulating both worlds, deviation ~0;
honest 'already minimal' on sparse discovered worlds); lawsynth compose (union
two worlds into a coupled system, namespacing collisions) and lawsynth edit
(immutable rename/set-param/drop-law/scale-law, re-validated).

SDK — lawsynth.simplify / World.simplify (stdlib expand/fold/combine +
equivalence verify), lawsynth.compose, World.rename/set_parameter/drop_law/
scale_law. Two runnable examples.

Deploy — a verifiable hosted-deploy story: deploy/quickstart (config-validated
minimal api+gateway) + docs/self-hosting/quickstart.md (real curl/Client run
loop), after fixing genuine drift in the compose files (SQLite URL the API
actually accepts, correct token env, object root, health endpoints, native
build step) — verified end-to-end from source.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-08-18 01:08:14 +03:00

1.5 KiB

Self-hosting the local server core

Just want it running over HTTP? Follow the quickstart: bring up the API + admission gateway (SQLite metadata, filesystem object store), mint a token, and submit your first discovery run with curl or lawsynth.Client. The runnable Compose profile lives in deploy/quickstart.

lawsynth-server is a dependency-light Python domain core for local use and integration tests. It uses Python's standard-library SQLite adapter and atomic filesystem object storage. Application.dispatch() receives an in-process request dictionary; it is not itself an HTTP listener. The HTTP surface is the separate lawsynth-api process (a stdlib WSGI adapter that dispatches to this core); the domain's own lawsynth serve intentionally returns an unsupported-operation error.

Install the package in a Python 3.11+ environment, set PYTHONPATH=src while developing, and run python -m pytest -q tests from python/lawsynth-server. Configure a SQLite URL, an object root on a local filesystem, and explicit local bearer tokens. See architecture and authentication before exposing any adapter beyond a trusted machine.

Production HTTP/ASGI hosting, OAuth/OIDC verification, PostgreSQL, object-store signing, queues, worker execution, and distributed event delivery are deliberately unavailable here. Supply reviewed deployment-specific adapters for those concerns; do not infer support from the presence of domain routes.