Nine kinds, one set of parts.

Books, anime, games, software, and MCP servers all use eight of the same fifteen parts.

Five gray sheets of different shades form a step, with five small colored sheets on top

Nine kinds

Choose a kind to see its eight parts.

Part names stay the same, but their role depends on the kind. Library editions mean translations and collections; game editions mean platforms and regions.

Choose a kind

Eight parts used by Library

  • Identity

    A work has one identity across languages and communities. An ISBN identifies one edition.

  • Editions

    Translations, reprints, paperbacks, ebooks, and collections are recorded as separate editions of the same work.

  • Credits

    Authors, translators, illustrators, and publishers are listed by role. A translator is the same person across every book.

  • Relations

    Series, sequels, side stories, and adaptations each have a relation type. Web versions and rewritten editions are connected too.

  • Progress

    Your book, page, and next read stay in sync when you switch reading languages.

  • Ratings

    Rate the story, translation, and narration separately, with the number of ratings and scope shown for each score.

  • Wiki

    The Wiki cites chapters for people, places, and events, and shows only what you have read.

  • Offers

    Buy ebooks from participating creators here. Sales information for other editions includes the date it was observed, or is marked unknown.

Eight parts used by Anime

  • Identity

    Names in every language point to the same anime. Adaptations and source works each have their own identity.

  • Schedule

    Record each season’s air dates and episodes on a schedule, with announcements, delays, and cancellations kept separate.

  • Credits

    Voice actors, characters, and works share one credit record. Directors, writers, and production companies have their own roles.

  • Relations

    Seasons, side stories, and source works have distinct relation types, so you can follow links back to the novel or manga.

  • Progress

    Keep track of the episode you watched and what comes next. Optional specials do not count toward completion.

  • Ratings

    The whole work and each episode have separate ratings, with the number of ratings shown.

  • Discussion

    Each episode has its own discussion, with content beyond your progress hidden by default.

  • Wiki

    The Wiki cites the episode for each person, place, and event, and shows only the episodes you have watched.

Eight parts used by Manga

  • Identity

    The original title, translations, and romanization all point to the same manga.

  • Editions

    Volumes, ebooks, new editions, and collections in each language are recorded separately, keeping their original volume numbers.

  • Credits

    Writers, artists, translators, and publishers are credited by role. An author’s novels and manga appear on the same page.

  • Relations

    Source novels, anime adaptations, side stories, and sequels have distinct relation types, so each can be found from the other.

  • Progress

    Track progress by chapter and see how many volumes you have read.

  • Ratings

    Rate the whole work, an individual volume, or a translation separately. Series ratings stay separate from volume ratings.

  • Discussion

    Every chapter has a discussion, with unread plot details hidden by default.

  • Offers

    Sales regions and prices for each language edition include the date they were observed.

Eight parts used by Games

  • Identity

    A game has one identity across platforms and regions. Remakes and reboots each have their own linked identity.

  • Editions

    Editions across platforms, regions, and languages are listed separately, along with DLC.

  • Credits

    Developers, publishers, writers, composers, and voice actors are credited by role. A creator’s books and games are connected.

  • Relations

    Sequels, side stories, adaptations, and mods have relation types that show what depends on what.

  • Specifications

    System requirements and supported languages are recorded by platform. Unknown and not applicable are distinct.

  • Ratings

    Ratings can target an edition on a specific platform. Any score across editions explains how it was calculated.

  • Discussion

    The game, DLC, and an edition on a specific platform can each have a discussion.

  • Offers

    Buy small games from participating developers here, alongside sales information from other stores.

Eight parts used by Software

  • Identity

    A software project has one identity across platforms and package repositories. Forks have their own entries, linked to their source.

  • Editions

    Keep every version number, release channel, and set of release notes, with older versions available too.

  • Specifications

    Record supported operating systems, processor architectures, and package dependencies for each version, with a source for each.

  • Credits

    Maintainers, development teams, and organizations each have an identity, with their projects listed on the same page.

  • Ratings

    Rate a version on a specific platform, with the number and distribution of ratings shown.

  • Discussion

    Questions, update notes, and discussions of alternatives are attached to the software page.

  • Offers

    Official downloads, stores, and package repositories are listed with prices and licenses.

  • Follow

    Follow a software project or its maintainers to hear about new versions and announcements.

Eight parts used by Visual novels

  • Identity

    Chinese and Japanese visual novel communities share one work identity and choose their own names and ordering.

  • Editions

    Original editions, official translations, fan patches, and demos are separate releases, each listing language, platform, region, and coverage.

  • Names in many languages

    Original titles, aliases, and translations are stored separately. A translated title does not mean a playable translation exists.

  • Credits

    Writers, artists, musicians, and voice actors are credited by role, with voice actors linked to their characters.

  • Relations

    Sequels, side stories, anime adaptations, and novelizations are connected.

  • Filters

    When filtering by language, platform, region, and coverage, every condition must match the same edition.

  • Progress

    Track progress by route to see which ones you have finished and which remain.

  • Wiki

    The Wiki cites the route for each character and event, and hides routes you have not played.

