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

docs: general wording for the example-base document counts

Browse source 
Replace the exact document counts of earlier example bases (and the
per-base counts in the sources-format note) with general wording or
N-of-N in prose, comments and docstrings. Percentages and numerators
stay; no constant, assertion or test data changes.

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

10
src/portfolio_optimiser/stress.py
View file

@ -17,8 +17,8 @@ and the set's own ``mandate.json`` / ``fasit.json`` / ``bundle.txt``.
**THE ORDER'S (a) WAS VACUOUS AS WRITTEN, AND THE DEVIATION IS MEASURED, NOT CHOSEN.** The order
defines grounded as "a ``must_cite`` path was OPENED *or* CITED". But on the S2c navigation path
``run_project`` stamps ``citations = bundle_citations(bundle)``, which is one citation PER CONTEXT
FILE - the whole corpus. Measured on a requirements base during development: 446 context files,
446 citations, and **6 of 6 fasit paths already "cited" before a single model call**. A judge
FILE - the whole corpus. Measured on a requirements base during development: a few hundred context files,
as many citations, and **6 of 6 fasit paths already "cited" before a single model call**. A judge
honouring that literally would be a gate that can only be green - the repo's own vacuous-gate
class, inside the gate built to catch it. So a CITATION grounds an approach only when the citation
list is NARROWER than the base (a declared pre-pass cut, where the stamp really does name what was
@ -27,7 +27,7 @@ one fired stays readable.
**(b') was checked for the same vacuity and is CLEAN for the requirement bases, so the order
stands.** ``bundle_citations`` snippets are concept BODIES while ``ref``/``title`` live in
FRONTMATTER: measured 0 of 446 bodies of that base contain its ``Krav 4.1.2-1``.
FRONTMATTER: measured, not one body of that base contains its ``Krav 4.1.2-1``.
``named_in_measure`` / ``named_in_snippet`` are still reported apart, because the measure is the
model's own prose and a snippet is the base's.
@ -476,8 +476,8 @@ def score_context_set(
named_in_measure = any(m in measure for m in marks)
# P18/C2 (PM decision, P16 § 6.2): the snippet arm counts ONLY under a narrowed citation
# scope, exactly as (a) does. A whole-base citation list is stamped by ``bundle_citations``
# before a single model call — measured on a requirements base, 446 context files, 446
# citations, 6 of 6 fasit paths "cited" for free — so a mark found in THOSE snippets is
# before a single model call — measured on a requirements base, a few hundred context files,
# as many citations, 6 of 6 fasit paths "cited" for free — so a mark found in THOSE snippets is
# evidence about the base's contents, not about this run. Measured on a process catalogue:
# ``12.1`` appears in whole-base snippets and gave this row ``named`` without the model
# having said anything.