Audio Notes

Wednesday, June 10

1 session recorded
🎙️ 9:43 PM · ~3 min
Daily Overview

The evening wrapped up with a forward-looking architecture discussion between Alex and the team. The conversation centered on how Milestone 1 will replicate the 2.0 routing model — forms and structured inputs handled on-device, everything else flowing through Hatch.

The more substantive debate was around Milestone 2, where the team explored the open question of messaging integrations. As FOA moves toward making Instagram and WhatsApp messaging available within the experience, the team grappled with a fundamental tension: privacy versus utility. International users in particular are expected to have stricter privacy preferences, potentially refusing to route any data through Facebook's servers.

Alex framed the decision space as binary — Hatch-only or Hatch + on-device hybrid — with the resolution deferred to 2027 pending signal from M1. The key architectural insight: whether a user has connected the WhatsApp connector to Hatch determines the routing path, making user consent the switching mechanism rather than a system-level policy.

The session concluded informally with dinner plans and a thank-you to Saurav for attending virtually.

Session Details
🕘 9:43 PM 👤 Alex, Saurav 📍 Architecture / Routing

Milestone Roadmap: On-Device Routing, Messaging Integrations & Privacy Tradeoffs

Messaging Integrations & Alignment

  • FOA is moving toward making Instagram, WhatsApp, and other messaging options available within the experience
  • How variables and forms work for communications remains an open discussion with very little alignment yet

Privacy Expectations & Routing Logic

  • Expectation that some users will refuse any data going to Facebook — especially i18n users with stricter privacy concerns
  • Team wants signal from M1 and next version to gauge how privacy concerns affect usage
  • If a user has the WhatsApp connector connected to Hatch → request routes to server (user has consented to server-side communication)
  • If connector is not connected (privacy priority) → request must use the on-device stack

Decision Timeline

  • Hatch-only vs. hybrid routing is characterized as a 2027 decision
  • Discussion described as very early — not a plan of record
Key Exchanges
9:43 PM Alex: In Milestone 1, it will go through the on-device communication style to the server. So it'll be exactly same as 2.0 — if it's a query dealing with forms, on-device will pick up, and then the rest of it will be handled through Hatch.
9:43 PM Alex: For Milestone 2, there is open conversation on generally for comms, given that there will be Instagram messaging, WhatsApp messaging and other options available… How does variables form work? I think it's still an open discussion. There's very little alignment yet.
9:44 PM Alex: The decision space is basically either Hatch-only or Hatch and on-device. And depending on whether you sign up for a skill or not, you basically have computation on the device.
9:45 PM Alex: It would really depend on if you have WhatsApp connector connected to Hatch or not. If you have it connected, it should go to the server — basically you're saying part of my communication is going to the server.
Action Items
No action items captured for this day.
Generated by Hatch · Audio Notes Summary · June 10, 2026