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

View file

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

View file

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