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

docs: neutral wording for the reference path and the catalogue counts

Browse source 
Say "referansesti" for the reference-project path in the P7 note, and
replace the declared-number counts of earlier example material with the
shipped synthetic catalogue's own (300 prosessnr, 306 declared numbers)
or a general wording. Comments, docstrings and prose only; no constant
or assertion changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-09-23 17:32:25 +02:00
commit 0b7c853f3d
Signed by: ktg
SSH key fingerprint: SHA256:JakMjO6FTBBzN0Bhfj9saOoEjaFxlSdYuZQQpM/lF9Q
7 changed files with 17 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -629,7 +629,7 @@ when the seam is detached, so the loop cannot silently degrade into theater.
`12.1`. When a run is **unanchored** — the knowledge base ships no cost baseline, so the
validator's stage 0 never runs — a cost code shaped like a clause number is refused unless it is
one of the reference numbers the base itself declares (`req_number`, `prosessnr`, `seksjon` in a
document's own frontmatter). The refusal names the denominator: *"not one of the 2765 this
document's own frontmatter). The refusal names the denominator: *"not one of the 306 this
knowledge base declares"*. A code the base does declare still validates, so a project priced in
real process codes is untouched; an input that declares no reference numbers at all cannot trip
the rule at all. `code_forms` reports the third value, `requirement`, for a code the base does