Status key
Available
Implemented and usable in the current playground/core surface.
Planned / likely
Not a current guarantee, but plausible next expansion from the existing boundary.
Out of scope
Explicit non-goal for the current feasibility kernel or playground surface.
Feature matrix
| Capability | Status | What it means here |
|---|---|---|
| Exact-match qualifications | Available | Candidate qualification must match required qualification type exactly. |
| Qualification validity windows | Available | Qualifications are only valid when their time window covers the assignment interval. |
| Availability / time off | Available | Unavailability blocks assignment; availability windows constrain eligibility. |
| Shift-pattern compatibility | Available | Weekday/weekend and shift-family pattern rules are enforced as hard constraints. |
| Minimum rest | Available | Rest-gap violations between assignments are treated as hard failures. |
| Consecutive-work limits | Available | Max consecutive worked days is enforced in the feasibility search. |
| Rolling utilization max | Available | Rolling window caps on assigned shifts are hard constraints. |
| Site-scoped coverage | Available | Coverage rules may scope to a site and regroup explanations preserve site context. |
| Line-aware coverage | Available | Coverage grouping preserves line context in domain explanations. |
| Recurring domain types / boundary entry point | Available | The package exposes recurrence template types and a boundary entry point, but not end-user expansion behavior. |
| Infeasibility explanations | Available | Primitive failures regroup into domain-facing explanations centered on failed needs. |
| Deployable evaluator surface | Available | The playground and local docs expose a runnable evaluator for the package. |
| Partial fill | Out of scope | Success still means a complete assignment set; no “best effort” solve mode yet. |
| Optimization / ranking | Out of scope | The solver does not choose the best schedule among alternatives. |
| Soft constraints | Out of scope | No penalty-based preferences or score-based tradeoffs are modeled. |
| Fairness | Out of scope | No fairness ranking or balancing policy is enforced. |
| Cost / overtime optimization | Out of scope | Overtime and labor cost are not part of staffing-scheduling’s current objective. |
| Recurring expansion / end-user behavior | Planned / likely | Deterministic expansion of recurring templates into concrete input is still a planned domain-side behavior, not an end-user runtime feature. |
| Qualification substitution | Out of scope | No hierarchy or “higher qualification covers lower role” semantics are modeled. |
| Production sequencing / machine-job planning | Out of scope | The system is staffing-feasibility oriented, not production-sequencing oriented. |
| Saved scenarios / collaboration | Planned / likely | Useful for workflow, but not part of the current core feasibility boundary. |