Digital Collar
Menu

Blue collar White collar Digital collar

The Digital Collar Manifesto

The digital collar is the work AI agents now do on our behalf, and the people who direct it, check it and answer for it.

digital collar

noun

  1. The class of work performed by AI agents and automated systems on behalf of people and organizations.
  2. The people who assign that work, supervise it and answer for its results.

Every era of work gets a collar. The blue collar named the people who made and moved things. The white collar named the people who wrote, counted and decided at desks. Each word was shorthand for a deal: what you do, where you do it, and who you answer to.

A new kind of worker has arrived with no shirt to wear. Software agents now draft, sort, schedule, reconcile, reply and build. They do it at the request of people, inside companies, under rules that are still being written.

Work that has no name has no standards. So here is the name, and here are the standards we propose.

Twelve theses

  1. Work is what gets done, not what does it.

    An agent that files the report, answers the ticket or ships the fix has done work. Pretending otherwise hides it from every rule that governs work.

  2. Every agent works for someone.

    There is no such thing as unsupervised labor. There is only responsibility that nobody has claimed yet.

  3. Accountability does not automate.

    When an agent acts, a named person answers for the result. Not the model, not the vendor, not "the system."

  4. Directing agents is skilled work.

    Assigning, checking and correcting an agent takes judgment. The people who do it are workers, and they should be paid as workers.

  5. Every agent needs a written job.

    Scope, permissions and limits belong in plain language before the first task, not after the first mistake.

  6. Speed is not a credential.

    Fast output still has to be right, and someone still has to look before it leaves the building.

  7. Agents say what they are.

    People have a right to know when they are dealing with software, in a message, on a call or across a counter.

  8. The record is part of the work.

    What an agent did, when it did it and on whose instruction should be something a person can look up and read.

  9. No job changes in silence.

    When agents reshape a role, the people in that role hear it first and have a say in what comes next.

  10. The gains are shared.

    When agents lift output, the people around them share in it: in pay, in time or in training. Not only the owner.

  11. Every agent can be stopped.

    Each deployment comes with an off switch, and with a person who is allowed to use it without asking twice.

  12. Collars are not ranks.

    Blue, white and digital work side by side. None of them is beneath the others, and none of them works alone.

For workers

The digital collar is not a storm to wait out. It is a kind of work you can claim. Directing agents, reviewing what they produce, catching their errors and owning the outcome are real skills.

Ask for those skills to be named in your role, counted in your review and reflected in your pay. If your job changes because an agent arrived, you are owed an explanation and a voice in what happens next.

For companies

An agent is not a free employee. It is a tool that acts, and a tool that acts needs an owner, a job description and a record.

Give every agent a responsible person. Write down what it may and may not do. Keep logs a human can read. Tell customers when they are talking to software. And when agents make the business more productive, decide in the open how that gain reaches the people who made it possible.

For agents, and the people who direct them

If you build or direct agents, you are setting the terms of a new kind of work. Make your agents legible: they state what they are, what they were asked to do and what they actually did.

Keep them inside their brief. Build the stop button before the start button. And treat the person who checks the output at the end of the day as part of the system, never as a cost to engineer away.

Name the work. Name who answers for it.

That is the manifesto in two sentences. Put it in a job description, a contract or a team meeting. Signing it means acting on it.