Architecture transition

Product concepts carry forward. The Electron architecture does not.

TAHAI Browser is being rebuilt on Chromium's native desktop architecture. The legacy Electron generation remains a reference for approved workflows, language, schemas, branding, and user experience—not the runtime foundation of the new browser.

Review current status Native architecture Legacy record

Side-by-side truth

What changes and what remains useful.

Legacy generation

Electron Browser

Electron desktop shell and Electron packaging
Existing Store generation and historical screenshots
Approved Mission Control concepts, recipes, tools, schemas, and content
Reference source for safe migration planning

Boundary: It is not proof of the native Chromium runtime, installer, policy integration, or Store package.

Next generation

Native Chromium Browser

Native browser windows, profiles, tabs, WebContents, storage, and permissions
Native downloads, DevTools, session restore, and physical input handling
Mission Control integrated into Chromium-native browser architecture
Managed policy, protocol governance, privacy, diagnostics, provenance, and native packaging

Status: Complete through NATIVE038. Six passes and G3, G4, and G5 remain open.

Migration boundary

Safe user data may migrate only by explicit choice.

Eligible for optional migration

Bookmarks, approved Missions, recipes, and selected settings may be migrated after validation and explicit user approval.

Never migrated

Cookies, tokens, credentials, authorization data, browser-storage dumps, raw Electron profiles, and service secrets are excluded.

No release inflation

No native download, signed package, Microsoft Store readiness, release candidate, enterprise readiness, or GA status exists until the corresponding evidence gates close.