mirror of
https://github.com/Hestia-Homes/Model.git
synced 2026-06-08 11:17:27 +00:00
2fbd7147b7
PortfolioGoal is domain vocabulary (a Scenario's goal — legacy planning branches on PortfolioGoal.INCREASING_EPC), so it belongs in domain/ co-located with scenario.py, mirroring how domain/epc/wall_type.py holds an enum that infrastructure/ imports. This lets the consolidated ScenarioModel (next slice) source the goal enum from domain without an infra→backend dependency. portfolio.py keeps a re-export so every existing `from ...portfolio import PortfolioGoal` caller is unaffected. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
23 lines
895 B
Python
23 lines
895 B
Python
"""PortfolioGoal — the retrofit objective a Scenario is scored against.
|
|
|
|
Domain vocabulary (ubiquitous language): the goal a user sets for a Scenario —
|
|
raise the EPC band, cut CO₂, cut energy, or improve valuation. The enum
|
|
*values* are the canonical strings stored in the live ``scenario.goal`` /
|
|
``portfolio.goal`` columns and used by the front end; the Modelling stage's
|
|
Optimiser branches on them (#1160).
|
|
|
|
Lives in ``domain/`` (not ``backend/``) so the domain, persistence
|
|
(``infrastructure/postgres/modelling``) and legacy app layers share one
|
|
definition — co-located with ``scenario.py``, which carries the goal. See
|
|
CONTEXT.md.
|
|
"""
|
|
|
|
import enum
|
|
|
|
|
|
class PortfolioGoal(enum.Enum):
|
|
VALUATION_IMPROVEMENT = "Valuation Improvement"
|
|
INCREASING_EPC = "Increasing EPC"
|
|
REDUCING_CO2_EMISSIONS = "Reducing CO2 emissions"
|
|
ENERGY_SAVINGS = "Energy Savings"
|
|
NONE = "None"
|