HushBrief — judge quickstart
Desktop Chrome is the intended platform. The interface and fictional example are English. No app account or payment is required.
Hosted evaluation (about 3 minutes)
Open **https://hushbrief-hybridai.web.app** in your normal desktop Chrome browser.
- Click Load example. The notes are fictional. The cloud preview should mask the example's email, phone and marked budget. Unmarked identifiers can be missed.
- Leave Allow cloud fallback for this preview unchecked. If compatible Nano is available, click Prepare Nano and wait for readiness before clicking Create handoff. Otherwise, local rules return three explicit tasks. Read the RESULT SOURCE badge: local rules do not mean a model ran.
- Confirm the marked internal budget is absent from the result and a private-note withholding notice appears. Export Markdown before changing the notes; check the same notice and absence in the file. Local/device output may retain unmarked email and phone text.
- Review the cloud preview and check Allow cloud fallback for this preview. Click Create handoff again. A successful SDK result may say Gemini Nano · on device or Gemini · cloud, according to actual availability. On devices without Nano, successful permitted inference should use cloud. Model/attestation errors return labelled local rules and a warning; that is not live-model verification.
- Edit any note. Permission is revoked, old results are invalidated, and export stays disabled until the next run. Clear workspace removes notes, results and permission from the tab.
After the first successful production load and service-worker activation, disconnect the browser and reload. Local extraction should remain available. The cache holds application code, not note content. A ready device model is device-dependent; offline success here is not evidence of Nano inference.
App Check uses reCAPTCHA Enterprise. Use ordinary interactive browser evaluation; automated browsers can fail attestation. Do not bypass protection or treat a local fallback as a cloud success. If the hosted model path is unavailable, the local path below still evaluates the interface and routing logic without any credentials.
Local evaluation
Requires Node.js 24+, npm and desktop Chrome. From the repository root, in PowerShell:
npm ci --ignore-scripts --cache .cache/npm --registry https://registry.npmjs.org
npm test
npm run build
npm run rehearse
Open http://127.0.0.1:4173**. The default commands do not load private configuration files. Use the same example, cloud-off run and export. Rehearsal's cloud is a fake backend on loopback, and its device results are simulations. Their badges say so. No Firebase, Gemini or Nano inference is established by rehearsal. Stop with Ctrl+C**.
For an app-shell offline test, stop rehearsal, run npm run preview -- --port 4173 --strictPort after the build, and visit once while online. Wait for the service worker before disconnecting. The fake backend is not an offline service; local extraction is.
The dedicated Firebase configuration is owner-managed. Judges do not need its credentials. Do not add server credentials to this client or copy a debug token into testing instructions.
Evidence and limitations
- Current local verification on 17 November 2026: 42/42 tests, strict TypeScript, sanitized production build and output safety check, plus 19 isolated Chrome checks, all passing. No external app requests were observed. These checks used local rules, synthetic ports and a loopback fake backend.
- Historical human live verification on 15 November: post-fix cloud success in Edge. Historical Nano success was before the private-span fix; post-fix Nano and permitted device/cloud fallback await owner recheck.
- The 17 November video and gallery show the current local build. They demonstrate actual local extraction and privacy controls, not live Gemini inference.
- No measured accuracy, cost, latency, adoption or complete identifier-removal claim. Source quotes are review aids, not semantic guarantees.
The owner must keep the hosted app and public licensed source available free of charge through 17 December 2026, 06:00 SGT, the published end of judging converted from PST. This document records preparation, not confirmation of future uptime.