feat(p18): a listing is a WINDOW, and an invented path is refused by name
P18 part A (order 20260914T105139Z). P16 measured S7a-3's ladder against a delivered corpus for the first time and found two things fixture bases cannot show. (1) One level is not bounded by being one level. Measured 14.09 on the four mounted vegnormal bases: okf.directory_listing on krav/N200 is 169 974 chars over 1 132 documents, krav/N100 69 250 over 445, krav/N500 39 853 over 269, and R761's own root 110 912 over 2 728 SUBDIRECTORIES -- 27-113x the 1 500-char ceiling S7a-3 set, riding in every later prompt. That last number is why the window covers BOTH kinds: a pagination over documents only would have left the largest measured level unpaginated. read_dir now answers with a window. offset/limit page directories first then documents as ONE sequence (two independent windows make "the next ten" a question with two answers); total is the denominator and is always carried; limit is CLAMPED to 50, never refused. Default 10 chosen against the ceiling: one entry is 121-209 chars (median 145) over the four bases. After: n100 1 493, n500 1 453, R761 479, n200 1 537 -- 2.5 % over, stated rather than tuned away, because the ceiling is a character budget and the window is a count. Largest single call any caller can make: ~7 600 chars. filter narrows a level instead of paging it: case-insensitive SUBSTRING over title + req_number/prosessnr and over a directory path, answering with total_matches beside total. A substring and not a pattern for _ground_against_input's reason one rung down -- a form the rule does not know returns nothing, and an empty listing reads as "the base does not have this". A filter that matches nothing is an ANSWER (total_matches: 0), never a refusal. ORDER PREMISE FELLED before building on it: the order asks for a separate top-level reader "like own_frontmatter" because parse_frontmatter was last-write-wins -- P15 (f13dc64) already made a top-level key win, so BundleFile.frontmatter IS the concept's own value and a second reader here would be the second copy ko-(p) forbids. (2) 0 of 26 fasit concepts were opened in 32 read_file calls (the order's "24" is the four runs' DISTINCT paths, re-measured 14.09), and 10 of those calls named a path the base does not hold. Each reached the model as MAF's opaque "Error: Function failed." while counting toward the three consecutive tool errors that end a request. read_file now refuses such a path by name (BundlePathNotFound, funn-99 returned form) and names the nearest directory that actually HOLDS documents -- chosen off context_files, never the filesystem, because a directory can exist on disk and hold no navigated concept (read_dir would then refuse the very path the refusal handed back) and because context_files is what drops the type: verdict layer, so a refusal can never advertise by name the one layer no listing mentions. Narrow by construction: only an ABSENT path is translated; any other OSError propagates untouched. Two existing arms REWRITTEN, neither weakened: - test_a_nonexistent_sibling_is_still_an_os_error was a tripwire whose own docstring said "when it goes red, someone has closed it, and that is a decision to be recorded". This is the record. Its narrowness half survives as a new arm driving a real PermissionError on a file that IS there. - test_every_document_is_still_reachable_and_the_counts_add_up became STRONGER: the accounting must now page, so the same assertion also proves the window is complete and non-overlapping. tests/test_navigation_window_loadbearing.py: 13 arms. Arms needing the delivered bases SKIP with the root named (PORTFOLIO_VEGNORMAL_ROOT), as MAJOR-3's ceiling arm does; the window algebra, the filter negative and the refusal run over a synthetic base UNCONDITIONALLY, so the file can never be silently absent in full. Verification: uv run pytest -q 1672 passed / 5 skipped before the new file (1670 oncfd9079). ruff check + format clean, mypy clean (38 files). Golden demo-transcript.stdout BYTE-UNCHANGED, shasum -a 1 of the CONTENT = ea8c534773acdbe41ae68f2c55724d69aaf8be4f. No version bump, no push. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
cfd9079a4a
commit
9b47e5aa62
7 changed files with 634 additions and 42 deletions
18
README.md
18
README.md
|
|
@ -700,6 +700,24 @@ when the seam is detached, so the loop cannot silently degrade into theater.
|
|||
112 116 → 362 tokens for three bases, 124 942 → 21 448 for 171
|
||||
([report](docs/2026-08-26-katalogkostnaden.md)).
|
||||
|
||||
**Opening one level is bounded the same way (P18).** `read_dir` answers with a *window*: `total`
|
||||
says how many entries — subdirectories plus concept documents — the level holds, `offset`/`limit`
|
||||
say which of them you were given, and a `limit` past the maximum is clamped rather than refused.
|
||||
`filter` narrows a level instead of paging it: a case-insensitive substring over a document's
|
||||
title and reference number (`req_number` / `prosessnr`) and over a subdirectory's path, answering
|
||||
with `total_matches` beside `total`. A filter that matches nothing is an answer, never a refusal.
|
||||
Measured 2026-09-14 over four delivered bases, default listing of the largest level in each:
|
||||
`krav/N200` 169 974 → 1 537 characters, `krav/N100` 69 250 → 1 493, R761's root 110 912 → 479
|
||||
(its cost was 2 728 *subdirectories*, which is why the window covers both kinds), `krav/N500`
|
||||
39 853 → 1 453. The largest single call any caller can now make is ~7 600 characters.
|
||||
|
||||
A path the caller **invented** is refused by name rather than failing opaquely: `read_file` on a
|
||||
path the base does not hold answers `REFUSED (BundlePathNotFound)` and names the nearest directory
|
||||
that actually holds documents, so the next call has somewhere to go. Measured over the four paid
|
||||
runs of 2026-09-14: 10 of 32 `read_file` calls named such a path, and each previously reached the
|
||||
model as the framework's opaque `Error: Function failed.` while counting toward the three
|
||||
consecutive tool errors that end a request.
|
||||
|
||||
`--semantic-retrieval` (S3.1) is an **opt-in** ranking change, **off by default**. Off, prior
|
||||
verdicts are ranked exactly as before: a structural score over the affected cost-code set,
|
||||
measure type and magnitude bucket, with surface text deliberately excluded. On, that score is
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue