Status
Inbox, to‑do, in progress, waiting, blocked, completed or cancelled — waiting and blocked being the two most operations work actually needs.
Status, priority, owner, due date, the capture it came from and an append-only activity trail — enough to survive a handover, not just a checkbox.
A task app stores a string and a checkbox. An operations record has to hold enough to survive a handover.
Inbox, to‑do, in progress, waiting, blocked, completed or cancelled — waiting and blocked being the two most operations work actually needs.
Low, medium, high or urgent, proposed by Zephyr from the language of the request and adjustable by you.
Who it's on, and who else is named in it. "Ask John to confirm staffing" produces an action linked to John.
Extracted from natural language — "before Friday", "end of the month", "by the 14th" — not typed into a date field by hand.
Whether it was AI-generated, at what confidence, and which capture it came out of.
An append-only record of what happened to this action and when. It's an audit trail, not an edit history you can rewrite.
The failure mode of every task system is that maintaining it becomes a second job. Zephyr's answer is that the list mostly maintains itself: actions arrive already classified, already dated, already attributed, because they were extracted rather than typed.
What's left for you is the part that needs judgement — is this real, is it mine, is it urgent — which is exactly the part you were doing in your head anyway.
Zephyr is in development for iOS and Android. Join the early access list.