Software
Make every release easy to find and verify.
Developers maintain their programs on REZICS with the version, platform, files, change notes, license terms, and download location for each release. Followers, people using filters, and AI agents all read the same record.
One release
Fields in a release record
A release cannot be submitted until all required fields are complete. After submission, the record is archived.
Version
4.0
Channel
Stable
Date
2026-08-25
Platform
System A · 64 bit, System B · 64 bit, System C · Mobile
File size
48.2 MB
Hash (excerpt)
sha256 9f2c41d7e41a
License
Example open source license, version 2.0
How to get it
Developer website (external link)
Change notes
Adds workspaces and removes the old plugin format.
Release process
Five steps to publish a release.
Confirm maintainer access
Confirm that you can maintain the project before updating its page and releases.
Enter release details
Add the version, channel, date, and files for each platform.
Declare the license
Choose the license terms and version. The declaration records who made it, when, and for what scope.
Explain how to get it
State who provides the files, where to download them, or which external page to visit for installation. If REZICS only links to another site, it does not say that REZICS installs the software.
Publish
The release becomes an archived record. Followers receive a notice based on their notification settings.
Complete these steps through the API and MCP to automate each release in your publishing workflow.
License
State the exact license terms and version.
A license declaration records the exact terms and version, declarant, date, scope, and source. License text imported from an external source is labeled with that source, not treated as your declaration.
Not a certification
A declaration is not legal certification and does not change anyone’s editing permissions.
Say when it is unknown
If you do not know who licensed it or when, say that it is unknown.
Filter by license
Use license terms as a filter to find programs that meet your needs.
Dependencies
Dependencies follow each ecosystem’s rules.
When REZICS resolves package dependencies, it preserves each ecosystem’s identities, version order, and dependency meaning, then locks the result to exact files.
Required and recommended
Required dependencies and conflicts are recorded separately from suggested combinations and notices.
Removed versions
Removed versions follow the rules of their ecosystem. Existing locks keep their original file selections.
Report separately
Unavailable sources, unsupported terms, and budget limits are reported separately from unsolvable dependencies.
Unavailable does not mean absent
Dependency data that cannot be found is not treated as proof that there are no dependencies.
Installing does not authorize execution; scripts in a package run only with your explicit approval.
The REZICS installation process accepts only verified files and places them in an isolated staging area.
After release
Maintenance after release
Screenshots and statements
The provider is named for screenshots and privacy and accessibility statements.
Withdraw a claim
Withdraw an outdated claim about a platform without deleting the program, its releases, or discussions.
Store listings
When software is sold, prices, regions, and validity dates appear in a table. Price changes stay in the record.
Credits
Maintainers and contributors are listed by role. When a person changes projects, their identity stays the same.
Publish once. Everyone reads the same record.
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.