Understood. This is how I would do it:
Every working day at 7:00 I look into your mailbox, your calendar and the weather for Straubing and lay out a summary for you as a notification and card in “Today”.
You write one sentence, OCTOVO shows you in plain language what it would make of it, and after your yes it creates an order — visible in a list, pausable, changeable and deletable at any time.
Orders
No rule editor. One sentence.
Create from one sentence, pause any time. No condition chains, no “workflow”. You say it the way you would say it to a person — that becomes an entry in a list, with a name, a state and a button to pause it.
Every order has exactly one trigger. That’s how you see at a glance in the list why it runs:
-
Recurring task
- Trigger
- A time or a rhythm
- How you say it
- “Every working day at 7:00” · “Every first of the month”
-
Event
- Trigger
- A single point in time
- How you say it
- “Wednesday at 14:00” · “On 31 July”
-
Order
- Trigger
- An occurrence
- How you say it
- New mail from X · invoice recognised · file in a folder · deadline running out · nobody replies
Before anything runs
It never answers with “ok”
Every sentence gets a confirmation card in plain language. Every highlighted piece can be tapped and changed.
- planned
- waiting for its trigger
- running
- waiting for you
- done
Across those, three states you understand at once: paused, because you wanted it. Disrupted, because a channel is gone — with the reason next to it and a button that fixes it. Aborted, because the emergency stop or the loop guard kicked in.
When something goes wrong
No silent failure. Ever.
Pause any time, nothing gets lost.
-
Try three times, then ask
On technical trouble — network down, provider acting up — it retries with growing gaps. After that it gets you, instead of failing silently.
-
In doubt, don’t send
If it’s unclear who is meant or what applies, the draft goes to approval. Even on autopilot, even if you have set something else.
-
Never twice
Every outgoing action gets a fingerprint. If the computer crashes mid-order, nothing is sent twice after the restart.
Plus the loop guard: if an order breaks loose — more than ten times its average, or 20 runs an hour — it stops itself and asks. The hard ceilings (50 messages per hour, 20 recipients) always apply.
The list
Everything that runs, in one place
RecurringEventsOrders
Morning overview running
Every working day at 7:00 · last run today at 7:00
I collect new mail, your appointments, open tasks and the weather and lay out a summary for you.
“Change” doesn’t open a form editor, it opens the conversation at that spot: “What should I do differently?” You write “make it 6:30 and skip the weather”, and the card rewrites itself — the change stays highlighted.