I love what Proton is building with Lumo, but there's a gap that's genuinely frustrating in daily use: Lumo can't write to Proton Calendar.

If I want Lumo to add an event, I'm manually exporting, uploading, processing, re-importing. That's not an AI assistant — that's extra homework. For someone with ADHD, that friction might as well be a wall.

Siri and Google Assistant do this every day. They encrypt the event locally on your device before anything touches the cloud — the AI never sees your key. That's not magic, it's just good architecture. Proton already understands local-first encryption better than anyone. So why can't Lumo do the same thing?

What I'm proposing is pretty simple:

1. You tell Lumo to add an event
2. Lumo sends the request to your device
3. Your device encrypts it with your private key
4. Your device sends it to Proton Calendar

Zero-Access stays intact. The keys never leave your device. But the workflow actually works.

This isn't asking Proton to compromise on privacy — it's asking them to finish the job. A private AI assistant that can't write to your calendar isn't a full assistant. Let's fix that.