Files
infospace-bench/docs/lefevre-epub3-validation.md

2.3 KiB

Lefevre EPUB3 Validation

Date: 2026-05-14

Source

Local source file:

/mnt/c/Users/bernd.worsch/Downloads/LefevreEdwin-ReminiscencesOfAStockOperator.epub

The EPUB is Project Gutenberg edition 60979, EPUB package version 3.0. The OPF metadata identifies:

  • title: Reminiscences of a Stock Operator
  • creator: Edwin Lefevre
  • subjects: Speculation, New York Stock Exchange, Investments
  • rights: public domain in the USA

Current Infrastructure Result

The current generic generator can initialize a disposable infospace from the file and run non-provider metrics:

  • disposable root: /tmp/infospace-bench-lefevre-583mopy_/infospaces/reminiscences-stock-operator
  • source chunks: 155
  • entities: 0
  • relations: 0
  • evaluations: 0
  • stale status: false
  • metrics snapshot: 5978ece0

The source-only metrics were:

  • redundancy ratio: 0.9225806451612903
  • coverage ratio: 1.0
  • coherence components: 155.0
  • consistency cycles: 0.0
  • granularity entropy: -0.0

Findings

The EPUB intake works mechanically, but it is not ready for a serious full-book OpenRouter generation run.

  • EPUB spine order is visible in OEBPS/content.opf, but current intake reads XHTML files by archive-name sorting.
  • Current titles mostly collapse to the same long Gutenberg page title instead of chapter labels such as I, II, and III.
  • Current intake includes non-body material such as cover/header/footer/license candidates unless the caller manually filters after import.
  • generate plan is not yet a compact cost/risk plan for a long book; a full all-stage run would imply hundreds of provider calls.
  • Resume state is run-level enough for the small generic path, but a long ebook needs chunk-level retry, stale, and skip policy.
  • Cross-chunk entity deduplication and merge/review policy are needed before a full narrative book becomes a coherent infospace.

Desired Readiness Bar

Before building the real Lefevre infospace with OpenRouter, the CLI should be able to show:

  • book metadata and selected source sections
  • body-only chapter order
  • stable chapter/chunk IDs
  • estimated provider call count and token/cost budget
  • selected chapter or chunk filters for smoke runs
  • deterministic fixture acceptance on a small Lefevre-like subset
  • optional live one-chapter smoke run with explicit provider/model/cost caps