HushBrief
Private notes. Clear handoffs. A Chrome workspace for freelancers and small studios to turn rough working notes into a useful handoff without silently sending private context to a cloud model.
Paste notes, mark private passages, inspect the redacted preview, and create an evidence-linked action list. Cloud starts off. Editing notes revokes permission. Download the result as Markdown when you are ready to share it.
What it does
[[private: …]] spans never reach any model and never appear in the handoff or export. They are replaced with a neutral placeholder before device, hybrid, cloud, local-rules or rehearsal processing; unclosed spans are withheld to the end. Actions quoting withheld text are dropped. The UI and Markdown header report the number of private notes withheld.
Automatic email/phone masking applies to the cloud packet. Device-only and local-rules results keep email addresses and phone numbers visible. Review the cloud preview and the resulting handoff before sharing.
Built for #BuildHybridAI 2026 · Web/Chrome.
Judge setup, expected source labels, offline testing and current evidence limits are in the judge quickstart. Current local checks (17 November 2026): 42/42 tests and 19 isolated Chrome checks passed, including private-span withholding, consent reset, Markdown export and actual offline reload. These are local checks, not new live Firebase or Nano evidence. The post-fix human cloud observation is historical; post-fix Nano still needs owner recheck.
For judges: try it live
**https://hushbrief-hybridai.web.app** (desktop Chrome; no login, no payment)
- Click Load example: fictional notes with a
[[private: …]]span. - With cloud off, click Create handoff. You get "Local rules · no model", or "Gemini Nano · on device" if Chrome's built-in model is available and you clicked Prepare Nano.
- Review the redacted preview, tick Allow cloud fallback for this preview, then run again. A successful permitted request can return Gemini Nano · on device or Gemini · cloud; read the actual source badge. Attestation/model failure returns labelled local rules with a warning.
- Export Markdown and inspect the withholding notice before editing. Editing notes revokes permission and disables export until a new handoff is created.
Inference goes through Firebase AI Logic hybrid modes (ONLY_ON_DEVICE, PREFER_ON_DEVICE, ONLY_IN_CLOUD), protected by Firebase App Check with reCAPTCHA Enterprise. See verification.md for what has been verified live, including the current status of the on-device path.
Run in five minutes
Requires Node.js 24+ and npm. No account or credentials needed for rehearsal.
npm ci --ignore-scripts --cache .cache/npm --registry https://registry.npmjs.org
npm test
npm run build
Start the app and fake cloud together in one terminal:
npm run rehearse
Open **http://127.0.0.1:4173** in a fresh Chrome profile. The fictional example is preloaded: leave cloud off and click Create handoff. Review the three source-linked actions. Allow the redacted preview and run again to exercise the loopback fake cloud. Rehearsal controls can simulate Nano availability, offline operation and cloud failure, with explicit source labels. Result source and attempted route are reported separately.
In a second terminal, npm run record:demo generates a silent English-captioned MP4 in a unique output/demo/rehearsal-* folder. It uses a fresh temporary Chrome profile and the labelled fake cloud, then deletes its profile. This rehearsal is not evidence of live Firebase inference. The owner command card has the full configuration, Hosting, source-release and live-recording commands.
For a production/offline-app-shell check:
npm run build
npm run preview -- --port 4173 --strictPort
Open once online and wait for the service worker. Reload offline and use local extraction. The fake backend is still a separate loopback process; it is unavailable offline. Development Vite does not register the production offline cache.
Why hybrid belongs here
Handoffs combine shareable tasks with private contact details and internal context. Private spans are withheld before any processing. An on-device model can work with the remaining notes without a cloud inference request. A cloud fallback remains useful on devices without Nano, but only after the user reviews and permits the locally redacted packet.
- Device only: private-masked notes go to Firebase AI Logic ONLY_ON_DEVICE; failure returns local extraction of the same masked text. Emails and phones remain visible.
- Hybrid with permission: redacted notes go to PREFER_ON_DEVICE, enabling real SDK cloud fallback.
- Nano absent with permission: redacted notes go to ONLY_IN_CLOUD.
- Offline or model failure: a deterministic local extractor returns source lines. Its badge says “Local rules · no model.”
The model response reports its actual inference source. Every model action must quote a verbatim substring from the submitted masked notes. Actions whose quotes overlap private spans or placeholders are dropped; malformed output is rejected. Source quotes help review; they do not guarantee semantic accuracy. The fallback deliberately leaves owners and dates unset.
Real Firebase mode
The implementation imports and calls the official Firebase JS SDK in src/firebase.ts: initializeApp, initializeAppCheck, getAI, getGenerativeModel, initializeDeviceModel and generateContent. App Check is initialized before AI Logic, and hybrid mode is part of runtime routing.
The owner runs npm run configure -- --init to generate an untracked .env.local with placeholders, then fills it privately. npm run configure validates names/formats without printing values; npm run preflight itemises missing client fields and the console-only Firebase/App Check checks. No environment file is part of the public-source allowlist. Do not put a server Gemini key or App Check debug token in the client environment.
Default dev/build commands never load private environment files. The owner explicitly uses npm run dev:live or npm run build:live for the dedicated Firebase demo project. The Firebase menu option stays disabled until required fields are present at build time. Configuration alone does not verify an API, attestation, model or real inference.
Start with the setup and deploy commands. Public hosting needs production reCAPTCHA Enterprise attestation and enforced App Check. npm run publish-check -- --refresh-manifest refreshes hashes and prints the exact public-file allowlist; -- --export creates a clean source folder. The local fake backend is a rehearsal aid, not a deployed Gemini service. Real Firebase and Nano verification status is listed in verification.md; a successful rehearsal is not evidence of live inference.
Privacy and boundaries
Notes stay in tab memory; the app has no notes database, analytics or browser-storage writes for note content. The offline cache stores application code only. Clearing the workspace removes the current input, result and permission. Downloaded Markdown is a user-created file. Explicit private spans are withheld on every route; unmarked sensitive information may still appear, so review before sharing.
[[private: …]] spans never reach any model and never appear in the handoff or export; unclosed spans are withheld to the end. A neutral placeholder replaces each span before any model or local extraction, and the UI and Markdown header show the span count. Automatic email/phone masking applies to the cloud packet. Device-only and local-rules results retain emails and phones. Names, account numbers and uncommon identifiers can be missed. The preview needs a human review. A fixed instruction template and normal service metadata accompany a cloud request; the notes field itself is exactly the previewed packet.
There are no model tools, external actions or HTML execution from output. No claims of measured accuracy, latency, cost savings or complete PII removal are made. English text, up to 12,000 characters and six action cards are supported.
Validation and project map
npm test uses Node's single-process test runner with actual loopback HTTP integration. It checks consent, redaction, routing, source validation, malformed responses, evidence and offline fallback. npm run build includes strict TypeScript checking. npm run check:browser runs the local fresh-profile browser verification against a running preview and fake backend.
| File | Purpose |
|---|---|
| src/core.ts | Redaction, prompts, parser, device detection and routing policy |
| src/firebase.ts | Real App Check and Firebase hybrid model calls |
| src/demo.ts | Labeled rehearsal ports |
| scripts/fake-cloud.mjs | Loopback-only fake cloud, no request logging or external calls |
| scripts/browser-check.mjs | Fresh temporary Chrome verification |
| scripts/configure.mjs / preflight.mjs | Private field validation and explicit Firebase/App Check readiness gaps |
| scripts/publish-check | Exact public source allowlist, hashes and optional clean export |
| scripts/record-demo.mjs | Fresh-profile recording, burned-in English captions, optional owner voice-over |
| docs/design.md | Product, architecture and actual SDK use |
| docs/demo-script.md / demo-narration.json | 2:24 shot list and canonical English narration |
| docs/owner-commands.md | Copy-paste setup, live build, deploy and recording commands |
| docs/verification.md | Live Firebase verification and local checks |
The application, UI and fictional sample were created during the contest period. Pre-existing libraries are declared in THIRD_PARTY_NOTICES.md. Original project source is under the MIT licence.