Skip to content

Close out the PDF study with a one-page summary - #740

Merged
willhea merged 3 commits into
developfrom
pdf-study-closeout-min
Oct 4, 2026
Merged

willhea merged 3 commits into
developfrom
pdf-study-closeout-min

Conversation

@willhea

@willhea willhea commented Sep 30, 2026 •

Copy link
Copy Markdown
Collaborator

Closes out the PDF research with a one-page summary and retires the external-validity investigation as inconclusive. Supersedes #728 (the earlier closeout, which also published scored outputs and register entries).

What changes

  • Adds docs/research/pdf-backend-bakeoff/CLOSEOUT.md: what the PDF work demonstrated, what it observed on a bounded population, what it does not support, the reusable code, and one next product task.
  • Adds a four-line "Closed" pointer at the top of validation/README.md, the directory's "start here" document.

Documentation only. No code, probes, frozen inputs, thresholds, methodology or register entries change.

Why this replaces #728

#728 added metrics.json and register entries A57 to A62.4 alongside its closeout. Those carry per-control answers from both adjudication routes keyed by blind ID, which join to the expected answers already public in control_fixtures.json, and they cannot be verified from public material because the oracle provenance is private. This version links to the existing public evidence instead and publishes no scores, blind identifiers or individual judgments.

It does not undo what the #728 branch already exposed, and it says so. All 20 adjudication controls are treated as retired.

Things a reviewer should check

  • No architecture recommendation is made. The document says so explicitly.
  • A frozen-rule conflict is named, not resolved. PRE-REGISTRATION §5.6 says an N-B control failure makes the run void; §7 Rule 3 says any control failure means the evidence is insufficient. Both lead to no architecture choice. The rules are not amended.
  • Every claim traces to an existing document (staffer-delivery/README.md, RESULTS.md and its audit, validation/). Nothing was re-measured for this PR; the Pyodide parity result cites its 2026-08-11 re-run with a negative control.
  • All relative links resolve, checked locally.

Next product task named in the document

Make the module-level pypdfium2 import in src/deltatrack/parsers/pdf_text.py lazy, so the engine loads under Pyodide without a stub. The XML path never calls PDFium, but reaches that import through module-level imports of parsers/pdf_anchors.py, at least from bill_tree.py and the canonical JSON formatter. Making the import lazy in pdf_text.py covers every route. Tracked in #751.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XmeDh5BVXMBkwZ7zCX1oca

Records what the PDF research demonstrated, what it observed on a bounded
population, and what it does not support, and retires the external-validity
investigation as inconclusive.

This is a replacement for the closeout proposed in #728, built from that
PR's base. It adds no scored outputs, register entries, blind identifiers or
individual judgments: those cannot be verified from public material and some
pair control answers with identifiers. It does not amend the frozen rules; the
§5.6 versus §7 disposition conflict is named and left open.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XmeDh5BVXMBkwZ7zCX1oca
willhea and others added 2 commits October 4, 2026 00:30
The next-task paragraph said the XML path reaches the module-level pypdfium2
import only through bill_tree.py. That was true when the delivery study
checked it, but the canonical JSON formatter now imports parsers/pdf_anchors.py
at module level too, so there are at least two routes. Every route ends at
pdf_text.py, so the recommended task, making that import lazy, is unchanged;
only the explanation was wrong. Links the task to #751.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XmeDh5BVXMBkwZ7zCX1oca
…he closeout

verify_parity.py --mutate returns 0 when it detects the injected mismatch
and 1 when it does not, so the reproduce step now says exit 0.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant