Skip to content

About

Why the package is shaped the way it is, what it costs, where it came from and where it is going. Nothing here is needed to write a spec or run a model.

Architecture the thesis, the hard rules, the lane from YAML to solver, and the module map
The limits of the language what the language deliberately cannot say, and what that buys
Decomposition Benders as evidence: an algorithm the language does not contain, written as a loop over specs it does
Benchmarks measured build and solve cost against linopy, with the method and how to reproduce it
Relationship to linopy not a runtime dependency, the differential oracle, and the second lane
Prior art and credit the work this is derived from, and how to cite it
Roadmap where it is going, and what it will not become
Changelog every release

Contributing is CONTRIBUTING.md and AGENTS.md.