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
|
|
@ -41,10 +41,10 @@ def _entry(
|
|||
|
||||
def _mixed_ledger() -> SavingsLedger:
|
||||
""">=2 projects, >=2 dimensions, one cross-dimension overlap (the same candidate ``c-a`` realized
|
||||
under both ``energi`` and ``asfalt`` in P1 -> counted ONCE by the deduped total, FLAGGED)."""
|
||||
under both ``energi`` and ``lisens`` in P1 -> counted ONCE by the deduped total, FLAGGED)."""
|
||||
led = SavingsLedger()
|
||||
led.add_realized(_entry("P1", "c-a", 1000, dimension="energi"))
|
||||
led.add_realized(_entry("P1", "c-a", 1000, dimension="asfalt")) # overlap: same candidate id
|
||||
led.add_realized(_entry("P1", "c-a", 1000, dimension="lisens")) # overlap: same candidate id
|
||||
led.add_realized(_entry("P1", "c-b", 2500, dimension="energi"))
|
||||
led.add_realized(_entry("P2", "c-c", 4000, dimension="energi"))
|
||||
return led
|
||||
|
|
@ -109,7 +109,7 @@ def _sc6_entries() -> list[LedgerEntry]:
|
|||
direct ``SavingsLedger(entries=[...])`` (``add_realized`` would dedup the second). This exercises
|
||||
the TOTAL provenance sort from Step 1: a triple-only sort key would TIE the pair and let
|
||||
insertion order flip the bytes. Also carries a genuine cross-dimension overlap (``c-ov`` under
|
||||
both ``energi`` and ``asfalt``) so ``overlaps`` is non-empty."""
|
||||
both ``energi`` and ``lisens``) so ``overlaps`` is non-empty."""
|
||||
return [
|
||||
LedgerEntry(
|
||||
project_id="P1",
|
||||
|
|
@ -137,7 +137,7 @@ def _sc6_entries() -> list[LedgerEntry]:
|
|||
),
|
||||
LedgerEntry(
|
||||
project_id="P1",
|
||||
dimension="asfalt",
|
||||
dimension="lisens",
|
||||
candidate_identity="c-ov",
|
||||
amount_ore=3000,
|
||||
verdict_id="v-d",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue