Journal
Blog
Release notes, technical articles, and product direction updates from SolverForge.
Releases
solverforge-cli 1.1.2: Stabilized Scaffolding for the Converged Runtime
solverforge-cli 1.1.2 polishes the CLI/runtime integration introduced in SolverForge 0.8.x, with aligned scaffold targets and improved test reliability for the retained lifecycle workflow.
SolverForge 0.8.2: CLI and Runtime Convergence
SolverForge 0.7.0 through 0.8.2 bring CLI scaffolding, config-driven runtime, and a retained SolverManager lifecycle—one coherent toolchain from first install to production operations.
SolverForge 0.6.0: Scaffolding and Codegen
SolverForge 0.6.0 is now available with first-class project scaffolding and generated domain accessors for cleaner constraint code.
Planner123 1.0: Your Week, Optimized
Planner123 1.0 is a personal task scheduler that models your week as a constraint satisfaction problem and solves it with SolverForge. Native Rust. Tauri desktop app. One binary.
solverforge-maps 1.0: Routing Infrastructure for VRP Solvers
solverforge-maps 1.0 provides zero-erasure road network and routing infrastructure for VRP solvers, with OSM data, R-tree indexing, and 3-tier caching.
SolverForge 0.5.0: Zero-Erasure Constraint Solving
Introducing SolverForge 0.5.0 - a general-purpose constraint solver written in native Rust with zero-erasure architecture and the SERIO incremental scoring engine.
Technical
The Current SolverForge Architecture: CLI-First, Rust-Native, Explicit
SolverForge's current architecture is CLI-first without being opaque: one neutral project shell, generator-driven model growth, scalar and list planning variables, retained jobs, and explicit Rust code.
Historical: From Quickstarts to Scaffolds
Archived transition note. The current SolverForge onboarding model is CLI-first: one neutral solverforge-cli project shell, generator-driven model growth, and scalar/list planning variables.
Public Means Public
In SolverForge, visibility is a contract enforced by the compiler. What's public is public. What's internal is internal. This will never change.
Historical: How We Built Quickstart Frontends with jQuery
Archived context for the old quickstart frontend architecture. Current SolverForge apps are generated by solverforge-cli and compose solverforge-ui.
Why Java Interop is Difficult in SolverForge Core
Reflections on the challenges of bridging Rust and Java in constraint solving, and the hard lessons learned along the way.
Order Picking Quickstart: JPype Bridge Overhead in Constraint Solving
Building an order picking quickstart with real-time 3D visualization deepened our understanding of JPype's performance characteristics in constraint-heavy workloads.
Dataclasses vs Pydantic in Constraint Solvers
Architectural guidance for Python constraint solvers: when to use dataclasses vs Pydantic for optimal performance.
Essays
Historical: Rust Constraint Solving Notes from the 0.5.0 Era
Archived context for early SolverForge design thinking. The current architecture is CLI-first, Rust-native, and centered on the current SolverForge runtime.