peppermint-Aashish/axorin-release-hub

A calm, transparent, and obsessively documented distribution channel for the Axorin Windows companion experience — built for people who value reproducibility, verifiable artifacts, and a release history you can actually read.

Axorin Atlas is the canonical release ledger for the Axorin Windows companion app. Think of it less like a download page and more like a library's card catalog: every entry, every revision, every signature, catalogued with care so that anyone — a curious newcomer, a power user, or an auditor — can trace exactly what changed, when, and why.

Where the older si-update repository served as a simple announcement board, Axorin Atlas expands that mission into a full verification-first ecosystem. We do not merely publish versions; we publish context. Each release arrives with:

• A human-readable changelog written by an actual human.
• A machine-verifiable SHA-256 checksum manifest.
• A signed provenance record describing how the artifact was built.
• A compatibility matrix covering contemporary Windows builds.
• Localization notes for every supported language pack.

The goal is simple: trust through transparency. No mystery binaries. No silent rebuilds. No guesswork.

The companion surface adapts to whatever screen real estate you give it — from a modest 1366×768 laptop panel to an ultrawide workstation. Layout reflows gracefully, controls remain reachable, and density adjusts to your preference. It is a UI that behaves like water: it takes the shape of its container.

Axorin Atlas ships translation bundles for a growing set of locales. Language packs are versioned independently, so you can update strings without waiting for a full app release. Right-to-left scripts are handled natively. Pluralization rules follow CLDR conventions. A localization contributor guide lives alongside the release manifests.

A rotating team of maintainers monitors the issue tracker and community channels around the clock. Response targets are published openly. Escalation paths are documented. You will never be left staring into the void of an unanswered ticket at 3 AM.

Every artifact is hashed with SHA-256 and accompanied by a detached signature. A verification script (documented in the wiki) lets you confirm integrity with a single command. If a hash mismatches, the release is quarantined and an incident note is published — no quiet fixes.

Historical releases are never deleted or rewritten. Older entries remain in the archive folder for as long as the project exists. This is a deliberate design choice: reproducibility beats tidiness.

Not every change requires a full reinstall. Atlas supports component-level delta updates for translation files, themes, and configuration schemas — reducing bandwidth and friction.

Manifests are signed. Transport is validated. Rollback is a first-class operation. If a build regresses, the previous verified version remains reachable within seconds.

Usage statistics are opt-in, anonymized, and never required for core functionality. If you decline, the app simply works — no nagging, no dark patterns.

Light, dark, and high-contrast palettes ship by default. Custom themes are plain text files, easy to share and fork.

Early adopters can subscribe to a preview channel that receives candidate builds ahead of the stable line. Preview builds are clearly labeled and never masquerade as stable.

A guided tour of the folder structure, written for humans:

• manifests/ — JSON manifests describing each release, its components, and their expected hashes.
• changelogs/ — Markdown changelogs, one per release, named by semantic version.
• checksums/ — Plain-text SHA-256 files and their corresponding detached signatures.
• locales/ — Translation bundles organized by ISO language code.
• docs/ — Long-form documentation: verification guide, rollback procedures, contribution standards.
• archive/ — Historical releases retained indefinitely for reproducibility.
• notes/ — Incident reports, postmortems, and maintenance announcements.
• tools/ — Utility scripts for verifying and comparing release artifacts.

Each directory contains its own README with deeper context. Nothing here is a black box.

We believe a changelog is a letter to the future. It should explain not only what changed, but why. Entries follow a consistent voice: past tense for what happened, present tense for what it means, and a short note about who is affected. Breaking changes are flagged at the top. Deprecations receive at least two release cycles of warning.

A representative entry might read like this:

Version 4.2.0 — Spring Refresh Introduced a reorganized settings panel that groups related options under collapsible headers. Users on narrow displays will notice significantly less scrolling. The legacy flat layout remains available behind a compatibility flag for one more cycle.

Brevity is respected, but clarity is never sacrificed for it.

This repository is discoverable through natural, descriptive language rather than keyword tricks. The phrases that describe it best:

• Windows companion utility release channel
• verified software distribution with SHA-256 checksums
• multilingual desktop application localization
• transparent changelog and rollback documentation
• cryptographic signature verification for Windows builds
• reproducible release artifacts for desktop software

If you arrived here searching for a reliable update ledger for a Windows companion tool, you are in the right place.

Verification is a ritual, not a burden. The documented workflow:

1. Retrieve the manifest for the release you intend to use.
2. Compute the SHA-256 digest of the downloaded artifact locally.
3. Compare the digest against the manifest entry.
4. Optionally, verify the detached signature against the published public key.
5. If everything matches, proceed. If not, open an issue immediately.

The full procedure, including platform-specific digest commands, is spelled out in docs/verification.md. We recommend reading it once — the confidence it provides lasts a lifetime.

Translation work is ongoing. Languages currently receiving active attention include those with large desktop user bases and those requested most often by the community. Contributors who wish to add a new locale can submit a bundle following the schema in locales/_template/. Review typically takes under a week.

Strings are versioned separately from the app, which means a translator's work can reach users without waiting for a full release cycle. This decoupling has proven invaluable for long-tail languages that would otherwise be deprioritized.

Contributions are welcome across documentation, translation, verification tooling, and release notes. Before opening a pull request, please read CONTRIBUTING.md for standards on commit message format, changelog phrasing, and manifest schema validation.

We value small, well-explained changes over large, opaque ones. A thoughtful paragraph in a pull request description can save reviewers hours.

Support runs continuously. Channels include:

• The GitHub issue tracker (for reproducible defects and feature requests).
• A community discussion area (for questions, tips, and showcase threads).
• A dedicated localization feedback thread (for translation corrections).

Response expectations are published in docs/support.md. We aim for first response within a few hours, though complex issues may take longer to resolve fully.

Axorin Atlas is an independent distribution channel maintained by volunteers and community contributors. It is not affiliated with, endorsed by, or sponsored by any third-party platform mentioned in passing. All trademarks belong to their respective owners.

Artifacts published here are provided as-is, without warranty of any kind, express or implied. While every effort is made to verify integrity and correctness, users assume responsibility for how they deploy and use the software. Always verify checksums. Always read changelogs. Always keep a rollback path available.

The maintainers reserve the right to withdraw, quarantine, or supersede any release if a defect or security concern is identified. Such actions will be documented publicly in the notes/ directory.

In 2026, as in every year, our commitment remains the same: honest releases, clear documentation, and respect for the people who use what we build.

This project is distributed under the MIT License. You may use, modify, and redistribute the contents of this repository in accordance with the terms of that license.

Read the full license text here: MIT License

Copyright (c) 2026 Axorin Atlas contributors.

A release channel is more than a folder of binaries. It is a promise — that what you receive is what was published, that what was published is what was intended, and that the people behind it are reachable when something goes wrong. Axorin Atlas exists to keep that promise, one verified artifact at a time.