← HandbookChapter 02

Why Digital Employees have names.

It would have been easier to call them 'Invoice Automation' and 'Shipping Automation'. It would also have been wrong.

A name is not decoration. A name is a contract. When you hire Kira, you expect Kira-quality work. When Kira escalates a case, you know Kira is asking. When Kira makes a mistake, the mistake has a face — a plain typographic one, but a face all the same.

Naming Digital Employees the way we name humans is a decision about who is accountable. The company that put Kira into your operation is accountable for Kira's work. Not for 'the platform'. Not for 'the workflow you configured'. For Kira.

It also changes how you delegate to them. You do not 'configure a bot'. You give Kira the inbox. That framing carries more discipline into how the work is scoped, more clarity into what good looks like, and more forgiveness for the edges — because a real employee is allowed to say 'I'm not sure, I'll flag this'.

We could have called them anything. We called them Kira and Nox on purpose.