Shared knowledge need not be trapped in one page, language, or community
Readers are not trying to understand an isolated article. They are trying to follow a traceable network among a work, its people, places, and events. A wiki connects content back to real works and entities, so the same subject can be reached through a work page, a character relationship, a curated route, or another language.
A REZICS wiki therefore does not end at “an editable Post with history.” Editing and history are conditions that let shared knowledge remain understandable, correctable, and reusable over time.
One subject can share facts and still retain community context
Works and entities provide common reference points. A Realm preserves a particular community’s access rules, focus, and organization. Two communities can cite the same work while understanding it through different navigation, features, and explanatory contexts—without creating two work records that cannot recognize each other.
A Zone organizes related pages into an explorable knowledge entry, but it does not own the works it cites. The same knowledge content can be referenced across works or Zones, allowing the value of a correction to return to the wider work network.
The products that complete this experience together
- Posts carry attributable, multilingual knowledge instead of introducing a separate document format.
- Units and entity relationships connect pages to stable identities for works, people, places, and concepts.
- Zones provide subjects, navigation, and knowledge entry points that make pages explorable as a whole.
- Realms define publication context and access boundaries so a shared foundation can hold distinct communities.
- The editor, Content Structure, and history preserve continuously revisable documents and published versions.
Each of these serves other products independently. In a wiki, they combine into a maintainable, explorable knowledge environment that returns readers to real subjects.
A correction should return to the whole work network
When someone improves a character name, work source, or relationship, wiki entries, work pages, and community curation that rely on the same stable identity can all receive better foundations. Knowledge need not remain in a Zone-specific copy or restart because each community uses a different language.
Home filters, character tables, work timelines, and elaborate feature pages remain publishable content. Zones organize them; Posts and Block Schema carry them so they can be cited, revised, and reused.
Today’s boundaries and the next step
People can already create wiki-kind Portable Text Posts, connect them to works and entities, set Realm access contexts, manage wiki Zone navigation, and view published revisions. Fuller source citation, version discussion, collaboration permissions, entity-filter blocks, and mature templates remain in development.
A wiki is not a live whiteboard, and it does not turn every keystroke into formal history. It preserves knowledge changes worth publishing and tracing while reusing REZICS products for content, identity, community, and authority.