# Verification report — Orvi Secure Browser 0.3.0 Status: browser release. The complete browser specification is NOT fulfilled or certified by this report. Production signing is prepared but not activated. Installer SHA-256/SHA-512 and exact signing state are in release-record.json and the website checksum file. ## Checks performed in this workspace - TypeScript compile: passed. - JavaScript syntax checks: passed. - Eight browser-policy tests: private defaults; address/query handling and dangerous schemes; public suffix site isolation keys; preference validation; overdue/daily cleanup; update downgrade/off-origin/invalid metadata rejection; cleanup ordering and partial failures including locked storage; storage category coverage. Passed. - Website delivery: 56 tests passed for installer streaming, byte ranges, immutable chunks, metadata validation, unsigned-update refusal and signed filename support. Website TypeScript check and production build passed. - Eight additional encryption/lock tests passed: authenticated ciphertext, cross-record tampering, legacy migration, restart locking, active-key clearing, concurrent attempts/retry delays, recovery rotation, lock-change authorization, missing-key preservation and HTTPS request policy. These exercise real AES-GCM/scrypt with a test OS wrapper; they do not certify Windows DPAPI or EFS. - Windows x64 build: NSIS installer generated with the pinned Electron/builder versions. PE header and packaged source/metadata identity checked. NSIS uninstaller original CRC checked by the existing pinned Orvi packaging adapter. - Runtime launch attempted with sandbox and site isolation enabled. The execution environment rejected a required OS socket in Chromium’s process singleton. The app did not reach a usable desktop window. No protections were disabled to work around this restriction. - No Windows machine was available. Application launch, real website sessions, permissions, storage deletion, installed updater and performance are NOT verified by compilation or mock-based tests. ## 0.3.0 interface and request-processing checks - Four additional tests pass (20 browser tests total): coalesced notifications/cancellation, bounded origin cache and schemeful site classification, case-insensitive cookie-header removal without input mutation, and bookmark-bar defaults/migration/native viewport height. - Local interface fixture reviewed in a browser: Light and Dark palettes, settings dropdown above the current view, plus button beside two tabs, bookmark bar, navigation icons, Refresh/Stop loading state, and the address-bar loading indicator. This fixture uses simulated application events, not a Windows Electron engine. - A 500-update renderer burst took 98.6 ms in the local browser fixture; existing tab nodes and typed new-tab search text were preserved. This is not a Windows or website loading benchmark. - Isolated Node benchmark on Linux, Node 24.22.1, 20,000 synthetic request site checks, median of seven runs: previous repeated parsing 54.32 ms, bounded origin cache 32.02 ms. A burst of 500 notifications coalesced to one. These numbers describe only these synthetic operations. - Removed the unused CDP Network event stream while retaining Network.setCookieControls. Chromium implementation review indicates the cookie control overrides do not require Network.enable. Verify real third-party cookies, workers and tracking protection on Windows before production. - Settings uses a separate sandboxed local WebContentsView above website views. Its privileged IPC accepts only its exact local main frame; website views receive no preload bridge. Native Windows composition, resizing, keyboard focus and screen-reader behavior still require Windows testing. ## Required before production 1. Complete Microsoft Artifact Signing organization verification and sign the app/installer using docs/SIGNING.md. Validate exact publisher, timestamp, Windows trust chain and installed artifact hash. 2. Validate Windows DPAPI on a fresh user account and after restart/update; EFS on supported NTFS and refusal on unsupported editions; PIN/key setup, lock across multiple windows, external links while locked, wrong secrets, recovery, Windows lock/sleep and interrupted saves. Verify no website context opens before unlock. Then run the actual Windows storage harness with `npm run test:windows-storage`, then verify full application multi-window erase, service worker activity, failure/retry, saved-site exceptions, all-data override, active downloads and crash/forced-termination recovery. Inspect actual profiles before/after restart. 3. Inspect network requests from the packaged Windows app: idle startup, typing (suggestions off/on), website navigation, tracker blocks, permission grants, update checks, crash behavior. Verify infrastructure access-log retention. No privacy claim is considered audited yet. 4. Integrate and evaluate a privacy-compatible phishing/malicious-download reputation service; validate downloads and OS zone marking. Add proven fingerprinting/bounce tracking protections or explicitly narrow the production feature claim. 5. Exercise login, shopping, video, PDF, print, fullscreen, HTTP downgrade, invalid certificate, popups, hostile pages, IP/IDN address display, accessibility and keyboard navigation. Test third-party cookies and workers separately. 6. Test signed updater success, tampering, wrong publisher, revoked/untrusted certificate, interrupted download/install, rollback attempts and pending restart with active sessions. The application and Chromium engine must move together. 7. Measure startup, tab switching, scrolling, memory and idle CPU on real Windows hardware with recorded specs and comparable browser settings. No speed claims are substantiated yet. 8. Finish unsupported capabilities identified in ARCHITECTURE.md or obtain an explicit narrower release scope. This version is not suitable for security-sensitive daily browsing.