Documentation
Architecture, policy, privacy, and release truth.
Public documentation is organized around what is known at the source level, what still requires runtime proof, and which release claims remain blocked.
Development update
NATIVE038 completion, Chromium pin, blockers, and current gates.
ArchitectureNative Chromium foundation
Native windows, profiles, processes, services, isolation, and Mission Control boundaries.
ProductMission Control
Native Mission Tabs, multi-pane architecture, runbooks, timelines, and OpsTools.
SecurityPrivileged boundaries
Managed policy, remote-site isolation, payload validation, and prohibited interfaces.
PrivacyLocal-data inventory
Profiles, Missions, evidence, diagnostics, downloads, policy, and secret exclusions.
RoadmapRemaining passes
NATIVE039 through NATIVE044 and Enterprise Gate G5.
Release evidenceChecksums and provenance
Current source identity and planned source-to-binary proof.
TruthKnown blockers
Open runtime, packaging, signing, Store, and release gates.
PlatformSystem requirements
Why final hardware and Windows requirements are not yet claimed.
HistoryRelease notes
Development milestones without inventing a native public release.
EvidenceRelease gates
G3, G4, G5, packaging order, and prohibited release claims.
EvidenceRelease readiness
Named-pass progress, runtime blockers, gates, and packaging truth.
AnswersFAQ
Architecture, availability, legacy generation, security boundaries, and long-term scope.
QualityAccessibility
Public-site support and native runtime evidence still required before release.
Source context
Legacy source remains available as reference.
The public GitHub repository documents the former Electron generation. It is not the architectural source of the native Chromium rebuild.