Safal

Enforced a strict "No Raw Cloud Sync" rule by keeping all active files inside a locally controlled folder structure rather than connected cloud drives.The Trade-off: The practice loses automatic real-time sync across multiple off-site devices, requiring manual file transfers if the physician works on a secondary laptop.The Rationale: Giving a desktop agent autonomous read/write access to a shared cloud drive (like Google Drive or OneDrive) risks syncing unverified or draft notes across external networks. Limiting Cowork to a dedicated, encrypted local folder creates a hard security boundary, keeping patient context completely isolated while ensuring zero risk of accidental cloud overwrites.

I chose to follow the MCP standard instead of building a custom API because it makes the integration easier to maintain and compatible with AI clients that already support MCP. I also used Next.js to keep the implementation straightforward and easy to deploy. The main trade-off is that lowering the friction to publish also lowers the friction to spam users could generate and post low-quality content more easily. Any production version should therefore include safeguards such as authentication, rate limiting, moderation, or user approval before publishing. I considered the improved user experience worth the trade-off, provided those protections are added.