01
Why not let the model plan
It breaks rules quietly.The plan looks right and puts someone on an early shift after a night, or an uncertified operator on a line.
It cannot prove anything.Not that a plan is the best one, and not that no plan exists.
It changes its mind.The same request gives a different plan on each run.
02
The split
The planner writes in words:"W07 is off Thursday. Line 2 needs a certified welder on nights all next week."
The model turns that into structured changes, checked against a schema before anything runs.
The solver computes the whole weekwith every rule, old and new.
The model explains the planand what changed, in the planner's words. A person approves it.
The model's output in step 2 is data, not a plan:
03
The solver
One line, one week, three shifts. Every rule is a constraint; fairness is the objective.
04
When no plan exists
The model must never invent one. The solver can name the requests that cannot all hold at once (CP-SAT assumptions), and the model turns that into a sentence the planner can act on: "Line 2 needs a certified welder on Thursday night, and both are off."
05
Where it fits
This is a Level 4 build: it reads people, skills and line needs from the plant’s own systems, and a person approves every plan before it goes out. The solver does the part that has to be right; the model does the part that has to be understood.
Related use case
Decision intelligenceOne answer across systems that disagree.