One operator, four abilities

Most AI products arrive as a list. Chat. Agents. Automations. A browser. A builder. Each one is a thing to evaluate, a tab to lose, a vendor conversation to restart.

Kaer is the opposite shape: one operator. It communicates, it operates your software, it runs workflows, and it builds the missing tool. The menu is the claim: four abilities, not a suite. If a fifth one appears, it has to earn a place on that list, not a new top-level app.

You do not brief it on clicks. Most tools still want a prompt that is secretly a procedure: open this, click that, paste the thing. That is not delegation. That is remote control with extra words. An outcome is 'the unpaid invoices from March are chased by Friday, and nothing goes to a customer who already paid.'

Given an outcome, the operator decides whether it is mail, a browser session, a scheduled workflow or a small tool that does not exist yet, and then it does that. If it cannot see a path, it says so. If the path needs you, it stops.

Planning is visible. Acting is visible. Stopping is the point. If a step would send, pay, delete or publish, the operator waits. That stop is not a personality. It is a control. You can tighten it. You cannot turn it into a shrug.

Each ability has its own page: Mail for the inbox, Computer for the software that has no API, Workflows for the processes that repeat, and Software Builder for the tool nobody got round to building. The Operator page shows how a job is read before it is edited, split across machines that run at the same time, and stopped at the step that carries a consequence.