What each page is for
Boundary guide
Explains the line between caller-domain staffing problems and the current feasibility kernel.
Abstract companion
Restates the same boundary in object/morphism language for advanced readers and machine consumers.
Package overview
Summarizes the package contract, recommended flow, and what the solver does and does not do.
Examples overview
Shows a few concrete scenarios and how they map to the current compile / solve / regroup path.
Feature matrix
Lists current support, deferred areas, and the conservative read on package fit.
Current recurrence position
Recurrence domain types now exist in the package surface, but recurrence expansion is still not available as end-user behavior. The boundary proposal keeps recurrence as a domain-layer concern: templates and exceptions should expand into finite concrete input before the solver runs, and the primitive solver is not a recurrence engine.
Suggested reading order
- Boundary guide for the mental model.
- Abstract companion for the category-theoretic boundary view.
- Package overview for the recommended caller flow.
- Examples overview for concrete usage.
- Feature matrix for current support and out-of-scope areas.