Skip to content

extend-solver.md

Latest commit

 

History

History
31 lines (24 loc) · 1.28 KB

extend-solver.md

File metadata and controls

31 lines (24 loc) · 1.28 KB

Extend the Solver

Use the generated project as the starting point, then grow solver behavior in the application that depends on solverforge.

When to change solver behavior

  • Add or refine constraints when the default business rules are incomplete.
  • Tune solver.toml when the search strategy, termination, or runtime settings need to change.
  • Use #[planning_solution(config = "...")] when a retained solve needs a per-solution override; the callback should decorate the loaded solver.toml config rather than replace it.
  • Introduce custom phases, selectors, or acceptors when the stock search flow is not a fit for the problem shape.

What to keep in mind

  • Keep domain modeling in Rust and solver policy in configuration separate; use per-solution config callbacks only to layer runtime-specific adjustments on top of solver.toml.
  • Preserve structured solver events and telemetry so the UI and service layer remain accurate.
  • Prefer small, app-specific extensions over forking the scaffold templates.

Practical path

  1. Start from the scaffolded project.
  2. Change the domain model or constraints that encode your business rules.
  3. Adjust solver configuration for search strategy and termination.
  4. Add custom solver code only when configuration is not enough.