Documentation
Documentation
Use these docs to learn what SolverForge solves, scaffold a working app, and inspect the Rust APIs behind the runtime, UI, and routing helpers. Section indexes orient the tree; deep links take you straight to the implementation surface.
Start Here
Overview
What SolverForge solves, when to use it, and how it differs from mathematical solvers.
Status & Roadmap
Current release, published package status, runtime surface, and roadmap.
Getting Started
Start with the CLI shell, then continue into a complete hospital, lessons, deliveries, or field-service use case.
Worked Use Cases
Hospital Use Case
Scalar assignment, retained jobs, schedule constraints, and browser updates in one worked app.
Lessons Use Case
Lesson timetabling with teachers, cohorts, rooms, two scalar variables, retained jobs, and timetable views.
Deliveries Use Case
List-variable vehicle routing with maps, retained snapshots, and insertion recommendations.
FSR Use Case
Field-service routing with technicians, skills, shifts, road-network travel, and route geometry.
Runtime Reference
Constraint Factory Methods
Generated accessors, source-aware streams, joins, projections, collections, and scoring terminals.
Solver Configuration
solver.toml, phase configuration, move selectors, acceptors, foragers, and facade exports.
Projected Scoring Rows
Retained scoring-only rows from projection types and joined-pair .project(...).
SolverManager
Retained solve lifecycle, snapshots, events, analysis, pause, resume, cancel, and delete.
Companion Crates
solverforge-maps
Road-network loading, routing, matrices, route geometry, and map-backed planning helpers.
solverforge-ui
Frontend assets, lifecycle adapters, retained-job controls, and scheduling views.
solverforge-bench
Benchmark harness, CVRP and employee-scheduling runs, TOML configuration, and PostgreSQL result storage.
Crate & Runtime Map
Which crate or companion repository owns each part of the runtime surface.