Core purpose
A Realm is a long-term community built around a common interest, not merely a discussion board. It combines members, rules, publication and tag contexts, scores, wikis, feeds, Docks, and governance under an evolving Unit.
For example, around a web novel, the core product loop is to discover cross-language material, join or create a community, discuss it, correct source information, and leave knowledge for the next reader.
What is available now
- Create multilingual Realm identities, summaries, and public pages.
- Join, view members, and manage membership states.
- Publish Posts, collections, and other Units to a Realm feed.
- Set rules for member acknowledgement, content governance, and pending queues.
- Use policy tags, Realm tag contexts, classification trees, and score contexts.
- Provide wikis, navigation, pins, and configurable Docks.
- Switch between global and Realm context on Post detail pages.
Publication does not transfer ownership
Publishing to a Realm creates only a governable relation. A Realm can reject or hide that relation, add a status, or remove it, but it cannot delete the source Unit. Only content that a Realm directly creates or owns follows its ownership relation.
Membership does not currently provide an arbitrary role hierarchy. Management capabilities come from explicit Unit and access permissions together with governance rules. Documentation will not pretend that an unimplemented role system already exists.
In development
Full state history for Realm–Unit relations, annotations, granular notification preferences, custom taxonomy-label filtering, and cross-language governance remain in development. Automatically following a Realm after joining, and the scope of bell notifications, are important questions for later design.
Relationships and boundaries
A Realm is not a work classification, collection, or Zone. It is a community with membership and governance context. Zones organize particular surfaces inside or across products; collections are curated lists.