Runtime foundation proof.
Requires the pinned Chromium checkout, successful native build, headed Windows execution, and earlier-pass runtime receipts.
Native Chromium Rebuild — Active Development
Release gates
Release labels follow evidence.
The native rebuild is not downloadable or release-ready. The remaining gates define what must be proven before packaging and public release may proceed.
Open enterprise gates
Packaging remains blocked until the evidence chain closes.
Source contracts and deterministic checks are progressing, but final runtime and release claims require the full pinned Chromium checkout, headed Windows proof, policy/security/privacy evidence, provenance, packaging, and installed-app verification.
Security and privacy proof.
Requires privileged-boundary, policy, local-data, protocol, extension, permission, and diagnostics evidence.
Provenance before packaging.
Requires SBOM, Chromium revision evidence, TAHAI patch hashes, GN arguments, toolchain versions, checksums, and source-to-binary manifest coverage.
Packaging sequence
Installer and Store work follow—not precede—the gates.
- NATIVE039Protocol, extension, and permission governance
- NATIVE040Safe support bundle and diagnostics
- NATIVE041SBOM, provenance, and reproducibility; then Gate G5
- NATIVE042Windows installer and signed-artifact lane
- NATIVE043Native Chromium MSIX and Microsoft Store evidence
- NATIVE044Safe legacy migration, physical input proof, installed smoke, final RC decision
Prohibited claims
No evidence, no release label.
Do not publish native download, production-ready, enterprise-ready, signed-release, Store-ready, release-candidate, or generally-available language until the corresponding evidence exists.