open/llm-ingestion-okf
1
0
Fork 0
Code Issues Releases 4 Activity

docs(accounting): record the operator's two decisions of 2026-09-17

Browse source 
The content accounting stays OPT-IN until the losses it reports on the
reference corpus are fixed; a default-on door would fail builds that pass
today. Of the three exceptions the gate proposed, only the PDF one
(heading, paragraph, table) is approved. Approving it moves no number,
because no witness counts a heading in a PDF: what it changes is that the
gap is a stated limit of the instrument rather than an open question
about the build. An image in a workbook, or in md/txt/csv/json/odt/rtf,
stays unaccounted and therefore stays red.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-09-18 00:37:04 +02:00
commit 751441c17d
5 changed files with 50 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

19
tests/test_accounting_gate.py
View file

@ -380,8 +380,25 @@ def test_row6_without_its_source_is_red_locally_and_skipped_in_ci(tmp_path: Path
def test_the_proposed_exceptions_are_not_applied() -> None:
assert gate.APPROVED_EXCEPTIONS == frozenset()
assert "NOT APPROVED" in gate.render([])
assert not {suffix for suffix, _ in gate.APPROVED_EXCEPTIONS} & {
item["suffix"] for item in gate.PROPOSED_EXCEPTIONS
}, "an exception cannot be both proposed and approved"
def test_the_operator_approved_the_pdf_exception_and_nothing_else() -> None:
"""Operator 2026-09-17, answering the gate's three proposals: the PDF one
only. It moves no number -- no witness counts a heading in a PDF -- so what
it changes is that the gap is a stated limit rather than an open question.
"""
assert gate.APPROVED_EXCEPTIONS == frozenset(
{(".pdf", "heading"), (".pdf", "paragraph"), (".pdf", "table")}
)
assert [item["suffix"] for item in gate.PROPOSED_EXCEPTIONS] == [
".xlsx",
".md .txt .csv .json .odt .rtf",
]
assert gate.APPROVED_ON in gate.render([])
def test_bad_usage_exits_two() -> None: