The workspace repository metadata pointed at a 404 (lawsynth/lawsynth instead of caelum0x/lawsynth). RELEASE.md documents 12 crates plus all services/apps as explicitly internal for v0.1 (not part of the published surface), but only lawsynth-integration actually carried `publish = false` — add the missing flag to the other 16 internal crates/services/apps so a future `cargo publish` run can't accidentally ship them. Also fix the two cargo clippy -D warnings failures blocking CI on main since the 2026-10-12 release-cut merge: lawsynth-information-diffusion's forecast() needlessly indexes `totals` by a range-loop variable (needless_range_loop) and exceeds clippy's argument-count lint (too_many_arguments, same pattern already used elsewhere in the workspace for fixed simulation-contract surfaces). Verified: cargo fmt --check, cargo clippy --workspace --all-targets -- -D warnings, and cargo test --workspace (388 suites, 0 failures) all pass clean; cargo build --locked --release -p lawsynth-cli succeeds. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
LawSynth scheduler service
lawsynth-scheduler is a local, durable scheduler for the worker's typed
JobEnvelope values. It owns queue state, worker-pool placement, generation-fenced
leases, expiry recovery, cancellation, and dead-letter transitions, and persists
lifecycle checkpoints through lawsynth-store. It is a library first
(Scheduler<S>) with an optional HTTP/1.1 control-plane transport
(SchedulerServer). No async runtime, HTTP framework, or message broker is linked.
Boundaries
- Control-plane only over HTTP. The transport exposes exactly the scheduler's
serializable operations: health, pool registration, job state, checkpoints,
cancellation, expiry recovery. Lease/heartbeat/complete/fail carry or fence
executable
JobEnvelopevalues, which have no wire codec, so they stay in-process Rust API calls.SchedulerTransportdeclares this honestly:LocalTypedis real executable dispatch;HttpControlPlaneis the serializable subset. Seedocs/security.md. - Deterministic in caller time. Placement, lease expiry, and recovery take
now_msexplicitly, so routing is a pure function of(scheduler, now_ms, request)and is testable without a socket or a clock. - Durable, bounded checkpoints. Records are persisted through an
ObjectStoreand bounded bymaximum_checkpoint_bytes; the payload is never serialized.
CLI
lawsynth-scheduler serve <addr> # control plane over an in-memory store
lawsynth-scheduler serve <addr> <root> # control plane over a durable LocalStore
Example:
lawsynth-scheduler serve 127.0.0.1:8082
lawsynth-scheduler serve 0.0.0.0:8082 /var/lib/lawsynth/scheduler
Run with no subcommand and it prints the honest transport statement (executable
dispatch is in-process and typed; the HTTP surface is control-plane only) and
exits. serve prints one startup line to stderr and then blocks, handling one
request per connection on a thread-per-connection model.
HTTP surface
See docs/api.md. In brief: GET /health, POST /pools, GET /jobs/{id},
GET /jobs/{id}/checkpoint, POST /jobs/{id}/cancel, and POST /recover.
Configuration
Bounds and per-environment profiles live under config/ (limits.yaml,
development.yaml, test.yaml, staging.yaml, production.yaml,
logging.yaml). They document the fields of SchedulerConfig (src/config.rs)
and StoreConfig; the current CLI applies the built-in defaults reproduced in
limits.yaml. No environment variables are read — see .env.example.
Build and test
cargo build --release -p lawsynth-scheduler
cargo test -p lawsynth-scheduler
Further reading: docs/architecture.md, docs/api.md, docs/operations.md,
docs/failures.md, docs/security.md.