Built for the work nobody schedules

The premise

Operations work is not a to-do list problem

People whose job is coordination don't fail because they can't prioritise. They fail because the obligations arrive in eleven formats across five channels, and turning each one into a tracked item costs more attention than doing it.

So it stays in the head. And the head is a fine short-term store and a terrible long-term one, which is why the thing that slips is almost never the urgent task — it's the small commitment made in passing three weeks ago.

Zephyr's bet is that the useful application of a language model here is not doing the work. It's noticing the work: reading what came in, proposing what it means, and putting it somewhere durable before it evaporates.

• Propose, don't act. The assistant's job ends at a suggestion. Yours begins at approval.
• Say "I don't know". An answer with no evidence behind it is worse than no answer, in a system people are meant to trust with commitments.
• Keep the original. Every extracted action can point back at the thing it came from.
• Be honest about what's not built. This website says so on the feature pages, not only in the small print.