Eight parts used by MCP Hub

  • Identity

    An MCP server project has one identity, with packages, deployment endpoints, and observations attached to it.

  • Editions

    Record each package release, with older versions and change history available.

  • Specifications

    Each record dates the task completed, client, version, and language used.

  • Credits

    Maintainers and their organizations have their own identities. Skills and APIs maintained by the same person are connected.

  • Ratings

    Ratings name the version they refer to, with the number and distribution shown.

  • Discussion

    Discuss setup, bug reports, and usage on the server page.

  • Lists

    Arrange useful servers in a list with notes, then share or export it.

  • Follow

    Follow a server to receive new versions and announcements based on your notification settings.

Eight parts used by Skill Hub

  • Identity

    A skill has one identity, showing which repository it came from and how many times it changed.

  • Editions

    Every release fixes file contents, license, and source. The downloaded files match the edition shown on the page.

  • Specifications

    Required and optional packages are separated, and missing declarations or unsupported formats are identified.

  • Credits

    Authors and co-maintainers each have an identity, linked to their other skills and servers.

  • Ratings

    Ratings are not averaged until they reach the threshold. Until then, only the number and distribution are shown.

  • Discussion

    Discuss usage, limitations, and problem reports on the skill page.

  • Lists

    Arrange skills in a list by workflow, with a note for each one.

  • Follow

    Follow a skill or its author to hear about new versions.

Eight parts used by API Hub

  • Identity

    A public API has one identity, with its identifiers and former names pointing to it.

  • Editions

    Versions and change history are listed together, with withdrawn versions identified.

  • Specifications

    Compare measurements in one table, with methods, conditions, units, and dates shown.

  • Credits

    Providers and maintenance teams have their own identities. Find an organization’s software and MCP servers together.

  • Ratings

    Ratings state the question and who rated the API.

  • Discussion

    Discuss integration experience, limitations, and alternatives on the API page.

  • Follow

    Follow an API to receive new versions and withdrawal notices in your inbox.

  • Lists

    List the APIs used by a project with notes on their purpose.

Each kind uses shared parts as needed. These eight best describe this kind.

Build each part once, and a new kind only changes the arrangement.

Fifteen parts

Fifteen parts, each with one job.

Each part serves a different purpose for each kind. The full catalog explains what each one does and gives an example.

See the parts directory and examples
  • Identity

    One identity points to the same thing in every language and on every site.

    ExampleOne author writes a novel and makes a game. Both entries link to the same person in their credits.

  • Names in many languages

    Names, aliases, and pronunciations in every language coexist, with original spellings preserved.

    ExampleA visual novel’s Japanese title, Chinese title, and romanized title appear together. Search for any of them to find it.

  • Editions

    Editions, releases, translations, platforms, and coverage each have their own records.

    ExampleA three-volume omnibus is one release, but its three works remain distinct.

  • Credits

    People and organizations are listed by role, with each name linked to its portfolio.

    ExampleVoice actors, characters, and works share one record, so their credits do not have to be pieced together later.

  • Relations

    Adaptations, sequels, series, and dependencies are visible from either end.

    ExampleThe anime entry says “Adapted from,” and the original entry shows “Adapted into,” both from the same relationship record.

  • Filters

    Filter by available fields, browse to the last result, and save criteria as a view.

    ExampleSave a view such as “anime with female protagonists adapted from novels,” name it, and follow it.

  • Ratings

    State what is being rated, then show the score and review.

    ExampleRate an audiobook’s story, translation, and narration separately.

  • Discussion

    Discussions attach directly to the thing, without a separate forum.

    ExampleDiscussions follow reading progress, so readers who have not reached the ending do not see it.

  • Wiki

    Wiki+ pages and infoboxes use facts reviewed on the graph.

    ExampleA person page’s infobox uses facts from the graph. Correct a fact once, and every page that uses it is updated.

  • Lists

    Lists can include any kind, and can be ordered, annotated, and exported.

    ExampleAn introductory list puts novels, manga, and anime in order, with a short reason for each item.

  • Progress

    Library status, every reading or play session, and what to read or play next.

    ExampleRead the first ten volumes in Japanese, then switch to the Chinese edition and continue from volume eleven.

  • Follow

    Follow a thing, person, or view and receive new activity.

    ExampleFollow a saved view and get notified when a new item matches its conditions.

  • Offers

    When something is for sale, see its availability, price, and where to buy it.

    ExampleAvailability is marked unknown when there is no data, not shown as in stock.

  • Specifications

    Measured specifications and compatibility evidence include test conditions and dates.

    ExampleA compatibility record names the client, version, and date observed.

  • Schedule

    Release dates, air times, and events appear on one schedule.

    ExampleAnnounced, scheduled, confirmed, and delayed are four separate statuses.

Five modules

Parts are grouped into five modules by purpose.

Each module answers a question and uses a set of parts. Trust is different: it applies to every part and handles sources, rights, and privacy.

A new kind

A new kind is a configuration task.

Add a new kind without building a separate backend. The parts are already there. Prepare five configuration items.

  • Vocabulary

    Define the kinds and properties, reusing existing vocabulary where possible.

  • Mappings

    Map each field in external data to a property on the graph.

  • Seed data

    The first set of entries and the links between them.

  • Saved views

    Common filters become indexes and tabs.

  • Zone

    A site that arranges these pages into a home for this kind.

Build a new behavior once as a part, and connect every kind that needs it.

Start with the kind you care about. The other eight are already connected to the same account.

Use one account to follow books and anime, track games, write ratings, and make lists. You can also build a site for your community in a Zone.