Published packages and development source
One native browser. Distinct release states.
The official Microsoft Store listing is the public Windows installation route. The active repository contains the native Chromium-based browser. Source updates, screenshots, and locally built packages may be ahead of the published Store package and do not establish its release or signing status.
Current Store package
The Microsoft Store listing linked from this site is the official public Windows package currently available to users.
Development build
Source-side progress, screenshots, plans, or local test output do not by themselves make the native build an official release.
Source builds
Locally built or third-party packages are not equivalent to the official Store package and should not be presented as TAHAI-signed releases.
Historical packages
Old preview installers and test-package lanes are not promoted from this website. Visitors are directed to the current Store listing or the public source repository.
Release discipline
Proof before the promise.
Each new release requires coherent runtime, packaging, application identity, signing, distribution, recovery, security, privacy, and installed-app evidence. Release claims apply to the specific package being distributed, not simply to the source branch or website.
Runtime proof
Normal browsing, tabs, navigation, physical mouse buttons, Find, downloads, DevTools, multi-pane routing, focus, and recovery must work in the real Windows build.
Package identity
The executable, icons, version, publisher metadata, package manifest, update lane, and Microsoft Store identity must agree.
Signing truth
No signed-release claim is made without actual signature evidence for the package being distributed through that lane.
Release vocabulary
“Preview,” “release candidate,” “Store-ready,” and “GA” are evidence-backed states, not visual labels added to make a build sound finished.
Open development
Visible source does not weaken the boundary.
The public repository supports inspection, issue reporting, and development. Open source does not mean privileged browser boundaries, integration credentials, package-signing material, customer data, or release secrets belong in the repository.
Official route: Use the Microsoft Store link on this site for the published Windows package. Follow the repository for native development. Locally built or third-party packages are not automatically official TAHAI releases.
