public-domain-epub-pipeline

name	public-domain-epub-pipeline
description	Use when creating, reviewing, or maintaining public-domain book translation projects and EPUB pipeline templates in this repository. Follow multilingual, language-pair-specific, rights-aware workflow rules.

Public-Domain EPUB Pipeline Skill / 公版书 EPUB 流水线 Skill

Use this skill when an AI agent is asked to create a book project, add or update a language-pair template, revise prompts, review policy documents, or build EPUB output in this repository.

当 AI agent 被要求创建书籍工程、新增或更新语言方向模板、修改 prompt、审查政策文档或构建 EPUB 时，使用本 skill。

Core Workflow / 核心流程

Canonical translation-unit gate / Canonical 翻译单元门禁

For new or migrated translation projects, treat translation_units/ as the only authoritative source-target store. Lock the full-source proper-noun discovery manifest, candidate decisions, entity_id register, occurrence ledger, terminology, and translation contract before parallel translation. When the user does not choose a proper-noun display mode, policy 3 is allowed only with selection_source=default; it never waives discovery or review. Translators write {{pn:entity_id}} templates in worker-owned chapter patches, and the single CAS merger renders names from locked CSV data. chapters/translated and chapters/final are deterministic identical-target projections and must not be edited independently.

新建或迁移翻译工程时，translation_units/ 是唯一权威 source-target store。并行翻译前必须锁定全书专名发现 manifest、候选裁决、entity_id 注册表、occurrence ledger、术语和翻译合同。用户未选择专名显示方式时可用策略 3，但必须记录 selection_source=default，且仍须完成发现与复核。译者只在自有章节 patch 中写 {{pn:entity_id}} 模板；唯一 CAS 合并器只从锁定 CSV 渲染名称。chapters/translated 和 chapters/final 是目标文本完全一致的确定性投影，不得分别手改。

For long-book parallel work, read references/adaptive_parallel_orchestration.md, run the weighted planner, and use Scheme B: disjoint translation producers, independent chapter audit consumers, and one coordinator/merger. Never infer capacity from page count alone. Unknown or unauthorized client capability means zero spawned workers. GPT-family clients may spawn at most four workers and non-GPT clients at most eight; start with no more than two and scale only after the pilot satisfies the recorded structural, proper-noun, semantic, rework, and conflict thresholds. A reviewer must not be that chapter's translation owner. Different chapters use chapter-scoped CAS and audit invalidation; same-chapter stale patches still fail.

长书并行工作必须读取 references/adaptive_parallel_orchestration.md、运行加权规划器并采用方案 B：互不重叠的 translation producer、独立 chapter audit consumer 和唯一 coordinator/merger。不得只按页数推断并发。客户端能力未知或未经用户授权时派生 worker 为 0；GPT 家族最多 4 个，非 GPT 最多 8 个；首轮最多 2 个，只有 pilot 达到结构、专名、语义、返工和冲突阈值才扩容。reviewer 不得是该章 translation owner。不同章节使用按章 CAS 和局部审计失效；同章陈旧 patch 仍必须失败。

When the active client exposes safe subagent creation, its coordinator must populate the capability file from live tool/model metadata, run npm run translation:orchestration:plan, and create no more workers than the resulting spawned_worker_count. Keep the returned task/agent IDs in run evidence and enforce the planned producer/auditor roles. Re-run the planner after the pilot, rate-limit changes, budget changes, or quality regressions. If the client cannot create workers, continue serially; do not emulate parallel writes with uncontrolled processes.

活动客户端具备安全子代理创建能力时，coordinator 必须依据实时 tool/model metadata 填写能力文件，运行 npm run translation:orchestration:plan，且实际创建数不得超过 spawned_worker_count。返回的 task/agent ID 必须进入执行证据，并严格执行规划中的 producer/auditor 角色。pilot 完成、限流变化、预算变化或质量退化后必须重跑规划器。客户端不能创建 worker 时应串行继续，不得用不受控进程模拟并行写入。

For bilingual editions, one complete source short paragraph must be followed immediately by its complete target paragraph. A unit may split one long natural paragraph only at complete-sentence boundaries; it must never cross two source natural paragraphs. Sentence-by-sentence subtitles, viewport/page chunking, or several source units followed by a target-language batch are release blockers. Structural PASS and EPUBCheck never substitute for hash-bound semantic omission/addition/neighbor-boundary audits.

