assign_role:${memberId}:${patternId}:${roleId}:${day} and aggregate
assignment variable names matching assign:${memberId}:${patternId}:${day}.
Parameters
{ error?: string; hardConstraintConflicts?: object[]; softConstraintViolations: object[]; solutionInfo?: string; stageResults?: object[]; statistics?: { branches?: number; conflicts?: number; solveTimeMs?: number; }; status: "OPTIMAL" | "FEASIBLE"; values?: Record\<string, number\>; } | { error?: string; hardConstraintConflicts?: object[]; softConstraintViolations?: object[]; solutionInfo?: string; stageResults?: object[]; statistics?: { branches?: number; conflicts?: number; solveTimeMs?: number; }; status: "INFEASIBLE" | "TIMEOUT" | "ERROR"; values?: Record\<string, number\>; }
required
The solver response containing variable values
Returns
SolverResult
Parsed schedule result with assignments
The model uses aggregate assignment variables as the canonical shift presence
literals for intervals, objectives, shift-level rules, and skill-only coverage.
Role-specific variables are emitted when the solver also chooses a concrete
role for that shift. When both variable shapes exist for the same member,
pattern, and day, the role-specific assignment is returned so callers can see
the selected role without receiving a duplicate aggregate assignment.
IDs are validated during CP-SAT model compilation to not contain colons,
ensuring unambiguous parsing.