The census may soon have to count the software
A statistics office would publish a methodology note on whether autonomous agents that hold accounts and issue invoices belong in the economic register. One county in the draft would turn out to have more registered economic actors than residents.
A national statistics office would open a methodological consultation on the classification of autonomous software agents that hold accounts, enter into agreements and issue invoices. The note would run to a few dozen pages, would contain no photographs, and would concern itself with a single question: whether such an entity is a unit of production or a piece of capital equipment that has been given a bank account by mistake.
The distinction would matter only because of where the totals go. Capital equipment appears in one column and depreciates. A unit of production appears in another, is counted in the business register, contributes to the count of active economic actors, and is, by long-standing convention, the sort of thing that can be said to exist. The note would observe that the existing definitions were drafted at a time when this question could not arise, and would decline to blame anyone for that.
The consultation would propose three options. Treat the agent as an extension of the legal person that operates it, which keeps the register clean and loses the activity. Treat it as a distinct unit, which makes the register accurate and unusable. Or create a supplementary satellite account, which is the option statistical offices reach for when a question is real, important and best answered in an annex that nobody reads.
The passage attracting attention would be a footnote in the third annex. Applying the second option to the existing register, the office would note that in one administrative district the number of registered economic actors would exceed the number of resident natural persons. The footnote would add that this result is arithmetically correct, methodologically defensible and not intended as a statement about the district.
A second footnote would address the labour force. If an agent produces output continuously, the note would ask whether that output belongs in the hours-worked series, and if so, how many hours a week to record for an entity that does not have weeks. The proposed interim treatment would be to record the output and omit the hours, which would leave productivity per hour worked rising indefinitely without anyone working more.
The note would end, as such notes do, with a paragraph confirming that nothing in the document implies legal personality, that classification decisions are taken for statistical purposes only, and that the office has no view on the underlying phenomenon. It would then recommend that the next census questionnaire include a question about whether the household operates any such entity, and that the answer be recorded separately from the count of people.
No decision would be taken. The register, meanwhile, would carry on accepting registrations, because the register accepts anything with an identifier, a bank account and a postal address, and has never been asked to check for a pulse.
If you liked this…
Your father's voice may soon come with a licence agreement
A model deed circulating among estate practitioners would treat a synthetic voice as property of the estate. The worked example in the appendix involves five siblings, a pharmacy chain and a vote of three to two.
Photographs may soon need a birth certificate
A draft practice note for the courts would require photographic evidence to arrive with an unbroken record of where it came from. Images without one would not be excluded. They would simply count for nothing.
Your attention may soon appear on the timesheet
A discussion paper prepared for a European industrial-relations forum would pay for measured concentration rather than hours on site. Thinking about a problem while staring out of a window would, under the proposed method, bill at nothing.
Still laughing
We made it up. Then reality caught up.
What we wrote
We wrote it in 2021
One day the junior developer's main skill could be describing the problem clearly enough for the machine to solve it.
What actually happened
Reality caught up in 2025
AI coding assistants are built into mainstream development tools, and producing code from a plain-language description is now a routine part of professional software work.
Vendor product documentation and developer surveys on assistant adoption.
The joke was the job description. The job description was updated.
MISTAKE
TOMORROW, DELIVERED TODAY.
One email a week. The future, before it files a press release.
Worst case: you laugh. Best case: we predicted the future.
