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

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>

README.md

@@ -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

docs/2026-09-09-p7-forankrede-identifikatorer.md

@@ -116,11 +116,11 @@ tilbake.
 `generate._grounding_text(project, baseline, delivered)` komponerer på ÉTT sted:
 
 1. **`delivered`** — hva KALLEREN kan bevise at kjøringen fikk. `run_project` fyller den fra den
-   leverte rendringen (pre-pass-kuttet / bundle-pekeren / vegstiens hentede chunks) PLUSS den
+   leverte rendringen (pre-pass-kuttet / bundle-pekeren / referansestiens hentede chunks) PLUSS den
    navigerte basens `context_files` — **aldri `files`**, som er egenskapen som dropper
    `type: verdict`-laget på hvert nivå (MAJOR-3 N2 / S7a-3). Å grunne et forslag i en tidligere DOM
    ville rutet ExpeL-foldens eget materiale rundt sin egen gate;
-2. **prosjektets EGNE kostlinjer.** Vegstiens estimat ER prosjektet. **MÅLT:**
+2. **prosjektets EGNE kostlinjer.** Referansestiens estimat ER prosjektet. **MÅLT:**
    `_project_from_bundle` bygger `cost_items=()`, så denne kilden bidrar med INGENTING på
    bundle-stien og gaten forblir like skarp der fabrikasjonen ble målt;
 3. **baselinens koder når kjøringen er forankret.** Stage 0 har allerede dømt hver kode som når 0b

docs/invarianter.md

@@ -2761,8 +2761,8 @@
   kravbase bærer en kostbaseline. **Ordrens B1 sier: form 2/3 OG «står som
   `req_number`/`prosessnr` i toppnivå-frontmatter» → nekt.** MÅLT 15.09: kravbase C erklærer
   `seksjon: 10.4.1`…`10.4.4` og `req_number: Krav 10.4.3—2`, men **aldri den bare `10.4`** — den er
-  et seksjons-PREFIKS; og prosesskatalogen erklærer 2 727 `prosessnr` + 2 753 `seksjon`, hvorav **ingen**
-  er `1.10.4`, som står ÉN gang, som prosa: en henvisning til kapittel 1.10.4 i en annen
+  et seksjons-PREFIKS; og av prosesskatalogens erklærte `prosessnr` og `seksjon` er **ingen**
+  `1.10.4`, som står ÉN gang, som prosa: en henvisning til kapittel 1.10.4 i en annen
   kravstandard. **Den
   ordrede regelen fyrer altså på INGEN av sine egne kjent-positive.** KOMPLEMENTET fyrer på BEGGE,
   og lukker et hull `_ground_against_input`s egen docstring alt innrømmer skriftlig («it fails OPEN
@@ -2980,7 +2980,8 @@
   5/5/5/5/6, de to leverte energi-eksemplene 1 hver, MAJOR-4s avledning av det syntetiske K2-prisskjemaet 3),
   og det stoerste EKTE leverte prisskjemaet maalt er K2s `prissammenstilling-sheet-1.md` med 14
   prisede rader av 118 linjer — ingenting maalt naar vinduet; det finnes for den umaalte
-  prosesskatalog-formede mengdebeskrivelsen, der korpuset erklaerer 2 727 `prosessnr`.
+  prosesskatalog-formede mengdebeskrivelsen, der en katalog kan erklaere hundrevis av `prosessnr`
+  (den leverte syntetiske katalogen: 300).
   **`rejection_stage` er koblingen P21s «a4 5/5 paa stage0-baseline» hviler paa** og noekler paa
   delstrengen `cost baseline (` — hadde den nye klausulen flyttet den, ville hver stadium-0-nekt
   blitt omdoept til `other` i stillhet (M A7 → 2 roede, hvorav ett ELDRE uavhengig vitne).

src/portfolio_optimiser/okf.py

@@ -1229,8 +1229,8 @@ _FILTER_FIELDS: Final = ("req_number", "prosessnr")
 #: measured keys is the kø-(p) drift), plus ``seksjon``, which is the field that carries the BARE
 #: form-3 number on the requirement corpora and on the process catalogue (``seksjon: '10.4.3'``,
 #: ``seksjon: '11.11'``) while ``req_number`` carries the composed ``Krav 10.4.3—1``. MEASURED 15.09
