Editorial Standards

This page documents how recaps on AnimeRecap are produced, reviewed, and corrected. We believe readers should know where their content comes from.

AI-assisted, human-edited

First drafts of our recaps are generated with an automated pipeline that uses Anthropic's Claude language model. Every recap is then reviewed and edited by Hong-Bin Yoon, Founder of zzinDev LLC, before publication. No recap is published without human review.

We use AI assistance because it lets a small team cover more ground carefully — a model drafts a structured summary and a human reviews it — not because we think it replaces editorial judgment. The editorial judgment is the product.

What human review covers

  • Accuracy of plot details — cross-checked against AniList and MyAnimeList entries, and against our own familiarity with the show.
  • Character and studio names — spelled and credited correctly.
  • Spoiler tags — major reveals are placed behind explicit spoiler markers so a reader can control what they see.
  • Prose quality — trimmed for clarity, pacing, and tone.
  • Ratings — reviewed for sanity against the show's reception.

Sources

  • Show metadata (episode counts, airing dates, studios, genres): AniList GraphQL API.
  • Cross-reference metadata: Jikan (MyAnimeList).
  • Cover images and scene frames: official trailers and promotional art, used under fair use for commentary and criticism.

Originality

Our recaps are original prose. Major plot beats are inherently shared across all recaps of the same show — there's only one Attack on Titan — but phrasing, structure, editorial framing, and commentary are ours. We don't scrape plot wikis or rewrite other sites' recaps.

Ratings

Each season has a numeric rating from 0 to 10. The rating starts from AniList's community score at the time of writing and is re-evaluated during human review. Ratings reflect how we think the season landed, not just the show's popularity.

Corrections policy

If you spot a factual error, a misspelled name, or a misplaced spoiler tag, please let us know via the Contact page or the "Suggest an edit" link at the bottom of any recap. We aim to respond to factual corrections within 1 business day.

When we update a recap to fix an error, the "Last reviewed" date on the post is updated. We do not silently rewrite recaps to change their substance after publication.

Who to contact

Hong-Bin Yoon, Founder, zzinDev LLC — support@zzin.dev