B3IQ install and update trust is a production gate. The current public installers are useful pilot artifacts, but production trust requires stronger signing and smoke evidence across platforms.

Current Installer Trust

PlatformCurrent stateRemaining gate
Linux scriptPublic route verifies release checksums before installingSigned release metadata enforcement, Linux package trust, desktop install/reinstall/uninstall smoke
macOS scriptPublic route verifies release checksums before installingProduction signed update apply and rollback smokes
macOS GUISigned and notarized DMG public pilotClean-machine and existing-machine GUI smoke evidence
Windows scriptPublic PowerShell install route existsProduction signed metadata enforcement and Windows service/install smoke
Windows GUINSIS validation artifact onlyAzure Trusted Signing or PFX Authenticode, VM smoke, production-ready manifest evidence
Linux GUIDEB validation artifact onlyPackage trust plus real Ubuntu Desktop GUI smoke

Release Manifest

The host-agent release pipeline can generate and verify a signed release-manifest.json with Ed25519 over exact manifest bytes. Production publish should require the manifest signature and a configured production public key.

Checksum alone is not enough

Same-origin checksum verification is useful for pilots. Production install and update trust should require signed metadata and platform-native package trust where possible.

Update Trust

Production update trust still needs:

  • Signed apply paths for Linux, macOS, and Windows.
  • Rollback smokes after bad or failed updates.
  • GUI surfacing for update state and recovery.
  • Manifest signature enforcement with the real production public key.
  • Existing-machine tests that preserve local owner state, models, runtime state, and service state.

Public Installer Copy

Installation

Platform install commands and GUI status.

Learn More
Current status

Current evidence and production launch gates.

Learn More
Ask a question... ⌘I