Natively multilingual Unit
One work identity carries localized presentations, platform sources, canonical/variant records, and merge governance.
inherit · create · spread
Meet the stories you love.
Start with web novels scattered across platforms and languages. REZICS reconnects an original work and its localized presentations, serial sources, chapters, and communities as one evolving work.
01
A serial should not become fragments because of its platform, language, or translated title.
Readers are looking for the same story, yet today they must identify it again and again across platform pages, translated-title entries, progress tools, and discussion groups. REZICS reconnects them to one work identity first.
REZICSOne evolving work
Cross-platform sources
- Original serial platforms
- Translation and licensed sources
- Published and other editions
Original and translated names
Original title, romanization, and aliases
Official translated titles and customary names in each language
Serial updates
Sources continue to update; work identity does not need rebuilding.
Reading progress
Know where the work has updated to, and where you have read to.
Realm reader communities
Find people who want to discuss the work over time.
02
From finding a book to forming a work network that is hard to reproduce.
A 400,000-book launch catalogue solves cold start. What truly keeps accumulating is cross-platform identity, cross-language relationships, reading trails, and Realm community memory.
Find a work across platforms
Original titles, translated titles, aliases, and sources point to one identity.
Follow serials and progress
Know where to read, where updates have reached, and where you have read to.
Join or create a Realm
Find people who genuinely discuss the work over time.
Contribute sources and knowledge
Correct names, editions, relationships, and community content.
Improve search and recommendations
Every act of participation lowers the next reader's cost of searching.
03
Web novels are the entry point; the foundation is designed for every evolving work.
REZICS separates work identity, sources, content, structure, history, and communities into clear boundaries, then lets them cooperate through explicit relationships.
Content Structure
Chapters are reusable content; structure manages order, occurrence, and serial evolution.
Block Schema + Portable Text
Evolvable documents with type, key, and version semantics; rich text is not raw JSON.
Realms and shared memory
Communities do not own works, yet discussion, governance, and knowledge can accumulate over time.
Start with web novels and build a network where works and shared knowledge can be inherited, created, and spread.
A grand narrative must rest on verifiable foundations.
REZICS builds boundaries that can extend over time through open source, content documents with version semantics, publication licenses, and permissioned APIs. Product pages clearly distinguish what is available, in development, and planned.
Start with a web novel you are following.
Search for its original or translated title, save your reading context, and see whether someone has already created a Realm for it.
Have an idea you want to make real with us?
Whether it is a product collaboration, open-source participation, a content model, or any suggestion worth doing better, we would be glad to talk.