Khalim Conn-Kowlessar 2bbc401f0d feat(modelling): Score carries the scored SapResult for billing ... Score gains sap_result: Optional[SapResult], populated by PackageScorer with the calculator output its headline figures came from. This lets the Modelling stage price the post-package (and baseline) end-state via Bill Derivation reusing a SapResult already computed by the optimiser's re-score / the orchestrator's baseline score — no second calculate (ADR-0014 amendment). The optimiser reads only sap_continuous, so it stays domain-agnostic and the stub scorers (which omit sap_result) are unaffected — all optimiser tests pass unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-03 17:20:45 +00:00
..
__init__.py	refactor(modelling): group domain/modelling into generators/scoring/optimisation	2026-06-03 13:48:36 +00:00
overlay_applicator.py	refactor(modelling): group domain/modelling into generators/scoring/optimisation	2026-06-03 13:48:36 +00:00
package_scorer.py	feat(modelling): Score carries the scored SapResult for billing	2026-06-03 17:20:45 +00:00
scoring.py	refactor(modelling): group domain/modelling into generators/scoring/optimisation	2026-06-03 13:48:36 +00:00