feat(propose,consume,profiles,importer): recovery yields to declaration, and 9 % of the corpus that was in no segment
One rule explains every remaining `pdf` miss on the twelve-position reference: where a document DECLARES headings, Arm D's RECOVERED headings are the whole of the excess, and every declared one is a unit the reference wants. `--outline-gate` admits recovery only where the document declares none of its own, plus any one recovered heading covering OUTLINE_SHARE (0.20) of the text. It is `fold_units` clause 2's own principle moved from voting to admission, and it filters at ADMISSION so the text a removed mark opened is carried by the mark above it -- the post-filter form scores identically on all twelve positions and loses that text, which is why only one of them shipped. `--outline-gate` and `--drop-wrapped-outline` become the package default, one decision because neither carries the reference alone: `pdf` 2 of 8 -> 5 of 8 alone, 7 of 8 together; the sheet 5 of 12 -> 10 of 12; `docx` unchanged at 3 of 3. Each keeps an explicit opt-out. The bar the move had to clear was not the reference: hit@8 on a K2 bundle built with it holds 5 of 6 at ranks 1,1,1,1,1,-, no row losing rank 1. `--sheet-section-rows --keep-table-heading` reaches 11 of 12 and does NOT ship, because on a bundle built with it row 1 falls rank 1 -> 2. Cost to a consumer is a re-run: 492 concepts / 944 files -> 425 / 810. DOCUMENT_PRIOR_EXPONENT makes the document prior sublinear (total/n**0.5). A sum measures size and a density is diluted by every unit carrying none of the question, so a document split 1 -> 12 lost its prior by 12. Swept over five values on 18 rows it is at least as good as the delivered density everywhere and strictly better on three. Stated plainly: end to end it moved NOT ONE hit@8 row on any of four bundles, so it did not solve the knot it was adopted for -- what did is that the `pdf` gain never needed `--sheet-section-rows`. `--first-span-from-zero` is off and repairs a measured loss found while chasing one position's 940 characters: 32 of the 32 documents that get a plan leave the text above their first concept in no segment -- 159 704 characters, 9.18 % of the corpus, 45 841 from one document. It changes nothing on the reference. Off because it moves the first span of essentially every bundle with no hit@8 number behind it yet. vegnormal-okf FUNN 2: SPEC section 8's own star row parsed as prose, so every concept behind one was unreachable to the section 9.2 walk. `IndexPolicy.also_reads` carries it for the SEGMENTED profiles, read-only, after the emitted pattern misses -- the asymmetry `sources` already has. DEFAULT and STRICT_V1 untouched (O2). vegnormal-okf FUNN 1: Door C's own outcome was refused at exit 1, `bundle_id_missing`. `import_bundle` now takes `root_frontmatter_values`, keyword-only, rendered before any disk mutation, written only when the index is created -- Door B's mechanism and ordering. Report: docs/2026-09-09-k3-runde6-outline-gaten-og-prioren.md. Suite 1478 passed (1449 before), ruff and mypy clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
b01492b7f5
commit
38104b7df5
16 changed files with 1301 additions and 42 deletions
|
|
@ -35,6 +35,7 @@ from typing import Protocol
|
|||
from .errors import IngestError, MaterializationError, SourceError
|
||||
from .extract import decode_text
|
||||
from .materialize import (
|
||||
_render_root_frontmatter,
|
||||
check_filename_length,
|
||||
link_in_index,
|
||||
parse_frontmatter,
|
||||
|
|
@ -363,6 +364,7 @@ def import_bundle(
|
|||
channel: str,
|
||||
gate: ImportGate,
|
||||
profile: BundleProfile = DEFAULT,
|
||||
root_frontmatter_values: Mapping[str, str] | None = None,
|
||||
) -> ImportResult:
|
||||
"""Merge the accepted concepts of an external OKF bundle (Door C).
|
||||
|
||||
|
|
@ -374,6 +376,21 @@ def import_bundle(
|
|||
INCLUDING a disposition this library does not recognise and a concept the
|
||||
gate returned no verdict for, fails closed.
|
||||
|
||||
`root_frontmatter_values` supplies the values for the keys the profile's
|
||||
index policy names, exactly as Door B's `materialize_bundle` does, and for
|
||||
the same reason: a profile names a key, the CALLER owns its value (E1).
|
||||
Without it this door's own outcome was not a readable bundle -- the root
|
||||
index carried no frontmatter, so it declared no `bundle_id`, and the
|
||||
reading direction refused it with `bundle_id_missing` because SS 3.1's
|
||||
identity is the `(bundle_id, concept_id)` tuple and half of it was absent.
|
||||
Reported by vegnormal-okf 2026-09-08 (FUNN 1), who worked around it by
|
||||
using this door as a gate and writing the consumable tree themselves.
|
||||
|
||||
Keyword-only with a default of `None`, so every existing call site emits
|
||||
the bytes it always did. The block is written only when the index is
|
||||
CREATED, which is `materialize_bundle`'s rule and is what keeps a second
|
||||
run into an existing bundle byte-identical to the first.
|
||||
|
||||
`profile` names the filename namespace this door writes into and the shape
|
||||
of the index it maintains. It is keyword-only and defaults to `DEFAULT`, so
|
||||
every existing call site emits the bytes it always did — a consumer with
|
||||
|
|
@ -388,6 +405,9 @@ def import_bundle(
|
|||
are wrong for every concept at once: an invalid `ingested_at`, an
|
||||
unrecognised `origin`/`channel`, and a missing source directory.
|
||||
"""
|
||||
# Before any disk mutation, like `materialize_bundle`: a caller naming a key
|
||||
# this profile does not carry must not leave a half-written bundle behind.
|
||||
root_frontmatter = _render_root_frontmatter(root_frontmatter_values or {}, profile=profile)
|
||||
validate_ingested_at(ingested_at)
|
||||
if origin not in _ORIGINS or channel not in _CHANNELS:
|
||||
raise MaterializationError(
|
||||
|
|
@ -541,7 +561,7 @@ def import_bundle(
|
|||
if merged:
|
||||
index_path = bundle / profile.index.name
|
||||
if not index_path.is_file():
|
||||
write_bytes(bundle, profile.index.name, "")
|
||||
write_bytes(bundle, profile.index.name, root_frontmatter)
|
||||
# Projected first, in merge order, so the report of what could not
|
||||
# be rendered reads in the order the concepts were merged. ORDERED
|
||||
# second, through the POLICY's helper — the same one Door B calls,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue