JournalShift
JournalShift is a tool-augmented agentic app: two Opus 4.7 agents running on Anthropic's Managed Agents platform, a Smart Journal Finder that queries OpenAlex, Crossref, and SCImago to rank candidate journals, and a Temp
Core trick
Ranks journals via OpenAlex, Crossref, and SCImago queries, then mechanically rewrites LaTeX structure to the target template without altering text.
Description
JournalShift is a tool-augmented agentic app: two Opus 4.7 agents running on Anthropic's Managed Agents platform, a Smart Journal Finder that queries OpenAlex, Crossref, and SCImago to rank candidate journals, and a Template Adapter that mechanically rewrites the LaTeX against the user-supplied target template, drive a deterministic Python pipeline that turns a manuscript into a submission-ready package, with Haiku 4.5 handling smaller single-shot tasks (LaTeX preamble repair, reviewer rationale, soft-rule compliance, readiness notes).
README excerpt
# JournalShift **A multi-agent Python pipeline that converts a LaTeX manuscript into a submission-ready package for a target academic journal — without touching a single scientific claim.** --- ## Problem Every academic journal has its own submission rules: section order, section names, reference style, word limits, required statements, a specific LaTeX template. When authors re-target a manuscript — typically after a desk rejection or a change of strategy — they spend hours hand-rewiring structure that adds zero scientific value. ## Why this matters - **Friction kills throughput.** Re-targeting a paper takes half a day per journal and is pure yak-shaving. - **Mistakes cost desk-rejections.** Missing a required section or a citation-style rule can bounce the submission before review. - **Scientific content must not move.** Any tool that touches the paper has to *prove* it did not alter numbers, citations, or claims. ## What JournalShift does JournalShift takes a LaTeX manuscript and a target journal and emits a clean submission package: a transformed `.tex` in the target publisher's skeleton, a compliance report, an audit report that verifies content preservation, a checklist of author TODOs, a cover letter, and a zipped bundle — all under `outputs/`. **What it does not do:** generate scientific content, rewrite claims, change numbers, fabricate citations, or submit to a journal portal. ## Key pipeline steps 1. **Parse** LaTeX → structured `PaperModel` (title