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

docs(s7a-3): ordrens ANDRE binding maalt paa alle 478 K2-nivaaer, og to prosa-hull lukket

Browse source 
Funnet i review foer lukking:

1. Rapporten baar rotnivaaets tall, men ikke ordrens andre klausul ("read_dir
   over stoerste katalog bundet"). Sveipet med den SHIPPEDE okf.directory_listing
   over alle 478 nivaaer: verste nivaa noe sted er 6 073 tegn / 2 094 o200k-tok
   (65 underkataloger) = 4,9 % av den flate formens 42 761. Det er dyrere enn
   rota fordi hver sti er bundle-relativ - den maalte prisen paa at en sti er
   brukbar ORDRETT i neste kall.
2. okf-konsum-kontrakter.md § 3.1 listet verktoeyene uten read_dir - samme
   Fase-3-klasse som verktoeybeskrivelsene pkt. 2 flyttet.
3. CLAUDE.md-raden tidde om at bundle_id_notice har TO kallsteder mens
   cost_baseline_notice har tre. Portefoelje-armen er BEVISST ikke wiret
   (bundle_id_source er None der ved konstruksjon), og det staar naa uttalt i
   stedet for aa vaere en asymmetri en leser maa gjette paa.

Sjekket ogsaa for annen prosa som beskriver den gamle to-trinns-stigen: eneste
gjenvaerende treff er docs/plan/2026-08-23-magentic-utforskningssloeyfe.md, et
DATERT plandokument som allerede beskriver read_bundle -> bundle_context (sant
til MAJOR-4 i oekt 77). Planer er historiske artefakter, ikke levende paastander
om flaten - ikke roert. Ingen treff under shared/ (pull-only subtree).

Ingen kodeendring.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-09-03 08:09:53 +02:00
commit 2954216114
2 changed files with 26 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/okf-konsum-kontrakter.md
View file

@ -124,8 +124,8 @@ That is a consumer refusing a producer's legitimate output over a directory name
directory, `ProvenanceStamp.bundle_id_source` / `DryRunReport.bundle_id_source` carry the whole
resolution into the artefacts, and the run prints **one warning line** naming both values.
- **A base is addressed by its declared id at BOTH doors.** The exploration catalogue
(`list_bundles` / `read_bundle` / `read_file` / `quick_validate`) and the mandate dispatcher
resolve the same id. This is a consequence of the slacken rather than a separate decision: while
(`list_bundles` / `read_bundle` / `read_dir` / `read_file` / `quick_validate`) and the mandate
dispatcher resolve the same id. This is a consequence of the slacken rather than a separate decision: while
a disagreeing declaration was refused the two could not differ, and if they differed now, an
exploration's own minted mandate would be unroutable.