Paste a reading order below. Use plain text in the format described in the instructions, or paste JSON exported from this app. To build one, copy the instructions into a new Claude chat, then ask Claude to build or fix a reading order for a character. Claude researches it across two reference sites, applies this app's era, event, and formatting rules, and hands back plain text in the exact syntax the box below expects. Paste that answer straight in.

Optional. Select a file below and the pasted eras and entries will be added to it instead of creating a new one. Existing entries and your progress stay untouched.

Work in this order, and don't skip straight to writing the list from memory. Keep this lean: two sources, not a research project.

1. Primary source: comicbooktreasury.com. Find the character or team's reading order page. Use its structure, meaning which issues it groups into which omnibus or trade paperback collections, as the backbone for the era breakdown and sequencing. This is the starting draft.

2. Merge in what's missing from comicbookreadingorders.com. Pull that site's order for the same character/run and diff it against the comicbooktreasury-based draft. comicbooktreasury tends to lag behind on recent releases and ongoing series, so treat comicbookreadingorders as the more current source: fold in anything it has that comicbooktreasury is missing. This is the only other source to check. Don't pull a third or fourth site just to be safe.

3. Only search again if about to assert a specific superlative or "definitive" claim in a note, such as "issues #225–232 are Armor Wars." Do one targeted search when such a claim is actually being written, not a standing third cross-check of the whole file.

4. After any edit that adds or moves content, re-verify the whole file's chronological order end-to-end. It's easy to strand a block in the wrong place, so this is a read-through, not a new search.

Every reading order needs a PUBLISHER: line, a single value for the whole case file (e.g. Marvel, DC, Image, Dark Horse), not per issue. New files should always include it right after SUBTITLE. When editing an existing file that doesn't have one yet, add it as part of the edit, even if not asked. If a character genuinely spans more than one publisher, use the majority publisher and note the exception in a NOTE: line.

ERA names describe what happens in the story (e.g. "Confronting a Legacy of Harm"), never the comic title, volume number, or writer's name.

EVENT names can just be the event's real name (Civil War II, Secret Empire, etc.). No rewording is needed.

Never reopen the same EVENT name multiple times to interleave it with era content. Keep the whole event as one contiguous block, or accept split cards, but not both.

Only split when the reader picks up a different comic title. Never split a single series just to name a single-issue "first appearance." Fold that into the surrounding run's description instead.

Split every different title within a crossover's tie-in list. Use one line per title, even if minor.

Consolidate consecutive same-title ranges, even across a small numbering-quality gap, but don't paper over a real renumbering jump (like legacy numbering) by pretending the range is continuous.

Zero blank lines anywhere. Even one becomes a phantom "---" checkable entry, so never use a literal "---" as a separator either.

EVENT lines support exactly one | field. Extra context can't be stuffed in via a second pipe, so use a standalone NOTE: line instead.

Every entry needs a description. Bare titles aren't allowed.

No ⭐ KEY or star emoji. A leading * on an entry line still marks it a key issue in the input format. The app folds that into the note text automatically ("...Key issue in this reading order."). Don't add star characters or "KEY" flags manually.

This is the same syntax used when pasting a new file into the app:

CHARACTER: required, first line. SUBTITLE: optional. PUBLISHER: required. ERA: name | years starts a new era. Plain line Title | note is a normal entry (note required). Leading * marks a key issue. NOTE: text is a standalone callout. EVENT: name | note followed by > Title | note lines groups a crossover's tie-ins. Only one | field is allowed per EVENT line.

Re-run the research process above rather than patching only the flagged section, since there may be other issues nearby the person hasn't noticed. Preserve entry titles as closely as possible so read/unread progress (keyed off issue title text) carries over. Don't casually reword titles that don't need it. Add a PUBLISHER: line if the file doesn't already have one. End with the full end-to-end chronological re-verification pass.