What the AI employees are

A roster of named employees whose every action is a task you can read, approve, and undo.

AI Employee → Task Docket.

One rule governs everything here: every unit of work is a task, and every side effect comes from a registered handler for that task. Chat, schedules, buttons and the API all funnel into the same place. There is no quick path — a quick path is exactly how an unaudited change gets into a ledger.

The second rule is the run/apply split. Running a task computes a proposal and changes nothing outside the system. Applying it commits, after approval. That separation is what makes an approval meaningful: you read what will happen, not a summary written after it already did.

The third rule is: refuse rather than guess. An ambiguous task parks with a specific question and evidence — "which account? 11 of the last 14 similar went to Office Supplies" — instead of picking one and being wrong all year.

See The roster, Trust and autonomy, The controls that run before anything else and Ask your business.