Skip to main content

Tags & Community Classification

Use one tag identity across global, Realm, and personal contexts, so classification can be voted on, governed, and reused across products.

Current statusAvailable

Tags, voting, Realm contexts, and basic structural management are available; complete hierarchy closure, tree filtering, and large-scale faceted projections are in development.

Core purpose

Terms such as “light novel,” “isekai,” “women’s fiction,” or “completed” help readers describe taste, but are not work identities. A tag is a localizable, reusable Unit that can be used across books, Posts, collections, Realms, and Zones.

Four contexts of use

  1. Global community votes collect platform-wide judgments about a tag’s applicability.
  2. Realm-context votes let a particular community express its own classification view.
  3. Realm policy tags are maintained directly by community governance for rules and curation.
  4. Personal tags serve only a user’s own organization and do not claim public fact.

What is available now

  1. Create multilingual tag identities and descriptions.
  2. Add, vote for, or withdraw tag judgments on works and content.
  3. Switch between global and Realm classification context.
  4. Create tag structures and manage membership relationships.
  5. Share vocabulary across work pages, search, Realms, and curation surfaces.

In development

Hierarchy reads currently follow accepted adjacent relationships. Search, feeds, and tree filtering need versioned hierarchy-reachability projections for consistent ancestor/descendant semantics at scale; each request must not perform unbounded recursive queries.

Relationships and boundaries

Tags are not folders, permission boundaries, series, or work identities. Facts expressible through an entity, series, release, or Realm relationship should not be reduced to an ambiguous tag.