双语版必须是“完整源语短段后立即跟随该段完整目标语译段”。长自然段只能在完整句群边界内部拆分，绝不跨两个源自然段。逐句字幕、按视口/页面聚块、连续多个源语单元后集中目标语都属于发布阻塞。结构 PASS 与 EPUBCheck 不能替代绑定 hash 的遗漏、增译和邻段串译语义审计。

Ordinary translation and builds use full-book static DOM/text/order/navigation checks and EPUBCheck only. A real-reader smoke test is attempted only for the final release candidate. If no supported reader is installed, record SKIPPED_UNAVAILABLE, allow release, and disclose the unverified boundary to the user; never skip the static gates.

普通翻译和构建只运行全书 DOM/文本/顺序/目录静态检查与 EPUBCheck。真实阅读器只在最终发布候选阶段尝试；未安装受支持阅读器时记录 SKIPPED_UNAVAILABLE、允许发布并向用户披露未验证边界，但不得跳过静态门禁。

1. Read AGENTS.md. 先读取 AGENTS.md。
2. Before doing any repository task, read the relevant template/ files. The template is the source of truth; do not rely on memory or prior runs. 执行任何仓库任务前，必须读取相关 template/ 文件。模板是规则源，不得依赖记忆或历史执行经验。
3. Read the repository README in the user's preferred language when available. 优先读取用户偏好语言对应的 README。
4. Read template/epub_pipeline/README.md. 读取 template/epub_pipeline/README.md。
5. For EPUB production, cover, book-info/frontmatter, assets, quality gates, random review, or release work, read the applicable common policy files before editing or building:
   • template/epub_pipeline/common/README.md
   • template/epub_pipeline/common/preproduction/stage1/_TEMPLATE.production_spec.md
   • template/epub_pipeline/common/references/cover_design_policy.md
   • template/epub_pipeline/common/references/book_info_frontmatter_policy.md
   • template/epub_pipeline/common/references/epub_assets_figures_tables.md
   • template/epub_pipeline/common/references/bilingual_parallel_edition_policy.md
   • template/epub_pipeline/common/references/adaptive_parallel_orchestration.md
   • template/epub_pipeline/common/references/quality_gate_framework.md
   • template/epub_pipeline/common/references/proper_noun_display_policy.md
   • template/epub_pipeline/common/references/note_marker_policy.md
   • template/epub_pipeline/common/references/release_versioning.md 涉及 EPUB 制作、封面、书籍信息页/前置页、资产、质量门禁、随机评审或发布时，编辑或构建前必须读取适用的 common policy 文件：
   • template/epub_pipeline/common/README.md
   • template/epub_pipeline/common/preproduction/stage1/_TEMPLATE.production_spec.md
   • template/epub_pipeline/common/references/cover_design_policy.md
   • template/epub_pipeline/common/references/book_info_frontmatter_policy.md
   • template/epub_pipeline/common/references/epub_assets_figures_tables.md
   • template/epub_pipeline/common/references/bilingual_parallel_edition_policy.md
   • template/epub_pipeline/common/references/adaptive_parallel_orchestration.md
   • template/epub_pipeline/common/references/quality_gate_framework.md

Policy Boundary Lessons / Policy 边界教训

• Read cover_design_policy.md and book_info_frontmatter_policy.md separately. Do not merge them from memory.
• 必须分别读取 cover_design_policy.md 与 book_info_frontmatter_policy.md，不得凭记忆把两者合并。
• Covers use the concise producer line LifeBook 书坊 译制. Personal contributor names belong in book-info.xhtml and metadata only when the book-info policy requires them.
• 封面使用简洁署名 LifeBook 书坊 译制。个人贡献者名只在书籍信息页 policy 要求时进入 book-info.xhtml 和 metadata。
• Before asset or publication lint, remove or rebuild stale staging output so old XHTML and old asset links cannot affect the new result.
• 运行资产检查或出版检查前，应清理或重新生成旧的 staging 输出，避免旧 XHTML 和旧资产链接影响新结果。

Structural Translation Coverage / 结构性译文覆盖

