Distribution

Official packages, source builds, native release claims, and signing status are separate things. TAHAI Browser states that distinction plainly.

Current Store edition. Next-generation native edition.

The existing TAHAI Browser listing remains the official currently published Windows lane. The native Chromium rebuild is a separate next-generation product lane and is not represented as downloadable, signed, Store-ready, release-candidate, or generally available until the required evidence exists.

Current Store package

The Microsoft Store listing linked from this site is the official public Windows package currently available to users.

Native 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.

Proof before the promise.

The next-generation native Windows release requires coherent runtime, packaging, application identity, signing, Store, recovery, security, privacy, and installed-app evidence. Marketing language follows those facts rather than getting ahead of them.

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.

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 current public Windows edition. Follow the repository for native-development progress. Native downloads will be published only when the release lane is actually ready.