Release Trust
B3IQ host-agent provisioning, release-manifest, signing, and update trust gates for the machines B3IQ hosts and ships.
B3IQ provisions and updates the host agent on the machines it hosts and ships. Release trust is a production gate: every host-agent artifact B3IQ fetches during provisioning or a self-update must be verified before it can run. Production trust requires stronger signing and smoke evidence.
Provisioning artifact fetch
When B3IQ brings up a machine, the provisioning path fetches the host-agent binary and verifies it against published release checksum metadata before it is executed or installed. A binary that fails verification is rejected rather than run. This is the same trust boundary the self-update lifecycle enforces on every subsequent build.
Current host-agent trust
Provisioning verifies release checksums before it installs the host agent. The remaining gates before this counts as production trust are signed release-metadata enforcement, package trust, and install/reinstall/uninstall smoke coverage.
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.
Same-origin checksum verification is useful for pilots. Production provisioning and update trust should require signed metadata and package trust where possible.
Update trust
Production update trust still needs:
- A signed apply path for the host agent.
- Rollback smokes after bad or failed updates.
- Dashboard 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.