open/portfolio-optimiser-claude
1
0
Fork 0
Code Issues Releases 1 Activity

feat(portfolio): K2 — sequential multi-project run (parity row 4)

Browse source 
New portfolio.py: run_portfolio drives N projects sequentially from a
schema-validated reference config, composing each project's §5 context
(merge inbox -> seed -> fold) and running the loop core UNCHANGED per
project, collecting one typed result per project IN CONFIG ORDER. This is
the run path MAF got in its Fase 1 and D7 never had — the prior entrances
(run.py, run_s10.py) drive a single bundle. PortfolioResult holds
per-project results tagged with the config project_id.

Re-entrancy (§3 Step 3): each project composes its OWN context inside the
loop, never a hoisted shared one, so nothing survives one project into the
next except the explicitly shared mutable state — the §8 budget meter, a
portfolio-wide cap. Failure policy is a STACK-LOCAL choice until D-D: the
default RAISES (today everything is thrown); K18 flips it to
collect-and-continue when the D-D wave model lands.

New config contract in contracts.py: ReferenceProjectContract (project_id +
required non-empty bundle_dir + optional inbox_dir) + ReferenceProjectsContract,
loaded fail-fast by load_reference_projects (§10) — a project without a
bundle path is refused before any run. New data/reference_projects.json
example (shape-validated, never executed by the suite). New repo-local
mini-bundle fixture under tests/data/ (a distinct second project, VFD-retrofit
— ALDRI in shared/).

Two detach proofs delivered: drop the bundle_dir Field requirement -> a run
starts on the invalid config and only crashes mid-run -> the fail-fast test
goes red; hoist the per-project composition out of the loop -> project 2 runs
on project 1's context and the VFD marker never reaches its prompt -> the
re-entrancy test goes red. 11 new tests (test_portfolio.py 5 +
test_contracts.py TestReferenceProjects 6). 426 -> 437 tests, golden
byte-exact, full gate clean (ruff + format + mypy strict). README synced
(test count + a Run layer module block).

[skip-docs] — README documents the new module; CLAUDE.md holds invariants
(rules/commands) only, and K2 adds no new invariant, command, or convention.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RiTwaKLesgcwXx2mDviqpt
This commit is contained in:
Kjell Tore Guttormsen 2026-07-23 21:39:39 +02:00
commit f2c64da9ee
10 changed files with 406 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

26
tests/data/mini-bundle/verdict-vfd-fro.md Normal file
View file

@ -0,0 +1,26 @@
---
type: verdict
title: "Ekspert-dom (frø): VFD-retrofit — godkjent med realiseringskorreksjon"
description: "Frøsatt ekspert-dom for VFD-tiltaket. Koder et realiseringsgap distinkt fra LED-frøet (0.75, ikke 0.82) så porteføljetesten kan skille prosjektenes kontekst."
resource: PUMPE-SOR
measure_id: VFD-RETROFIT-01
decision: approved_with_adjustment
realization_rate: 0.75
modelled_saving_nok: 12000
expected_actual_saving_nok: 9000
gap_source: pump-affinity-oversimplification
context_key: "naeringsbygg; pumpe-last=stipulert"
provenance: "frø — AI-forfattet test-fixture; erstattes av ekte HITL i produksjon"
tags: [verdict, realization-rate, ExpeL-seed, fixture]
timestamp: 2026-07-16
---
# Ekspert-dom (frø): VFD-retrofit
> **Dette er et frø**, ikke en ekte dom — en test-fixture for porteføljekjøringen.
## Dommen
**Beslutning:** godkjent — med realiseringskorreksjon. Den modellerte besparelsen er
teknisk plausibel, men i drift realiseres erfaringsvis ~75 % fordi den antatte
affinitets-forenklingen overvurderer hvor mye tid pumpene faktisk kjører på redusert turtall.