• Treat large-chapter shrinkage and note loss as pipeline defects, not as model-style problems. The durable fix is a deterministic coverage gate, not a one-off prompt reminder. 大章后段缩水和注释丢失应视为流水线缺陷，不是单纯模型风格问题。长期解决必须依靠确定性覆盖门禁，而不是一次性 prompt 提醒。
• check_translation_coverage.py is the shared gate. It checks matching chapter filenames across chapters/src/, chapters/translated/, and chapters/final/. It fails on low paragraph-block coverage, low non-space character coverage for long chapters, note reference/definition loss, unresolved target note references, and lost table/image/formula units. check_translation_coverage.py 是共享门禁。它按同名章节对比 chapters/src/、chapters/translated/ 和 chapters/final/。若段落块覆盖率过低、长章非空白字符覆盖率过低、注释引用/定义丢失、译文注号没有定义，或表格/图片/公式单元丢失，必须失败。
• preflight:template and check:chapter-controls must include this gate. If an Agent writes a PASS chapter control while the coverage gate fails, the PASS is invalid and the chapter must return to translation or reconstruction before any EPUB build or release. preflight:template 和 check:chapter-controls 必须包含该门禁。若 Agent 写出 PASS 的章节 control，但覆盖门禁失败，该 PASS 无效；章节必须回到翻译或重组后才能进入 EPUB 构建或发布。
• For very long chapters, split translation work into stable paragraph or small-block units and keep notes with the relevant unit or a dedicated note unit. The final merge must not proceed until every unit and note definition has a target counterpart. 对超长章节，应按稳定段落或小块单元翻译，并让注释跟随相关单元或独立注释单元。所有单元和注释定义都有对应译文前，不得合并为终稿。

Language Requirements / 语言要求

• Important human-facing files must include the local language for the intended contributors.
• 面向人的重要文件必须包含目标贡献者能读懂的本地语言。
• English may be included in parallel as a bridge language, but English-only important instructions are not acceptable unless English is the template's contributor language.
• 英文可以作为桥接语言并列出现，但除非英语就是该模板贡献者语言，否则重要说明不能只写英文。
• For English-to-Japanese, use Japanese plus optional English. For German-to-Traditional-Chinese, use Traditional Chinese plus optional English. For French-to-English, English is acceptable.
• English-to-Japanese 使用日文，可并列英文；German-to-Traditional-Chinese 使用繁体中文，可并列英文；French-to-English 可使用英文。
• Shared repository-level documentation should include Chinese when project-owner review is expected.
• 需要项目发起者审阅的共享仓库级文档应包含中文。

Hard Stops / 必须停止的情况

• Rights or public-domain status is unclear.
• 版权或公版状态不清楚。
• The only available source is a modern copyrighted translation or unclear commercial EPUB.
• 唯一来源是现代受版权保护译本或来源不明的商业 EPUB。
• The current working directory is still under template/ while book-specific output is about to be written.
• 当前目录仍在 template/ 下，却准备写入具体书籍产物。
• A pretranslation report, chapter gate, EPUB validation, stratified random spot-check, closure validation, independent review, or PASS release gate fails.
• 预翻译报告、章节门禁、EPUB 校验、分层随机抽检、闭环校验、独立评审或 PASS 发布门禁失败。
• Publication lint reports hard errors such as mojibake, legacy print page-number tables, abnormal spacing, or target-language punctuation violations.
• 出版文本 lint 报出硬错误，例如乱码、旧纸书页码目录、异常空格或目标语言标点违规。
• Long printed-TOC chapter titles are still being used as EPUB navigation labels without title design.
• 旧纸书目录式长章节标题仍被直接用作 EPUB 目录题名，尚未完成标题设计。
• Source-language names or parenthetical originals appear in translated chapter titles, subtitles, or navigation labels where the target-language title should stand alone.
• 译文章节标题、副标题或目录题名中出现原文人名或原文括注，而目标语言标题本应独立呈现。

Public Policy / 公开政策

• Non-code book content is publicly licensed under CC BY-NC-SA 4.0 unless a file says otherwise.
• 非代码书籍内容默认按 CC BY-NC-SA 4.0 公开授权，除非文件另有说明。
• Third-party commercial use requires separate permission from LifeBook Shufang and relevant rights holders.
• 第三方商业使用必须另行取得 LifeBook 书坊及相关权利人的授权。
• Contributor rules are defined in license/CONTRIBUTING*.md.
• 贡献者规则见 license/CONTRIBUTING*.md。