refactor(examples): replace sector-specific example material with generic, fictitious examples
The context sets, the packaged knowledge bases and the example bundles are replaced by one fictitious example set about IT operations in an invented organisation: three context sets (serverrom-2027, driftsavtale-2027 and the two-base drift-og-avtale-2027), two synthetic knowledge bases under src/portfolio_optimiser/data/kunnskapsbaser and two example bundles under src/portfolio_optimiser/data/bundles. Numbers, codes and structural values in tests and fixtures are kept; names, ids and wording change. Dated measurement documents that only recorded runs on the replaced material are deleted. Gate figures measured on the new set are not comparable with earlier ones. The exclusion gate from the previous commit is green: 0 tracked files hit outside the shared/ subtree. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
058dd25570
commit
37547fe292
1147 changed files with 24138 additions and 9503 deletions
|
|
@ -40,11 +40,11 @@ from portfolio_optimiser.budget import PortfolioBudget, PortfolioMeter
|
|||
from portfolio_optimiser.run import RunFailure, run_portfolio
|
||||
from portfolio_optimiser.simulation import ScriptedChatClient
|
||||
|
||||
_PORTFOLIO_IDS = ["FV42-GSV-E1", "RV13-RAS-TP", "BRU-LAKS-REHAB"]
|
||||
_PORTFOLIO_IDS = ["KONTOR-IT-E1", "NETT-SIKR-TP", "ARKIV-LAGR-MIGR"]
|
||||
|
||||
# The MIDDLE project. Middle is deliberate (mirroring the Step-4 test): a failure at either end can
|
||||
# be dropped by a truncation bug and still leave the survivors in the right relative order.
|
||||
_FAILING_PID = "RV13-RAS-TP"
|
||||
_FAILING_PID = "NETT-SIKR-TP"
|
||||
|
||||
_DEFAULT_REPLY = (
|
||||
'{"measure":"Reduce scope","affected_items":'
|
||||
|
|
@ -54,7 +54,7 @@ _DEFAULT_REPLY = (
|
|||
# ``REPLIES`` is IMPORTED from tests/test_portfolio.py (see the import above) rather than copied —
|
||||
# the local copy had drifted onto other projects' cost codes, which S4.0's baseline anchoring
|
||||
# rejects. ``_DEFAULT_REPLY`` above is reached only by a prompt naming none of the three mapped
|
||||
# projects; on the anchored road path such a reply is rejected as a fabricated cost line, which is
|
||||
# projects; on the anchored reference path such a reply is rejected as a fabricated cost line, which is
|
||||
# the correct outcome for a project this fixture never described.
|
||||
|
||||
# Measured in tests/test_portfolio_budget_loadbearing.py: 4 chat calls x ``tokens`` per reply, so a
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue