rt-venue-reframe

name	rt-venue-reframe
description	Use after a rejection, or when switching target journals, to turn a manuscript framed for one venue into one framed for another. Produces a concrete reframing diff — introduction arc, contribution claim, evidence to add or cut, house style, format — by reading both venues' own packs. Complements rt-journal-match, which picks the venue; this one does the rewrite plan.

Cross-Venue Reframe (rt-venue-reframe)

rt-journal-match answers which venue next. This answers the question that immediately follows and that nothing else in the repository covers: what actually has to change in the paper.

Authors do this after almost every rejection, and they do it badly — usually by swapping the journal name in the cover letter and resubmitting. A real reframe is a diff across five layers, and both endpoints are already documented in this repo: the source venue's pack and the target venue's pack.

When to trigger

• A paper was rejected at venue A and the next rung is venue B.
• The author is choosing between two live targets and wants to know the cost of each.
• An editor or referee said "this reads like a paper".
• A paper written for an international venue is being re-aimed at a Chinese venue, or the reverse — the largest reframe distance in this repository.

Inputs

1. From venue and to venue — as venue_ids in venue-index.tsv. If the author only names a rejection, take the next rung from ladder.tsv — filter to same_discipline = yes and prefer high mentions, then sanity-check against rt-journal-match.
2. The manuscript — at minimum the title, abstract, intro, and the main table.