Chrome direct USB
Vault access and guided setup use WebUSB without a native host. Connection recovery is tested against queued public replies.
STATUS / DEVELOPMENT ALPHA
Evidence before
confidence.
A working development build is a step toward a release. It is not a completed independent audit or production certification.
CURRENT IMPLEMENTATION
The project today.
As of October 1, 2026. Each firmware image and extension package needs its own source, build, and acceptance evidence.
Safe 5 & Model T targets
Both have firmware build paths and model-specific guided setup. Qualification and physical acceptance remain candidate-specific.
Individual record release
Per-entry approval, fresh reveal PINs, separate local access, encrypted card storage, and bounded private records.
BEFORE A PRODUCTION RELEASE
The remaining requirements.
- 01
Full physical acceptance
Exact shipped candidates need recovery, interruptions, card handling, repeated operations, and capacity tests on the actual devices.
- 02
Independent security review
Review the release source and artifacts, resolve serious findings, and document the remaining risks.
- 03
Authenticated distribution
Establish the release authority, package provenance, update policy, and official browser distribution.
- 04
Reproducibility and recovery drills
Bind builds to source, reproduce artifacts, and exercise password-vault replacement-device recovery.