Typesetting · stage 11

Typesetting · stage 11

Turn approved author artifacts into a reproducible PDF submission bundle. The job is not merely to make LaTeX compile: preserve provenance, select a coherent engine/backend, preflight dependencies, compile to convergence, locate the first root cause, run profile-driven desk-reject checks, and hand exact PDF/page facts to venue-matching.

Read typesetting-resource-map.md before running a real build. Read references/build_contract.md before writing or consuming machine artifacts. Use references/latex_errors.md only after the first source-located error is known. Use a venue template under templates/ only when it matches the current author kit; the bundled copy is a starting point, not current venue truth.

Non-negotiable boundaries

• Consume citation delivery.json, references.bib and citekey-audit.json. Require delivery.status=DELIVERED, declared deliverable_hashes, empty citation failures and empty claim-review leftovers. Declared citation deliverables must be relative paths inside the citation delivery directory, and the build snapshot must preserve the audit, failure and claim-review sidecars under provenance. Check staged keys and compilation. Do not re-decide DOI existence, metadata conflicts, retractions or claim relevance.
• Consume figure files, declared dimensions/DPI and source manifest. Require the manifest to be light.figure_delivery.v1 or light.figure_build.v1 and require the embedded file hash to match a declared output hash. For empirical figure deliveries, require confirmed result-analysis evidence binding. Check presence, embedding, float/layout and compilation. Do not redo visual honesty, scientific content or publication-size generation.
• Consume the approved paper-writing manuscript. Do not invent claims, references, experiments or numbers to close a page budget.
• Take page, anonymity, template, font and page-box rules only from user input or current authoritative instructions with URL/date provenance. Never embed a universal venue limit.
• Keep tool/resource failure as UNAVAILABLE. Never call it manuscript ERROR, never call it PASS, and never mark the delivery DELIVERED.
• Keep stage-11 critical scope to typesetting. Security/network/tool unavailability does not enlarge it. ROUTES has no key 11; repair failures inside stage 11 and never invent a back-edge.