Core purpose
Software can be renamed, updated, released across platforms, forked, and surrounded by community knowledge. REZICS treats games, apps, websites, modules, services, and development tools as enduring works rather than records attached to one store or package listing.
What is available now
- Create multilingual software identities with summaries, images, and state.
- Preserve supported platforms and product-specific metadata.
- Connect releases, series, developers, publishers, tags, and sources.
- Return collections, reviews, scores, Realms, and related Posts to one identity.
- Present official sections and extensible Docks within the work detail framework.
General software scope
Games, applications, operating systems, development tools, libraries/frameworks, services, extensions, modules, and websites can share a software base, with platforms, requirements, tags, and relationships describing their differences. New products should exist only when distinct fields and lifecycles truly require them.
In development
Requirements need version-range syntax, searchable compatibility, and reliable sources. Modules and extensions also need decisions about which relationships belong in tags and which require formal dependencies; this is not yet a finished package-management system.
Relationships and boundaries
Software does not replace package registries, downloads, automatic updates, licensing verification, or runtimes. It provides work identity and knowledge context beyond a single store page.