Something went wrong. Try again.
A functional toolkit for authoring resource-leveling algorithms — compose constraint and scoring blocks, enumerate feasible schedules
Something went wrong. Try again.
feat(leveling): embed run provenance in materialized projects master
Every LevelingRun.materialize output now carries a levelset metadata block: engine version, the filled run config (rerunnable — the reproducibility artifact), seed, achieved scorer values, analysis warnings, and search annotations. ProjectFileSchema gains the optional field and the JSON reader/writer round-trips it (non-parsing provenance is dropped on read rather than failing the file). Answers "why does this schedule look like this?" from the file itself, spaCy config.cfg-style.
Author Russ T. Fugal Date (Jul 16, 2026, 6:10 AM UTC) Commit a8817373 a8817373fea264a74d3547e04474e4ab8f540623 Parent 1f9aec5b 1f9aec5ba32abd1507e367060ea6cd7f127a8836