# Consecutive production pilot report

The fixed Pass 1 production pilot processed physical pages **41–60**, the first
20 content pages after the Book 2 divider. The range is wholly within Book 2,
does not overlap the 14-page evaluation set, and was not selected for unusual
cleanliness. Page 60 ends naturally in an entry that continues outside the pilot.

The page-by-page owner inspection entry point is
`pilot/runs/20260808T201223Z-pilot/review/index.html`. It presents the
authoritative scan beside the exact OCR, model candidate, deterministic reading
and diplomatic renderings, uncertainties, notes, continuation details, and raw
run artifacts. Previous/next links support a sequential read. Building or
viewing the bundle does not change review state.

The authoritative detailed report is beside it as `review/report.md`; the
machine-readable version is `report.json`. All pages remain unapproved
`model_candidate` / `diagnostic_only` material.

## Result

- 20 pages attempted; 20 valid candidates.
- 19 first-pass successes; one repaired success (page 43); zero failures.
- 13 reciprocal continuation links; zero unresolved declarations between the 20
  processed pages; zero exact duplicated-boundary findings.
- Three pages contain explicit low/unreadable readings: 43, 48, and 59.
- Exact TSV alignment was partial for 47 of 52 logical blocks and complete for
  five. No block was wholly unaligned. This secondary alignment did not block a
  page.
- The content-addressed page cache had zero hits on the new range. The interrupted
  run resumed three already-valid pages without another model call.
- Recorded page execution time totals 3,103.622 seconds (51.7 minutes), averaging
  155.181 seconds per page including page 43's repair. CLI usage fields are
  retained in the JSON report; they are not converted to API cost because this
  project uses ChatGPT-authenticated subscription execution, not API billing.

## Profile change and provenance

Pages 41–43 were produced with `gpt-5.6-sol` / `xhigh`. The owner then requested
the faster `gpt-5.6-luna` / `high` profile. The active page-44 Sol attempt was
interrupted before a response and archived with an explicit interruption record;
pages 44–60 were produced with Luna/high. The run manifest records both profiles,
Codex CLI 0.145.0, and per-page provenance. This is an operational latency change,
not a quality comparison, because the pilot has not been owner reviewed.

## Findings

Page 43's first schema-valid response represented a visibly erased, unreadable
span as an unreadable deletion. An over-strict deterministic invariant rejected
that legal representation and caused the one repair, which converted it to a
generic illegible span. The raw first response, failure, repair, and final
candidate remain preserved. The validator now permits unreadable additions and
deletions to retain their intervention type in future runs.

Page 48 retains the low-confidence visible reading `invitea`, with `invited` as
an alternative rather than silently normalizing a possible source typo. Page 59
retains a low-confidence `Mrs.` / `Mr.` alternative. Page 56 correctly preserves
the visibly printed `Friday, Jan. 29 - 1896` while separately inferring
`1897-01-29`; it also exposes a schema-policy question because non-textual
handwritten star/line/pointing marks can currently be described only in a layout
editorial note.

## Recommendation

The Pass 1 machinery is operationally ready for owner inspection: sequential
context, resume, attempt preservation, constrained output, validation,
reconciliation, duplication checks, and report generation all worked. It is
**not yet approved for corpus-wide processing**. The owner should review this
20-page package—particularly pages 43, 48, 56, and 59—and decide whether an
explicit graphical-mark representation is needed before authorizing the
remaining corpus.