-#: over the four bases delivered at the time: 553, 1 440 and 365 distinct declared numbers on the
-#: three requirement bases, 2 765 on the process catalogue.
+#: over the four bases at hand: every one declared hundreds of distinct numbers or more. The
+#: shipped synthetic process catalogue declares 306.
 #:
 #: NOT added to ``_FILTER_FIELDS`` itself, and that is deliberate: what a ``filter`` word searches
 #: is measured and gated (P18), and widening it would change ``total_matches`` for every navigator

src/portfolio_optimiser/validator.py

@@ -193,7 +193,7 @@ def baseline_from_project(project: Project) -> CostBaseline:
 #: schedule yields 3 - while the largest REAL delivered price schedule measured is K2's
 #: ``prissammenstilling-sheet-1.md``, 14 priced rows of 118 lines. Nothing measured reaches this
 #: window. It exists for the unmeasured bill of quantities that is priced BY process number, where
-#: the process catalogue measured during development declares 2 727 of them.
+#: a process catalogue can declare hundreds of them (the shipped synthetic catalogue: 300).
 _KNOWN_CODE_WINDOW: Final = 20
 
 
@@ -539,8 +539,8 @@ def _reference_refusal(grounding: Grounding, code: str) -> str | None:
       declares ``seksjon: 10.4.1`` … ``10.4.4`` and ``req_number: Krav 10.4.3—2``; the bare ``10.4``
       is a section PREFIX that occurs in 12 of 274 documents and is no document's own number;
     * ``1.10.4`` (the process catalogue, an across-bases run, ``validated``) is not one of the
-      catalogue's 2 727 ``prosessnr`` nor one of its 2 753 ``seksjon`` values. It occurs in ONE of
-      2 756 documents, as prose: a cross-reference to chapter 1.10.4 of a requirements standard.
+      catalogue's declared ``prosessnr`` or ``seksjon`` values. It occurs in ONE of the catalogue's
+      documents, as prose: a cross-reference to chapter 1.10.4 of a requirements standard.
 
     So the ordered rule fires on NEITHER of its own known positives. The COMPLEMENT does, and it is
     the better-grounded rule besides: ``_ground_against_input``'s docstring already admits that this
@@ -560,7 +560,7 @@ def _reference_refusal(grounding: Grounding, code: str) -> str | None:
     there. That is what leaves every pre-P20 fixture untouched rather than exempted.
 
     The message NAMES THE DENOMINATOR (ansikt 4, and Step 5 feeds it verbatim into the next
-    attempt): "not one of the 2 765 it declares" is actionable where "ungrounded" is not.
+    attempt): "not one of the N this knowledge base declares" is actionable where "ungrounded" is not.
     """
     if not has_requirement_form(code):
         return None

tests/test_named_known_codes_loadbearing.py

@@ -25,8 +25,8 @@ two shipped
 ``shared/examples`` baselines: 1 each; MAJOR-4's derivation of the synthetic K2 price schedule: 3),
 and the largest REAL delivered price schedule measured is K2's ``prissammenstilling-sheet-1.md`` at
 14 priced rows of 118 lines. Nothing measured reaches the window; it exists for the unmeasured
-schedule of an agreement priced BY process number, where the catalogue measured then declared
-2 727 of them.
+schedule of an agreement priced BY process number, where a process catalogue can declare hundreds
+of them (the shipped synthetic catalogue: 300).
 """
 
 from __future__ import annotations

tests/test_requirement_number_gate_loadbearing.py

@@ -17,8 +17,8 @@ toppnivå-frontmatter i minst ett av grunnlagets dokumenter" — refuse that. Me
 
 * the requirements base declared ``seksjon: 10.4.1`` … ``10.4.4`` and ``req_number: Krav
   10.4.3—2``. The bare ``10.4`` was declared NOWHERE — it is a section PREFIX;
-* the process catalogue declared 2 727 ``prosessnr`` and 2 753 ``seksjon``. ``1.10.4`` was NONE of
-  them: it occurred once, as prose, a chapter reference into ANOTHER standard.
+* ``1.10.4`` was NONE of the process catalogue's declared ``prosessnr`` and ``seksjon`` values:
+  it occurred once, as prose, a chapter reference into ANOTHER standard.
 
 The ordered rule therefore fires on NEITHER of its own known positives. The COMPLEMENT fires on
 BOTH, and it closes a hole ``_ground_against_input`` already admits in writing — "it fails OPEN …