Persistent dev-fixture for energieffektivisering (energiledelse/M&V), valgt for sin lærings-overflate: gapet mellom modellert besparelse (validatoren regner) og faktisk realisert besparelse i drift (eksperten kjenner) — det ExpeL skal lære. Ett kontorbygg, ett LED-retrofit-tiltak. OKF-bundle (index/project/hypothesis/ methodology/reference/verdict) bærer kontekst-laget; verdict-led-fro.md koder realiseringsgraden (RR ≈ 0,82, forankret i National Grid SBS 2010) som ExpeL-frø. Energi mappet inn i den EKSISTERENDE kost-IR-en uendret (affected = byggets totale energikostnad, claimed = modellert besparelse ~10 % < 30 %-cap), så validatoren kjører som-den-er — src/ urørt. golden.json fryser de seeded percentilene; testen beviser at fixturen er konsumerbar (validerer, ikke Rejection), ikke bare til stede. Domenetall verifisert mot primærkilder (EVO/IPMVP, DOE/NREL UMP, CPUC, fire evalueringsstudier); norsk energipris mot SSB Q1 2026. README + shared/README oppdatert (eksempel finnes, ikke lenger "planned"). Suite 121/4, ruff+mypy rene. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MHR8iKxJRxDiDfNw8HZmWE
34 lines
1.8 KiB
Markdown
34 lines
1.8 KiB
Markdown
# shared/ — framework-neutral core
|
|
|
|
This directory holds the parts of the project that are **independent of any AI agent
|
|
framework** and are meant to be **shared, unchanged, between both reference
|
|
implementations**:
|
|
|
|
- **this repository** — the method built on Microsoft Agent Framework (MAF);
|
|
- **a sibling repository** (built later, in sequence) — the same method on the
|
|
**Claude Agents SDK**.
|
|
|
|
Sharing one identical core is what makes the two implementations a *fair comparison*:
|
|
both consume the same concept, the same example data, and the same expected outcomes,
|
|
so the only thing that differs is the agent framework itself.
|
|
|
|
## Contents (growing)
|
|
|
|
- [`CONCEPT.md`](CONCEPT.md) — the business concept, written for a non-specialist
|
|
(e.g. a business developer at another company).
|
|
- [`examples/bygg-energi-mikro/`](examples/bygg-energi-mikro/) — the first example knowledge
|
|
bundle (OKF / LLM-wiki): one office building, one LED-retrofit measure, with a seed expert
|
|
verdict encoding the realization gap and a golden-suite of expected validator outcomes. A
|
|
small **dev fixture** for exercising the agentic loop; a realistic full-scale example comes later.
|
|
- *(planned)* the method specification and the expert-reviewer persona.
|
|
|
|
## Rules
|
|
|
|
- **Nothing in here may import or depend on a specific agent framework.** If it does,
|
|
it does not belong in `shared/`.
|
|
- **Repo layout (decision R1, 2026-06-26):** the shared core lives here for now. When
|
|
work on the sibling repository begins, it will be extracted into its own repository
|
|
(e.g. `portfolio-optimiser-commons`) via `git subtree split`, and both implementation
|
|
repos will consume it. This defers cross-repo plumbing until it is actually needed.
|
|
|
|
See the target picture for the full architecture: `docs/plan/2026-06-26-maalbilde-agentic-loop.md`.
|