A chatbot is not a staff
Named desks. Standing jobs. A computer of their own. That is the difference between a reply and a teammate.
The last two years trained us to talk to a single glowing box. It is very good at the next paragraph. It is very bad at having a job.
A staff is not a better box. A staff is a floor: people with names, desks, and work that is still theirs tomorrow.
A name is a contract
Scout researches. Maker builds. Closer writes. If you ask Scout to “just make the page,” you are not using the floor — you are stuffing three jobs into one chat because that is what the old muscle memory does.
Hire them by name and the contract is visible. Scout’s computer holds sources. Maker’s computer holds files. Closer’s computer holds drafts. Drag a chat beside. Three windows, like a real office, not a nested accordion of threads.
The computer is the desk
Work that only exists as a reply will be rewritten tomorrow. Work that exists as a file can be opened, shipped, or handed to the next teammate. That is why 8staff puts a live computer in the thread: observe, click, type, terminal, browser. You see a work chip, not a CLI dump. Allow or deny in place.
- A chatbot borrows your attention for one turn.
- A teammate keeps a desk when you look away.
- A staff is several of those, with jobs that do not collide.
First run is a hiring, not a prompt
Open 8staff and the floor already has three desks. You are not staring at a blank composer wondering who this is. You are meeting Scout, Maker, and Closer. Then you hire the fourth.
“Make a bot named Riley who writes emails” creates Riley and starts the work.