About
What this is
The Shimotsuki Codex is a free fan reference for One Piece — not a wiki. The Fandom wiki is a useful starting point, but it carries speculation creep, edit wars, and circular citations. The Codex is the verification layer: every claim traced to a primary source, every fact stamped with a trust tier so you always know what you're reading.
28+ years of canon across 1,181 chapters and nearly three decades of SBS, cross-referenced in one place. Characters link to crews, fruits, weapons, family trees, birthplaces, and voice actors. Each fact points back to the chapter or SBS volume that establishes it.
Status legend: Live stable · Maturing works but rough edges · Planned on the roadmap
- Chapter Atlas Live — every character's appearances across all 1,181 chapters
- Story Arcs Live — 33 arcs grouped by saga, click to filter the Atlas
- Timeline Live — vertical scroll through every saga with notable canon events
- SBS Vault Live — every Q&A Oda has ever answered, searchable, with auto-linked references
- SBS by Topic Live — same Q&As bucketed by subject for faster browse
- Punk Records Live — 1,537 characters with portraits, stats, cross-links
- Devil Fruit Codex Live — 155 fruits, type-coded, user-cross-linked
- Bounty Wall Live — every Marine bounty as a pinned wanted poster on a corkboard
- Locations Live — 139 locations with born-here character counts and arc cross-links
- Ships Live — 41 named canon ships with crew rosters from the sails-on graph
- Crews & Organisations Live — 357 factions with member rosters
- Family Trees Live — 52 hand-curated bloodlines with chapter citations
- Theory Forge Maturing — top fan theories weighed against actual canon. Verdicts need human review; suggestions welcome.
- Theory Workbench Maturing — build your own theories with cited Fact Cards. Suggestion tools are early.
- Prove an Idea Maturing — claim tester returns CONFIRMED/LIKELY/UNKNOWN/CONTRADICTED with evidence. Coverage gaps remain.
- Canon Density Heatmap Live — every chapter colour-graded by how many verified facts attach to it
- Cover Compendium Live — the mini-arcs Oda runs on chapter title pages
- Trivia Trial Maturing — quiz generated from the appearance data + curated trivia. Difficulty tuning ongoing.
- Spoiler-aware reading Live — mark your current chapter; the Codex blurs anything past it until you click to reveal
- Per-page expand/collapse memory Planned — your view preferences (broad vs. expanded) saved per surface
- Anime cross-reference Planned — episode-by-episode mapping (currently arc-level only)
Built by Shimotsuki Kajiya, with Claude as pair programmer. Forging clarity from chaos.
The Canon Engine — trust tiers
Five tiers, each with its own visual treatment so the trust level is readable at a glance:
- 🟢 Canon — Oda direct (SBS, manga panel, Vivre Card)
- 🔵 Highly likely — multiple secondary sources agree, no contradiction
- 🟣 Speculation — one secondary source OR fan-derived; consistent with canon but unverified
- 🟠 Rumour — Reddit theory / fan analysis without Oda backing
- 🔴 Disproven — contradicted by a higher-tier source (kept on record)
In SBS Q&As and theory bodies, recognised references auto-link with a colour that tells you who said the surrounding sentence: Oda's words get gold, a reader's question stays neutral grey, and a theorist's claim reads as ink-blue speculation. A link is navigation — not endorsement of the surrounding sentence. See canon-policy.md and canon-engine-roadmap.md for the rules in detail.
Spoiler Shield
Set your reading cutoff (chapter or episode) in Settings — every data-driven panel across the site filters its content to that point. Character lists, devil fruit users, theory verdicts, family trees, debut chapters, voice-actor assignments: all tier-aware and respect your cutoff.
Where it's strongest: data pages (characters, fruits, crews, theories, atlas, heatmap) — the shield filters by chapter at the data layer, so future-arc names never appear. Where it's lighter: curated lore essays (Void Century, Will of D., Haki, etc.) have prose paragraphs that discuss revelations by chapter range; the related-character lists at the bottom of each essay do respect your cutoff, but the body text itself may name late-arc revelations. If you're avoiding mid-Wano-and-later spoilers, lean on the data pages and skip the essays until you're caught up.
Search and listings: character lists and search respect your reading cutoff once you've set one. If you haven't set a cutoff yet, results aren't filtered — so a cold search for a late-arc character can spoil. Set yours in Settings to switch filtering on. Tightening this for un-onboarded visitors is a known item on the post-launch list.
Coverage notes
The Codex covers everything that exists — but a few notable gaps in the source material itself:
- Volumes 11, 26, and 46 have no SBS — Oda took breaks those weeks (Going Merry blueprints, the international editions feature, and Thousand Sunny blueprints respectively).
- Spa Island isn't on the Cover Compendium — it's a non-canon anime arc, not one of Oda's manga cover stories.
- Theory Forge currently holds 94 (and growing) of the most-upvoted r/OnePiece theories. Submissions welcome via GitHub issues.
How it works
- Chapter Atlas — pulls character appearances from the Fandom wiki via MediaWiki API. Visualises every chapter as a coloured square; click any character to highlight every chapter they're in.
- SBS Vault — scrapes Oda's "Question Corner" sections from the wiki, parses Q/A pairs, extracts inline images and reader pen names, and categorises every entry via Claude Haiku.
- Theory Forge — pulls top fan theories from r/OnePiece, then for each theory searches the SBS archive for relevant Oda quotes. Those quotes are passed to Claude as authoritative canon, which then issues a verdict (active/confirmed/debunked/partial) and cites the SBS volume directly.
- Trivia Trial — generates trivia questions from the same appearance data + a curated trivia pool of devil fruits, epithets, and lore facts.
Every page is a static HTML file with all data baked in. Hosted free on GitHub Pages. No backend, no database, no tracking, no signup.
Credits & data sources
- One Piece
- Created by Eiichiro Oda, published by Shueisha. All canon belongs to him.
- SBS Translations
- Scraped from the One Piece Fandom wiki, which sources many translations from Library of Ohara by Artur. Go support him.
- Theory Source
- Top-voted threads on r/OnePiece — pulled with quality gates (300+ upvotes, real reasoning).
- Canon Research
- Grand Line Review by Liam — deep canon analysis videos referenced when curating the Will of D., Void Century, Joy Boy, and the Ancient Kingdom pages.
- World Map
- For the canonical, interactive One Piece world map, see Artur's Interactive One Piece World Map (Library of Ohara, May 2026) — five years of careful research from Oda's own sketches. The Codex's world-map.html is a simplified at-a-glance schematic and points readers to Artur's work for the deep dive.
- Cover Art & Images
- Tankoubon covers and SBS images from the Fandom wiki. Used for educational/identification purposes under fair use.
- AI Analysis
- Powered by Claude (Haiku 4.5) for SBS categorisation and theory verdicts.
- Built by
- Shimotsuki Kajiya · 2026 · with Claude as pair programmer
- Source code
- github.com/ShimotsukiKajiya/one-piece-chapter-map — MIT licence
- Contact
- shimotsukicodex@proton.me — for things that don't fit a GitHub issue
How to contribute
Found an error? Want to suggest a theory? Spotted a missing SBS Q&A? All contributions go through GitHub Issues — just pick a template:
Wrong text, wrong volume, missing Q&A, miscategorised — all welcome.
Open SBS correction →
Got a theory that should be tracked and verified? Submit it here.
Suggest a theory →
No GitHub account? Reach out via the social links at the bottom of this page — Bluesky, X, or Reddit DMs all work. We'll add your contribution to the queue manually.
Help shape what's next
The Codex is a community-driven reference, not a finished product. The Maturing and Planned entries above are where input matters most — what would make them sharper, what's missing, what would you actually use? Tell us what to build next, what existing surfaces feel rough, or what conventions need rethinking.
Anything from a small UX tweak to a whole new surface.
Suggest a feature →
Found a Maturing surface that feels half-baked? Specifics help us prioritise — which page, what about it, what'd be better.
Send UX feedback →
Privacy
No accounts. No tracking. No cookies set by this site. No analytics.
Your settings, favourites, and search history are stored in your own
browser's localStorage and never leave your device.
This site loads images from the One Piece Fandom wiki and reader avatars from this repo. That's the only passive network activity besides loading the page itself.
Submission forms. The Curate, Corrections, and Theory Workbench pages submit to GitHub Issues via the public GitHub API. If you choose to submit a correction or theory, your submission becomes a public issue on the project repo, attached to your GitHub identity if you are signed in. If you would rather stay anonymous, do not use these forms — read-only browsing collects nothing.
Legal
One Piece, all character names, story content, and artwork are copyright © Eiichiro Oda / Shueisha. This is a non-commercial fan project intended for education, archive, and discussion. No revenue is generated from this site, and there are no ads, donations, sponsors, or paid tiers.
Site code is licensed under MIT (see LICENSE). Curated reference data describes facts about the One Piece work; the underlying story, characters, and artwork remain copyright Eiichiro Oda / Shueisha. Images sourced from the One Piece Fandom wiki remain the property of their respective rights holders; Fandom community contributions are licensed CC BY-SA where applicable.
Takedown / Content Removal
If you are a representative of Shueisha, Toei Animation, or another rights holder and would like specific content removed, please open a GitHub issue on the project repository:
github.com/ShimotsukiKajiya/one-piece-chapter-map/issues/new →
To help us act quickly, please include:
- The full URL(s) of the content you want removed
- A short description of what should come down (whole page, specific image, paragraph, etc.)
- Who you represent and your basis for the request
We will respond and act in good faith within a reasonable timeframe. The maintainer monitors the repository directly; this is the fastest contact path.